W3C home > Mailing lists > Public > www-rdf-interest@w3.org > September 2000

Re: Last call on XLink -> RDF mapping

From: Jonathan Borden <jborden@mediaone.net>
Date: Wed, 13 Sep 2000 16:43:49 -0400
Message-ID: <033c01c01dc3$5298fcc0$0a2e249b@Synapse>
To: "Ron Daniel" <rdaniel@metacode.com>, <www-rdf-interest@w3.org>
Cc: <w3c-xml-linking-ig@w3.org>
Ron, a couple of issues have come up during the implementation of my
xlink->rdf xslt parser at:


Using your example now at:

and ChildSeq xpointer generation:

and attribute based xpointer generation

Several issues:
1) Where the heck did the RDF 'convention' of creating URIs via (the XSLT)
concat(namespace-uri(.),local-name(.)) arise? It really really ought be:
concat(namespace-uri(.),'#',local-name(.)) unless the namespace-uri ends in
a non-NameChar (e.g. '#','/'.'\') but even then we do really really need a
URI generation mechanism that can be deconstructed into a namespace and

2) From the paper:

"If an xlink:role attribute is specified on the simple link, it shall result
in an additional statement being added to the model. The object of the
statement is the ending resource of the simple link, its predicate is
"rdf:type", and its subject is the resource identified by the role

If an implementation wishes to use facilities defined in the RDF Schema
specification [RDFSchema], it may add a second statement to the RDF model
when an xlink:role attribute is specified. The object of the second
statement is the resource identified by the role attribute, its predicate is
"rdf:type", and its subject is the resource "rdfs:Class".

Do you really mean (p,s,o) =>


or ought it be:

(rdf:type, xlink:href, xlink:role)
(rdf:type, xlink:role, rdfs:Class)

Jonathan Borden
The Open Healthcare Group

----- Original Message -----
From: Ron Daniel
To: 'www-rdf-interest@w3.org'
Cc: w3c-xml-linking-ig@w3.org
Sent: Tuesday, September 12, 2000 5:00 PM
Subject: Last call on XLink -> RDF mapping


I've made another pass over the XLink->RDF draft NOTE.
   1) I've said that links without an arcrole attribute
      SHOULD be ignored, but still allow the element type
      to be used as the predicate. This seems the best
      compromise between safety and capability.
   2) I've added an appendix that provides a simple XSLT
      stylesheet and Java extension function to harvest
      simple links.
   3) Some restructuring to reduce the amount of material
      that gets duplicated.
   4) Some edits in the section on Synthesizing XPointers.
      Gist of that is that implementations MUST synthesize
      some kind of XPointer (since they have to point into
      an XML document, there is little else they could do).
      ANY form of XPointer is allowed, although one that uses
      the ChildSeq abbreviation is recommended.
   5) assorted minor edits.

Any last comments, requests, ...? Time is short, I'm
sending this in Friday unless the XLink WG has large
comments Thursday.


 <<xlink2rdf3.html>>  <<xlink2rdf3.xml>>  <<xlink2rdf-fig1.gif>>
<<xlink2rdf-fig2.gif>>  <<xlink2rdf-fig3.gif>>

> -----Original Message-----
> From: Ron Daniel
> Sent: Wednesday, August 23, 2000 12:56 PM
> To: 'www-rdf-interest@w3.org'
> Cc: w3c-xml-linking-ig@w3.org
> Subject: RE: Update to XLink -> RDF mapping
> Apologies for the delay in informing people...
> A couple of weeks ago the XML Linking WG discussed
> the issue of what to do about the XLink->RDF mapping
> NOTE. The decision was to finish it off and publish
> it as a NOTE, investing the minimum amount of additional
> work needed for that task. Beyond that, the WG does
> not intend to work on the document.
> So, I am going to make another pass over the document
> and then call it done. People who want to get any
> changes into the document need to make requests
> to me (cc'ing the rdf-interest and xml-linking-interest
> lists) by the end of next week (Sept. 1).
> Best regards,
> Ron Daniel Jr.
> Metacode Technologies, Inc.
> 139 Townsend Street, Suite 100
> San Francisco, CA  94107
> 415.836.7813 fax 415.222.0150
> rdaniel@metacode.com
Received on Wednesday, 13 September 2000 16:54:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:31 UTC