- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 Dec 2011 10:48:58 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14752 --- Comment #1 from Henry Zongaro <zongaro@ca.ibm.com> 2011-12-13 10:48:56 UTC --- It was the intention that the schema for serialization parameters should be extensible. The output:serialization-parameters element allows for zero or more output:serialization-parameter-element children. The output:serialization-parameter-element is declared to be abstract in the schema; the elements for all other serialization parameters are defined to be in the substitution group of output:serialization-parameter-element. As is described in section 3.1,[1] the "In-scope schema types, In-scope element declarations, Substitution groups, In-scope attribute declarations" components of the static context that is used in evaluating the various queries that extract parameter values from the data model instance may contain "any additional implementation-defined in-scope schema components." So the implementation can supply any additional schema components it chooses, including, but not limited to, additional elements in the substitution group of output:serialization-parameter-element. The last paragraph before the final example box of section 3.1 states, "If the instance of the data model contains elements or attributes in the instance of the data model that are in a namespace other than http://www.w3.org/2010/xslt-xquery-serialization, the implementation MAY interpret them to specify the values of implementation-defined serialization parameters in an implementation-defined manner." So I believe that makes it clear that an implementation is permitted to define additional implementation-specific serialization parameters, and to look for them in a data model instance that was supplied to set the serialization parameters. To ensure portability of the data model instance to implementations that do not define those same serialization parameters, a user might want to include schema location hints to refer to a schema that defines those additional schema components. Implementers might want to make a schema that defines the necessary schema components for their implementation-defined serialization parameters freely available. Of course, the extensibility mechanism might have been handled in a different way - for example, through wildcards in the schema for serialization parameters. This is a personal response, not on behalf of the XSLT and XQuery working groups. [1] http://www.w3.org/TR/xslt-xquery-serialization-30/#serparams-in-xdm-instance -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 13 December 2011 10:51:11 UTC