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

[closed] Re: Comments on the Editor's Draft 14 April 2008

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 18 Apr 2008 14:59:57 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <m27ievng42.fsf@nwalsh.com>
/ Toman_Vojtech@emc.com was heard to say:
| Missing (or forgotten) texts, typos:
|
| - 2.6.3.6 (p:resolve-uri)
| Copy/paste error: the second form of the function should be
| 'p:resolve-uri', not 'p:base-uri'

Fixed.

| - 7.1.11 (p:insert)
| I think that "in which case multiple copies of the insertion document
| will occur" should read "in which case multiple copies of the insertion
| documentS will occur". Plus perhaps also mention that if the 'insertion'
| input port contains an empty sequence of documents, nothing is inserted.

Fixed.

| - 7.1.12 (p:label-elements)
| Typo: "must bind the variable '>p:index' in..."

Fixed.

| - 7.2.2 (p:hash), 7.2.3 (p:uuid)
| There are still some forgotten TBDs there

Fixed. I don't think there are parameters for the md5 or sha1 p:hash
algorithms. I added a version option to the p:uuid step.

| - 7.2.5 (p:validate-with-schematron)
| Forgotten FIXME

Fixed. I added a 'report' output. I think that's all that's needed.

| - 7.2.9 (p:xquery)
| Describe what the parameter input on this step is used for (propably for
| passing parameters to the XQuery)
| Typo: "The query> port..."

Fixed.

| General comments/questions:
|
| - 7.1.12 (p:label-elements) 
| The default value of the option 'label' contains explicit reference to
| '$p:index'. What if the prefix 'p' is not bound in the pipeline? For
| example:
|
| <x:pipeline xmlns:x="http://www.w3.org/ns/xproc">
|   <x:label-elements/>
| </x:pipeline>
|
| In case like this, the default expression for label cannot be evaluated
| because 'p' is not bound to any namespace.

The default value comes from the declaration, where the p: namespace
is bound, so I think this is ok.

| - 7.1.6 (p:directory-list)
| Shouldn't the option 'path' be renamed to 'href' so it is more
| consistent with other steps?

No, we did that intentionally to discourage http: URIs which are
unlikely to work.

| - Relative URIs in option values:
| 7.1.6 (p:directory-list) says: "The value of the path option must be an
| anyURI. It is interpreted as an IRI reference. If relative, it is
| resolved to absolute form. The base URI used for resolution is the base
| URI of p:option element, if present, otherwise, that is in case the
| default of '.' is used, the base URI of the p:directory-list element."
|
| I think there should be a similar statement for each step that accepts
| options that represent external URIs (p:load, p:store, p:xsl-formatter;
| what about 'output-base-uri' on p:xslt?), and perhaps also for p:import,
| p:document, p:log.

Fixed, I think.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | We cannot put off living until we are
http://nwalsh.com/            | ready. The most salient characteristic
                              | of life is its coerciveness: it is
                              | always urgent, 'here and now' without
                              | any possible postponement. Life is
                              | fired at us point blank.--José Ortega Y
                              | Gasset

Received on Friday, 18 April 2008 19:00:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 April 2008 19:00:38 GMT