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

Re: Remarks on W3C Editor's Draft 24 January 2008 ( part III)

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 08 Feb 2008 13:31:31 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <m2lk5v9u64.fsf@nwalsh.com>
/ Innovimax SARL <innovimax@gmail.com> was heard to say:
| Dear,
|
| In 2.3 Primary Inputs and Outputs
|
| Please precise explicitely that we cannot have more than one primary input
| or more than one primary output

Fixed.

| Idem for 2.5 Parameters
|
| --
|
| s/If the pipeline declares another port named "parameters",/If the pipeline
| declares another (non parameter) port named "parameters",/
|
| s/to parameters accepted by the p:pipeline is/to parameters accepted by the
| p:pipeline or p:declare-step is/
| s/The attribute xpath-version may be used on p:pipeline (or p:library)/The
| attribute xpath-version may be used on p:pipeline or p:declare-step (or
| p:library)/

Fixed.

| May be a complete checking of "p:pipeline" should be done to replace it by
| "p:pipeline or p:declare-step"

Yes. I thought I had...

| [[
|  that are visible to the step
|  ]]
|  I fear that visible is not defined

Fixed, I think:

<termdef xml:id="dt-readable-ports">The
<firstterm>readable ports</firstterm> are the step name/port name
pairs that are on steps in the same scope.</termdef>

|  In 2.7 Environment
|
|  it is not clear of what happen in case of shadowed input or output port
| names

What do you mean by shadowed?

|  ---
|  [[
|  cannot determine will give the same result in XPath 1.0 that it would have
| given if XPath 2.0 had been used
|  ]]
|  is it possible to point to a spec for this sentence ?

Do you have a suggestion?

|  [[
|  The XPath 2.0 functions and the
|  ]]
|  please put a reference to XPath 2.0 functions and Operators
|  --
|  Idem for "The XPath 2.0 functions."

Fixed.

| In 2.8.3.1 System Properties
|
| We should define that String for XPath 1.0 is xs:string for XPath 2.0
| --
| In 2.8.3.2 Step Available
| Boolean should refer to xs:boolean for XPath 2.0
| --
| Integer should be defined (as number for XPath 1.0 and xs:integer for XPath
| 2.0)

Fixed.

| This sentence
| [[
| All the step types in a pipeline must have unique names: it is a static
| error (err:XS0036) if any step type name is built-in and/or declared or
| defined more than once in the same scope.
| ]]
|
| is a bit troublesome : what is "in the same scope" ? it is clear that there
| is a scope for "step names" but not clear for "step types".

The beginning of 3.2, "The scope of the names of the step types is..."
attempts to explain that. Is it unclear, or do you think it's incorrect?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | A wonder is often expressed that the
http://nwalsh.com/            | greatest criminals look like other men.
                              | The reason is that *they are like other
                              | men in many respects.*-- Hazlitt

Received on Friday, 8 February 2008 18:31:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 8 February 2008 18:31:44 GMT