ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: [xml-dev] XSLT, RDF, fragment identifiers
by Uche Ogbuji other posts by this author
Jul 1 2003 6:47PM messages near this date
RE: [xml-dev] XSLT, RDF, fragment identifiers | Re: [xml-dev] XSLT, RDF, fragment identifiers
>  uche.ogbuji@[...].com (Uche Ogbuji) writes:
>  >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
>  
>  Does this work for fragments inside the same document without a separate
>  retrieval call?

Yes in the general case.  Yoiu would provide the base URI of the foaf:knows 
lement, which is probbaly the same as the base URI of the node with the 
corresponding foaf:Person.

Of couse, it would break if the user used external parsed entities or xml:base 
in ways that ruined the correspondence of base URIs.  But then their RDF would 
probably also be broken.


>  The extra-special catch comes if I have to deal with
>  these documents in a pipeline where the base URI may not be meaningful.
>  I guess the pipeline could also manage normalization.

As long as the base URI is consistent at the crucial stage of the pipeline, 
for your case it doesn't matter precisely what that URI is.


>  >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.
>  
>  I'm thinking I can make this work for simple ID-based fragment
>  identifiers, at least in a context (like RDF) where I know all the IDs
>  will be rdf:ID.

II thik in every case where i works OK for rdf:ID, it would work just aswell 
if yuo threw in rdf:about.  Blank nodes, I think, would be the wildcard.  Youd 
probably have to force users to use rdf:nodeId, and then create a new key on 
those IDs.


-- 
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



-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl> 
Thread:
Uche Ogbuji
Simon St.Laurent
Simon St.Laurent

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved