- From: Libby Miller <Libby.Miller@bristol.ac.uk>
- Date: Mon, 27 Oct 2003 16:26:42 +0000 (GMT)
- To: Emmanuel Pietriga <epietriga@yahoo.fr>
- Cc: Graham Klyne <GK@ninebynine.org>, www-rdf-interest@w3.org
Damian Steer's approach to these issues is detailed in Treehugger documentation: http://rdfweb.org/people/damian/treehugger/ http://rdfweb.org/people/damian/treehugger/introduction.html Sean Palmer has been thinking about this too: http://infomesh.net/2003/rdfpath/ Libby On Mon, 27 Oct 2003, Emmanuel Pietriga wrote: > > Beyond the RDFPath problem, there are other problems to solve, like what > is the semantics of xsl:apply-templates in the context of an RDF graph. > We don't have a tree here, so what does: > > <xsl:apply-templates select="*" /> > > mean when applied to the context node of an RDF graph? > > Emmanuel > > > > Graham Klyne wrote: > > > > > At 12:59 24/10/03 +0200, Emmanuel Pietriga wrote: > > > >> I agree that it is something useful. But isn't this what XSLT already > >> does? That's what it does for XML. So why couldn't it do it for RDF? I > >> mean, except for the XPath part that is not (as discussed yesterday) > >> the best-suited technology to address nodes and arcs of an RDF graph, > >> XSLT seems to be well-suited to this task (all that is needed is to > >> replace XPath selectors by *RDFPath* selectors). > > > > > > I think that's a really interesting idea... using the existing XSLT > > design to its strengths and directly addressing its weakness with > > respect to RDF data. > > > > #g > > > > > > ------------ > > Graham Klyne > > For email: > > http://www.ninebynine.org/#Contact > > > > > -- > Emmanuel Pietriga (epietriga@nuxeo.com) > tel (mobile): +33 6 88 51 94 98 > http://claribole.net > > >
Received on Monday, 27 October 2003 11:40:10 UTC