Andy, is it possible however to have the original bnode IDs carried over to the output, or are they already lost when re-labelled with internal IDs?
I was thinking about producing anchors (HTML #fragments) for that part of HTML which renders an according #bnode in RDF. But I realized I can't do it if I can't get the original IDs. Martynas graphity.org On Sun, Mar 25, 2012 at 7:47 PM, Andy Seaborne <[email protected]> wrote: > On 24/03/12 23:55, Martynas Jusevicius wrote: >> >> Hey, >> >> I'll forward it to them :) >> >> Seems like I won't find an easy way out of this one. I'm using the >> DatasetGraphAccessorHTTP class which internally serializes into >> RDF/XML, so I guess I'll have to override that in order to try out the >> N-Triples option you mention. > > > yes, but only because RDF/XML is the only standard. > > N-triples will be standardised by RDF-WG (as well as Turtle and hopefully > TriG and NQuads if named graph debates pause enough to do the somewhat > mechanical work on named graph syntaxes). > > Andy > > > > >> >> Martynas >> graphity.org >> >> On Sun, Mar 25, 2012 at 12:13 AM, Andy Seaborne<[email protected]> wrote: >>> >>> On 24/03/12 22:47, Martynas Jusevicius wrote: >>>> >>>> >>>> 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 >>> >>> >>> >>> Naughty Dydra, that's not what the specs say. Labels are scoped to the >>> file >>> as read -- i.e. you can conclude nothing about whether two files (or one >>> file read twice) refer to the same bNode from the serialization label >>> alone. >>> >>> Nasty things will happen because some bNodes are implicit and some >>> explicitly labels. I can see why they do it though. c.f. Talis stores >>> which convert bNodes to URIs. >>> >>> Try N-triples, the normal output uses the internal unique label to >>> generate >>> the _: name. if need be convert with RIOT >>> "riot D.rdf> "D.nt". >>> >>> Else you might try rewriting the RDF/XML output and do string >>> substitution. >>> rdf:nodeID="A0" is quite easy to spot. >>> >>> (The RDF-WG is fixing this with a skolemization scheme.) >>> >>> Andy >>> >
