W3C home > Mailing lists > Public > public-grddl-wg@w3.org > June 2007

Proposal 2b to address issue-dbooth-3 (ambiguity)

From: Booth, David (HP Software - Boston) <dbooth@hp.com>
Date: Wed, 20 Jun 2007 01:15:03 -0400
Message-ID: <EBBD956B8A9002479B0C9CE9FE14A6C202CCAA0D@tayexc19.americas.cpqcorp.net>
To: "GRDDL Working Group" <public-grddl-wg@w3.org>

This proposal extends proposal 1b at
to also reduce/eliminate variability in the "transformaiton
determination" step, by specifying that the document parsing must be
minimal, non-validating parsing.  The only difference from that proposal
is part 1 below.  

Please note that this proposal also does not require any changes to our
test cases.

Summary of proposed changes: 
	- Change the domain of the GRDDL transformation from XPath node
tree to the original XML document (representation)

	- Require minimal, non-validating parsing

	- Leave the door open to a future Note that would define
"complete GRDDL results".


1. In http://www.w3.org/2004/01/rdxh/spec#rule_result which is
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[RDFC04] G, then G is a GRDDL result of IR.
change "XML document" to "XML document D"
and "TP applied to R" to "TP applied to D"
and add the following sentences:
Furthermore, N MUST be the root node of an XPath node tree T that is
created from D using only the minimum processing required of a
non-validating parser[XML] to produce T corresponding to D.  However,
such processing MAY include error checking that does not affect T.
And make corresponding changes to the informative text in section 6 and
the XInclude test cases.

2. I write a separate Working Group Note that defines the notion of
"complete GRDDL result", which would be referenced from the GRDDL spec.
GRDDL-aware agents would NOT be required to implement this. 
A draft of this Note is currently available at:

3. In conjunction with this Note, we adopt the following two changes to
the GRDDL spec:

a. To enable complete GRDDL results to be determined when namespace or
profile documents are used, add the following sentence to the end of the
Faithful Renditions section:
Furthermore, by serving a representation of a namespace or profile
document that indicates any namespace or profile transformations, the
author of that document states that every representation that indicates
any namespace or profile transformations indicates the same set of
namespace or profile transformations.

b. In sec 7 (GRDDL-aware agents), before the example, add:
Determining Complete GRDDL Results

In some cases, the person or application making use of a GRDDL-aware
agent may wish to know whether the GRDDL results obtained from an XML
document are known to constitute <i>all</i> of the GRDDL results that
the document was intended to denote.  This specification does not define
a notion of <i>complete GRDDL results</i>, but as of this writing the
GRDDL Working Group is considering publishing such a definition as a
separate Working Group Note.  Implementers of GRDDL-aware agents would
be encouraged, but not required, to make use of such a definition if one
is published.

David Booth, Ph.D.
HP Software
+1 617 629 8881 office  |  dbooth@hp.com

Opinions expressed herein are those of the author and do not represent
the official views of HP unless explicitly stated otherwise.
Received on Wednesday, 20 June 2007 05:16:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:50 GMT