RE: Update to XLink -> RDF mapping

Hi Dan,

Thought I had sent a response earlier but don't see
it, so here's the old response plus some new stuff...

Dan Connolly said:

> an editorial nit: it says both
> | The
> | starting Resource of the simple link SHALL be mapped to the subject of
> the RDF statement.
> and
> | The ending Resource of the simple link SHALL be mapped to the subject
> of the RDF statement.
> I presume you meant 'object' rather than 'subject' in the latter.
Yep, thanks for catching that. I've updated it in the
XML source of the NOTE and it will go out with the
next version.

> Anyway... I got about 1/10th of the way thru implementing it
> as an XSLT transformation. I was able to convert your first
> example:
> ... In a <x:extRef xlink:type="simple"
>       xlink:href=""
>       xlink:arcrole=""
>       xlink:role=""
>    >recent paper</x:extRef>, Dr. Taylor assumes that ...
> to
> <rdf:RDF xmlns:rdf=""
> xmlns:xlink="">
>   <oops-predicate rdf:about="#xpointer-for-N8"
>   rdf:resource=""
>   xmlns=""
>   xmlns:rdf="" />
>   <rdf:type rdf:about=""
>   rdf:resource="" />
>   <rdf:Class rdf:about="" />
> </rdf:RDF>
> As you can see, I ran into some trouble already:
> 	* how do I compute a namespace name and a local name from
> 	the predicate I suppose
> 	l:cite xmlns:l='' would work,
> 	but I couln't figure out how to implement that with XSLT ;-)
> 	But I don't see a general purpose algorithm, especially
> 	since URIs need not end with XML name characters
> 	(e.g.
> 	This is a generic RDF problem, not a problem with this
> 	xlink->rdf mapping; i.e. it's an issue with serializing
> 	RDF models in the general case.
To be perfectly honest, I had been assuming that the
harvesting would happen through something like XSLT extension
functions that directly poked statements into an RDF store,
rather than converting to RDF's serialization syntax.
How to serialize a RDF model that never kept info about
the namespace URI vs. local part is, as you point out,
a thorny issue for all RDF implementations.

But your sample motivated me to actually try and write
a proof-of-concept. Here's a XSLT stylesheet and a
mockup of the extension function. Barring errors, I think
the stylesheet handles all the cases with simple links.
I have not done anything with extended links yet.

This particular stylesheet works with saxon's version of
extension functions. It should not be hard to make it
work with XT but I have not tried.

(BTW - people who see '' should not get
their hopes up. This is nothing more than one call.)

 <<map_simple.xsl>>  <<>>  <<ex1.xml>> 

Ron Daniel Jr.
Metacode Technologies, Inc.
139 Townsend Street, Suite 100
San Francisco, CA  94107
415.836.7813 fax 415.222.0150

Received on Tuesday, 11 July 2000 14:44:54 UTC