W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2007

Re: Remarks on alternate proposal

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Mon, 26 Feb 2007 15:50:28 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <87k5y4prsb.fsf@nwalsh.com>
/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| http://www.w3.org/XML/XProc/docs/alternate/
|
| == Typos ==
|
| Example 5. A Sample Pipeline Library
|
| <p:pipeline-library>
|  <p:declare-step-type> name="extension-component">…</p:declare-steptype>
|
| should be (two changes the extra > and the missing "-" in close tag)
|
| <p:pipeline-library>
|  <p:declare-step-type name="extension-component">…</p:declare-step-type>

Fixed.

| --
| Example 3. A Sample Viewport
|
| <p:viewport name="encdivs" match="h:div[@class='enc']>
|  <p:input port="source">
|    <p:pipe step="step" port="port"/>
|  </p:input>
|  <p:output port="result">
|    <p:pipe step="encrypt" port="result"/>
|  </p:output>
|  <p:step name="encrypt" type="p:encrypt-document">
|    <p:input port="source">
|      <p:pipe step="encdivs" port="current"/>
|    </p:input>
|  </:step><!-- it should be </p:step> here -->
| </p:viewport>

Fixed.

| --
| Conceptually, we can speak of components as objects that have inputs
| and outputs that are connected together and which may have contain
| additional components. Syntactically, we need a mechanism for
| specifying these relationships.
|
| should be (removing have between 'may' and 'contain' and adding comma
| before second 'that')
|
| Conceptually, we can speak of components as objects that have inputs
| and outputs, that are connected together and which may contain
| additional components. Syntactically, we need a mechanism for
| specifying these relationships.
| --

Fixed.

| (not sure)
|
| The union of all the declared outputs of the contained components are
| added to the outputs in the context.
|
| should be
|
| The union of all the declared outputs of the contained components is
| added to the outputs in the context.

Fixed.

| == Miss ==
| Try/Catch is still not in the proposal

Fixed.

| == Precision ==
| 1/ What is the use of @sequence ?

It informs the processor when a sequence may be possible.

| 1.a/ In case of @sequence=yes and I put a single p:document ?

That's ok, a sequence of length 1 is still a sequence.

| 1.b/ In case of @sequence=no and I put two or more p:document ?

That's a dynamic error.

| ==Changes==
| 1/NCName vs QName

I think I've fixed those.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Monday, 26 February 2007 20:51:11 GMT

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