- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 23 Aug 2007 02:04:10 +0000
- To: public-sml@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4977 Summary: Schematron queryBinding attribute Product: SML Version: FPWD Platform: PC URL: http://www.schematron.com/spec.html OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Core AssignedTo: virginia.smith@hp.com ReportedBy: virginia.smith@hp.com QAContact: public-sml@w3.org According to section 4.2.1 the queryBinding attribute is required to be "xpath 1.0" if specified. The Schematron spec states that the default queryBinding is "xslt" when none is specified. (A value of "xpath 1.0" is not defined in the spec at all.) 1 - Why should we restrict the queryBinding in SML? Perhaps we should specify it in SML-IF but is there a good reason to restrict it in SML? 2 - If we do restrict the queryBinding, it should be the default of "xslt". Other values are mentioned in the spec but are intentionally undefined. However, we can assume a value of "xpath" would eliminate xslt functions in xpath expressions. -------from Schematron spec-------- ...The optional queryBinding attribute provides the short name of the query language binding in use. If this attribute is specified, it is an error if it has a value that the current implementation does not support.... ...The following query language names are reserved without further definition. Implementations which use different query language bindings are encouraged to use one of these names if appropriate : stx, xslt, xslt1.1, exslt, xslt2, xpath, xpath2, xquery.... Also see Appendix C in spec: A Schematron schema with no language binding or a queryBinding attribute with the value xslt, in any mix of upper and lower case letters, shall use the following binding: ...
Received on Thursday, 23 August 2007 02:04:13 UTC