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

Proposal 3c (compromise) to address the ambiguity issue

From: Booth, David (HP Software - Boston) <dbooth@hp.com>
Date: Tue, 26 Jun 2007 02:05:17 -0400
Message-ID: <EBBD956B8A9002479B0C9CE9FE14A6C202D33528@tayexc19.americas.cpqcorp.net>
To: <public-grddl-wg@w3.org>

This is a compromise proposal to address the ambiguity issue.  It only
involves changes to informative text.  In essence, this proposal
delegates further specification of the XML parsing/pre-procesing to TAG
issue xmlFunctions-34 and the XProc working group's task of defining a
default processing model.  This would not fix the ambiguity problem
right now, but at least (in theory) it would cause the problem to go
away when those are resolved.


1. In section 6
change "When an information resource" to "At present, when an
information resource".

2. Also in section 6, change "is unspecified" to:
is currently unspecified. However, this specification anticipates that
the resolution of TAG issue
<a href="http://www.w3.org/2001/tag/issues.html?type=1#xmlFunctions-34">
and the definition, by the 
<a href="http://www.w3.org/XML/Processing/">XML Processing Model Working
Group</a>, of a default processing model will provide further
clarification and guidance, and GRDDL-aware agents are expected to
comply with such guidance if it is issued.

3. Change the description of the XInclude test cases as previously
suggested by Jeremy.  Specifically, change the sentence beginning "In
particular, ... " to the following:
In particular, the output illustrates a situation where the XML
processor invokes XInclude processing at a low-level and presents the
expanded <a href="http://www.w3.org/TR/xinclude/#processing">result
infoset</a> <a href="#ref-XInclude">[XINCLUDE]</a> to the GRDDL-aware
Note that most browsers do not perform the XInclude, and
thus their behavior does not correspond with the output shown.  This
pair of tests anticipate that the resolution of TAG issue
will provide further guidance concerning them.


 - Some GRDDL implementations that are conformant now may no longer be
conformant when the TAG's issue xmlFunctions-34 is resolved or the XProc
working group defines a default processing model.

 - Making forward reference to a spec that is not yet published is
somewhat unusual, but not unprecedented.  For example, the RDF Concepts
document did this in reference to the non-yet-published IRI spec:

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 Tuesday, 26 June 2007 06:32:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:39 UTC