[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XSLT, RDF, fragment identifiers

• To: "Simon St.Laurent" <simonstl@s...>, <xml-dev@l...>
• Subject: RE: XSLT, RDF, fragment identifiers
• From: "Hunsberger, Peter" <Peter.Hunsberger@s...>
• Date: Tue, 1 Jul 2003 10:36:49 -0500
• Thread-index: AcM/382/fH1xTFqHRnqA0F/7nbN9rgABU7zQ
• Thread-topic: XSLT, RDF, fragment identifiers

Simon St.Laurent <simonstl@s...> 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?

• Follow-Ups:
  • RE: XSLT, RDF, fragment identifiers
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: Re: Allowed PEReference usages
• Next by Date: Re: Chameleon schemas <include>ing chameleon schemas
• Previous by thread: Re: Allowed PEReference usages
• Next by thread: RE: XSLT, RDF, fragment identifiers
• Index(es):
  • Date
  • Thread