[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...>
• Subject: Re: XSLT, RDF, fragment identifiers
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Tue, 01 Jul 2003 10:24:16 -0600
• Cc: xml-dev@l...
• In-reply-to: Message from "Simon St.Laurent" <simonstl@s...> of "Tue, 01 Jul 2003 10:47:14 EDT." <r02000000-1026-E960F1B9ABD211D7AD300003937A08C2@[192.168.124.11]>
• Sender: uche.ogbuji@f...

> [This question crosses XSLT, RDF, and general web architecture, so
> xml-dev seems like an appropriately cross-cultural place to post it.]
> 
> 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.
> 
> (Except maybe with the xpath1() scheme [1], of course, but that's highly
> unofficial.)
> 
> This seems to make XSLT even less appropriate for working with RDF than
> I'd originally thought, though I'd be happy to be shown wrong in this
> case.

Unsatisfactory answer (and how I do it): Use a processor that has a 
normalize-url() or resolve-url() extension function.  For example: 4Suite.  I 
think Saxon has such a beast as well.  In 4XSLT it's resolve-url(), namespace 
http://xmlns.4suite.org/ext

I usually combine this with an xsl:key that indexes rdf:about and rdf:ID.  
That way I can resolve fragments to full URIs and then look them up easily and 
efficiently.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
XML Data Bindings in Python - http://www.xml.com/pub/a/2003/06/11/py-xml.html
Introducing Examplotron - http://www-106.ibm.com/developerworks/xml/library/x-x
mptron/
Charming Jython - http://www-106.ibm.com/developerworks/java/library/j-jython.h
tml
The commons of creativity - http://www-106.ibm.com/developerworks/xml/library/x
-think18.html
A custom-fit career in app development - http://www.adtmag.com/article.asp?id=7
744

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

• References:
  • XSLT, RDF, fragment identifiers
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: RE: XSLT vs. CSS (Re: Indexing)
• Next by Date: Re: Chameleon schemas <include>ing chameleon schemas
• Previous by thread: Re: XSLT, RDF, fragment identifiers
• Next by thread: Re: XSLT, RDF, fragment identifiers
• Index(es):
  • Date
  • Thread