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

Re: ANN: XSLT RDF Parser

From: Dan Brickley <danbri@w3.org>
Date: Wed, 13 Sep 2000 06:27:34 -0400 (EDT)
To: Jason Diamond <jason@injektilo.org>
cc: www-rdf-interest <www-rdf-interest@w3.org>
Message-ID: <Pine.LNX.4.21.0009130557110.21070-100000@tux.w3.org>
On Wed, 13 Sep 2000, Jason Diamond wrote:

> Hi.
> 
> I've updated my XSLT RDF Parser to include support for containers,
> rdf:value, parseType, and more.
> 
> http://injektilo.org/rdf/

Aside: there's a minor problem with that page; missing stylesheet:
<link rel="stylesheet" href="injektilo.css" type="text/css" /> caused
Netscape to 404, because of an amusing bug in Netscape where pages with
bad stylesheet links show up as 404s (not exactly graceful degradation...;-)


> I've also refactored it so that it's broken up into many (over 30) smaller
> <xsl:template>s instead of the basically single large one full of <xsl:if>s
> and <xsl:for-each>s that was in the previous version.

Excellent! Sounds like this is shaping up as a real usable tool :-)

So does nybody fancy running some benchmarks? eg. this XSLT in a C++ XSLT
engine versus SiRPAC, VRP, the Prolog parser etc etc...?

> This update can actually parse all but two of the examples in Section 7 of
> the RDFM&S. I've placed a page with links to Dan Connolly's Extraction
> Service for each of the examples on my site. (I hope this is OK.)

Fine, so long as folk know it's an experimental service. It's good to know
people are finding it of value though; I think a more production-grade
successor service is in the works btw.

> http://injektilo.org/rdf/examples.html
> 
> This is so much fun! If anybody has any comments or finds any bugs, please
> let me know. I'm going to work on bagID and reification next.

One little thing: where you have an ID, eg 'foo', you're outputting '#foo'
where one might expect 'http://baseuritodocument.../etc#foo'.

> Thanks,
> Jason Diamond.
> 
> P.S. What the hell am I supposed to do with aboutEachPrefix? It doesn't seem
> possible to implement.

Hmm... I've not met anyone who considers this anything but a
bug. Something needs to be done about that; in the meantime, nobody seems
to be creating data that uses aboutEachPrefix anyway.

Longer term, we'll want something similar, but that has an RDF model
representation. There's two aspects: (1) picking out a class of things
to make statements about, but without laboriously enumerating its members
(really handy) and (2) doing so through regex matching against URIs
(sometimes useful).

Dan
Received on Wednesday, 13 September 2000 06:27:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:44 GMT