Re: Raptor 1.4.14 GRDDL 2006-10-24 implementation report

Hi Dave!

A  couple of comments on your message (not on the specs)

BTW Dan, I like the new text on caching - I'm aware of needing to do 
some of that - I have a cache but it doesn't comply with your new text 
(which is appropriate, it was done in too much of a hurry)

Dave said:
 > One issue I found causing problems was whether to traverse the GRDDL
 > profile URI itself, http://www.w3.org/2003/g/data-view

My implementation must read this doc, because I don't have a hard coded 
rule for profileTransformation, but rely on the GRDDL transform of the 
GRDDL profile.


 >    4. The GRDDL profile for XHTML
 >
 > This was implemented by earlier Raptor versions.
 >
 > It might be worth repeating that the <head profile="..."> is a
 > space-separated list of URIs and to look for the GRDDL profile you
 > need to find it in that list.

Not clear from your message, but my understanding is that it is *not* 
required for GRDDL profile to be explicit in that list. If any of the 
profile docs has a GRDDL transform, with a profileTransformation triple 
in it, then that applies.

 > The current WD mentions having non-XML results here such as Turtle .
 > with issue-output-formats
 >
 > This was tricky to deal with in XSLT and in the tests because
 > the XSLT environment does not always return an output mime type,

The test for this has an explicit mimetype "text/rdf+n3" declared within 
the XSLT. The Jena impl uses that to select the parser. No sniffing.

===

Other, I have some more tests at:

http://jena.sourceforge.net/test/grddl/

Most assume XSLT 2.0; some are Saxon specific. Quite a few deal with 
security issues.

Jeremy

Received on Wednesday, 7 February 2007 12:37:32 UTC