Hey Andy, well yeah, I mean the serialized form. But that is what gets inserted (currently POSTed as RDF/XML over the graph store protocol) and becomes the bnode IDs in the store. The store in question is the cloud service http://dydra.com.
Martynas On Sat, Mar 24, 2012 at 11:38 PM, Andy Seaborne <[email protected]> wrote: > On 24/03/12 21:31, Martynas Jusevicius wrote: >> >> Hey all, >> >> what would be the easiest way to control the generation of blank node IDs? >> What I need is to make them globally unique (I'm thinking UUIDs or >> smth like that), because that's the approach taken by the triple store >> I'm using. > > > Which one? > > >> Currently I load several documents into the store with the same >> Jena-generated IDs (A0, A1, etc), > > > Jena IDs should not be of the form A0, A1, ... -- is this their serialized > output (which is not the internal ID). > > >> and they sit nicely in their >> separate named graphs. However when triples containing those bnodes >> get re-serialized into a single RDF/XML result, the IDs are matching >> where they shouldn't be. > > > Concrete example? Every reading of a file should produce different bNodes > (unless you have reached into the internals of jena and changed the > allocation scheme.) > > (The RIOT parsers are configurable but not exposed.) > > Andy > >> >> Martynas >> graphity.org > >
