Andy, would you agree though that such feature (correspondence between blank nodes and HTML anchors) would make sense? However it seems pretty much impossible as you describe it, since I'm using RDF/XML as a gateway for all RDF serializations in the wild, which then gets transformed with XSLT.
I was thinking maybe I could somehow generate the fragment IDs opaquely, without loading the RDF document. XSLT has a generate-id() function, but it wouldn't really help here as it works on document nodes. Maybe I could hash the whole URI and use that as the fragment ID (would probably look quite ugly). Hash the hash URI, so to speak? Martynas graphity.org On Mon, Mar 26, 2012 at 10:54 PM, Andy Seaborne <[email protected]> wrote: > On 25/03/12 22:01, Martynas Jusevicius wrote: >> >> I mean when serializing RDF/XML. >> >> On Sun, Mar 25, 2012 at 10:59 PM, Martynas Jusevicius >> <[email protected]> wrote: >>> >>> 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. > > > They get relabelled - AFAIK this isn't changeable in ARP. > > On reading, the labels are treated as file-local and there is a mapping from > file label to internal Ids but the file usage isn't recorded > > For RIOT, you can change the policy at he very lowest levels. But you end > up with non-RDF semantics. > > Andy > >
