RE: Using the XInclude component with a default processing model for GRDDL

Looks good!
 


David Booth, Ph.D.
HP Software
+1 617 629 8881 office  |  dbooth@hp.com
http://www.hp.com/go/software

Opinions expressed herein are those of the author and do not represent
the official views of HP unless explicitly stated otherwise.


 


________________________________

	From: public-grddl-wg-request@w3.org
[mailto:public-grddl-wg-request@w3.org] On Behalf Of Ogbuji, Chimezie
	Sent: Wednesday, June 13, 2007 9:29 PM
	To: public-xml-processing-model-comments@w3.org
	Cc: public-grddl-wg@w3.org
	Subject: Using the XInclude component with a default processing
model for GRDDL
	
	

	This comment is with respect to the XML Pipleline Language's
XInclude component [1].  The GRDDL Working Groups resolution [2] to
postpone the #faithful-infoset issue in concert with the Technical
Architecture Group's ongoing [3] conversation on xmlFunctions-34  is
predicated on the XML Processing Model Working  Group meeting its
chartered responsibility for defining a default processing model:
	
	[[
	In the absence of any guidance, what default processing, if any,
should be done in what circumstances?
	]] --
http://www.w3.org/2005/10/xml-processing-model-wg-charter.html#xml-scope
	
	This is especially important for situations where uncertainty in
an XML Document's infoset can cause ambiguity in the GRDDL results
associated with that XML Document.  The GRDDL Working Group has
developed two test cases which demonstrate [4] (in the absence, at this
time,  of a recommendation document for XProc) the need for more
coarse-grained XML processing of XML Documents which make use of
"elaborating namespaces" [5] .
	
	In particular, Xinclude components will need to be used after a
deterministic, default processing model is applied to form the infoset
it takes as input.  Although short of the use of non-validating parsers,
ambiguity cannot [6] be completely eliminated from this infoset,
ambiguity as a result of the use of elaborating namespaces needs to be
addressable via XProc (in conjunction with a default processing model).
The #noxinclude test demonstrates measures that could be taken (but not
enforced by GRDDL) to ensure that XProc (along with certain processing
dictates) is properly used to ensure a functional mapping to a GRDDL
result from an XML Document.
	
	[1] http://www.w3.org/TR/xproc/#c.xinclude
	[2] http://www.w3.org/2007/06/06-grddl-wg-minutes.html#item04
	[3] http://www.w3.org/2001/tag/2007/06/11-minutes.html#item07
	[4]
http://www.w3.org/2001/sw/grddl-wg/td/grddl-tests#multiple-infosets
	[5] http://www.w3.org/2001/tag/doc/elabInfoset.html#elab_ns
	[6]
http://lists.w3.org/Archives/Public/public-grddl-wg/2007Jun/0000.html
	
	Chimezie (chee-meh) Ogbuji
	Lead Systems Analyst
	Thoracic and Cardiovascular Surgery
	Cleveland Clinic Foundation
	9500 Euclid Avenue/ W26
	Cleveland, Ohio 44195
	Office: (216)444-8593
	ogbujic@ccf.org
	
	
	

	
	===================================
	
	
	
	
	Cleveland Clinic is ranked one of the top 3 hospitals in
	America by U.S.News & World Report. Visit us online at
	http://www.clevelandclinic.org for a complete listing of
	our services, staff and locations.
	
	
	Confidentiality Note:  This message is intended for use
	only by the individual or entity to which it is addressed
	and may contain information that is privileged,
	confidential, and exempt from disclosure under applicable
	law.  If the reader of this message is not the intended
	recipient or the employee or agent responsible for
	delivering the message to the intended recipient, you are
	hereby notified that any dissemination, distribution or
	copying of this communication is strictly prohibited.  If
	you have received this communication in error,  please
	contact the sender immediately and destroy the material in
	its entirety, whether electronic or hard copy.  Thank you.