Some spec comments

Section 2 example

[[

<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:grddl='http://www.w3.org/2003/g/data-view#'
      grddl:transformation="glean_title.xsl
	
http://www.w3.org/2001/sw/grddl-wg/td/getAuthor.xsl"
 >
]]

Might that better be 

  http://www.w3.org/2001/sw/grddl-wg/td/getAuthor

i.e. drop the commitment to xsl.

--------------

A little further down, where it states:

[[
The glean_title.xsl transformation computes the following RDF/XML
document, given the XML document above as input:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:dc="http://purl.org/dc/elements/1.1/">
  <rdf:Description rdf:about="">
    <dc:title>Are You Experienced?</dc:title>
  </rdf:Description>
</rdf:RDF>
]]

This would be a good place to make it clear that the relative URI
references in this graph are relative to the URI of the source document
e.g.

[[
Note that this serialization of the graph contains a relative URI
reference.  The base URI for interpretting relative URI references in a
serialization of a graph produced by a GRDDL transformation is the URI
of the source document.
]]

---------------

[[
If an information resource([WEBARCH], section 2.2) IR is represented by
an XML document with an XPath root node R, and R has a GRDDL
transformation with a transformation property TP, and TP applied to R
gives an RDF Graph G, then G is a GRDDL result of IR.
]]

Reading the rule jars a bit because the definition of TP comes after the
rule - better to move it before.  

[[
Before introducing the rule that will define a GRDDL result, we first
introduce the idea of a transformation property.  Loosely, a
transformation can be thought of as a function from an input
representation to an RDF graph.  The transformation property of a
transformation represents that function.  The transformation property of
a transformation T is an RDF property that relates each input to T to
the result of applying T to that input.  

[[[Might want to move the rule at the end of section 6 Transformation
Algorithms here]]]

If an information resource([WEBARCH], section 2.2) IR is represented by
an XML document with an XPath root node R, and R has a GRDDL
transformation with a transformation property TP, and R is in the domain
of TP and TP relates R to an RDF Graph G, then G is a GRDDL result of
IR.
]]

This raises two questions in my mind.

1.  Should we say something about what happens when the input document
is not in the domain of the transformation - e.g. the code goes belly up
when executing.  This might affect the section on conformance labels.
Maybe we can just stay silent.

2. Is a transform necessarily functional on the input document alone?
For example, a transform that includes a triple containing the time at
which the transform was run is not a GRDDL transform?

Hey - I got to the end of section 2.

Brian

Received on Monday, 19 February 2007 16:34:56 UTC