[
Lists Home |
Date Index |
Thread Index
]
Simon St.Laurent <simonstl@simonstl.com> writes:
> Does XSLT (in 1.0 or 2.0) have an understanding of fragment
> identifiers?
>
> I'm dealing with a case where information looks like:
>
> <foaf:knows rdf:resource="#ben"/>
> <foaf:knows rdf:resource="#bitworking"/>
> <foaf:knows rdf:resource="#clkeller"/>
>
> All of those rdf:resource attributes act like IDREFs,
> pointing elsewhere in the same document, but of course
> they're not IDREFs - and the IDs to which they point are
> rdf:ID attributes, which aren't declared with a DOCTYPE.
>
> Hunting around on Google didn't bring much up, but then
> fragment identifiers aren't exactly the most exciting stuff.
> I'm thinking that I can solve this particular case with some
> XPath string tweaking and keys, but I seriously doubt XSLT is
> an appropriate environment for parsing URIs to figure out
> where to look and what to take.
I'm not sure quite what the issue is? Aren't URIs well enough defined
that something like:
*[concat('#',substring-after(uri,'#')) = @rdf:resource]
should behave predictably? Or am I just missing something completely?
|
