- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Thu, 26 Oct 2006 10:11:16 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87hcxryxob.fsf@nwalsh.com>
For completeness, here's a proposal to "go the other way". The following proposal changes p:for-each/p:viewport to remove the syntactic inconsistency. 4.2.9 p:for-each Element A p:for-each represents a for-each. <p:for-each name=NCName port=QName step=step name select?=xpath expression> (p:declare-output*, p:declare-parameter*, subpipeline) </p:for-each> The input to the for-each must be bound with the port, step, and select attributes. If outputs are declared, they must also include a binding. ... 4.2.10 p:viewport Element A p:viewport represents a viewport. <p:viewport name=NCName port=QName step=step name select=xpath expression> (p:declare-output, p:declare-parameter*, subpipeline) </p:viewport> The input to the viewport must be bound with the port and step attributes. A select attribute must be specified to identify the processed regions of the input. Exactly one output must be declared and it must include a binding. ... Be seeing you, norm -- Norman Walsh XML Standards Architect Sun Microsystems, Inc.
Received on Thursday, 26 October 2006 14:11:58 UTC