W3C home > Mailing lists > Public > xproc-dev@w3.org > February 2010

typo and awkward paragraph ordering in Xproc W3C Working Draft 5 January 2010 "5.1.2 Parameter Inputs"

From: Bruce Chapman <bruce.chapman@nec.co.nz>
Date: Fri, 19 Feb 2010 15:22:36 +1300
To: public-xml-processing-model-comments@w3.org
Cc: xproc-dev@w3.org
Message-id: <D131389687904844B0CCC4EA1A9C2BA0@necwlgxpwapp210>
5.1.2 Parameter Inputs <http://www.w3.org/TR/xproc/#parameter-inputs>  says

"If a connection is manufactured for a primary parameter input port, that
connection occurs logically last among the other parameters, options, and
connections passed to the step. In other words, the parameter values that
appear on that port will be used even if other values were specified with
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements. Users can
change this priority by making the connection explicit and placing any
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements that they
wish to function as overrides after the connection.

All of the documents that appear on a parameter input must either be
<http://www.w3.org/TR/xproc/#cv.param> c:param documents or
<http://www.w3.org/TR/xproc/#cv.param-set> c:param-set documents.

A step which accepts a parameter input reads all of the documents presented
on that port, using each  <http://www.w3.org/TR/xproc/#cv.param> c:param
(either at the root or inside the
<http://www.w3.org/TR/xproc/#cv.param-set> c:param-set) to establish the
value of the named parameter. If the same name appears more than once, the
last value specified is used. If the step also has literal
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements, they are
are also considered in document order. In other words,
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements that appear
before the parameter input may be overridden by the computed parameters;
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements that appear
after may override the computed values."

 

<aside> I (lies - my editor app) just noticed a spurious duplicate word in
the last paragraph above - "are are" </aside>

I read this for the first time yesterday, and after reading the first
paragraph above, I thought "There seems to be some sort of precedence rule
applying here, but I don't remember reading about it"

Then once I had read the last quoted paragraph, I thought "Aha, so here is
the precedence rule."

Suggestion: It might be better to reorder these paragraphs thus

A step which accepts a parameter input reads all of the documents presented
on that port, using each  <http://www.w3.org/TR/xproc/#cv.param> c:param
(either at the root or inside the
<http://www.w3.org/TR/xproc/#cv.param-set> c:param-set) to establish the
value of the named parameter. If the same name appears more than once, the
last value specified is used. If the step also has literal
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements, they are
are also considered in document order. In other words,
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements that appear
before the parameter input may be overridden by the computed parameters;
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements that appear
after may override the computed values.

If a connection is manufactured for a primary parameter input port, that
connection occurs logically last among the other parameters, options, and
connections passed to the step. In other words, the parameter values that
appear on that port will be used even if other values were specified with
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements. Users can
change this priority by making the connection explicit and placing any
<http://www.w3.org/TR/xproc/#p.with-param> p:with-param elements that they
wish to function as overrides after the connection.

All of the documents that appear on a parameter input must either be
<http://www.w3.org/TR/xproc/#cv.param> c:param documents or
<http://www.w3.org/TR/xproc/#cv.param-set> c:param-set documents.

Regards

Bruce

 

 
Received on Friday, 19 February 2010 11:36:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 19 February 2010 11:36:06 GMT