This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The current draft of SML specifies that it uses and constrains XML 1.0 documents, implicitly excluding XML 1.1 documents. This should be revisited in the light of (a) the completion of XML 1.1 and (b) the support for XML 1.1 in other specifications (such as XSD 1.1). Personally, I think the correct thing to do is to make SML version-agnostic vis-a-vis XML (and vis-a-vis most other specifications), in a way similar to that common in ISO specs. Another resolution of this issue would be to stay with XML 1.0, or to move to XML 1.1, or to allow either, or ...
Michael will present differences between XML 1.0 and 1.1 at the WG meeting in Toronto.
Discussed during 2007-08-30 F2F question. Decided to adopt the general principle to specify a fixed floor and an open ceiling. More specifically: SML processors are required to support SML 1.0, XML Schema 1.0 and XPath 1.0; but they are allowed to also support any future versions of those referenced specifications.
I have created a new section in the SML document defining the relationship between SML and XML, XML Schema, XPath and Schematron : 3. Dependencies on Other Specifications Other specifications on which this one depends are listed in [Normative-References]. This specification is a profile of XML Schema 1.0 [XML Schema Structures, XML Schema Datatypes] and defines datatypes depending on definitions in XML 1.0 [XML 1.0]. SML uses a profile of Schematron [ISO/IEC 19757-3] and XPath 1.0 [XPath 1.0] for defining rules. Conforming implementations of this specification MUST support XML 1.0 [XML 1.0], XML Schema 1.0 [XML Schema Structures, XML Schema Datatypes], Schematron [ISO/IEC 19757-3] and XPath 1.0 [XPath 1.0]. However, the current specification does not impose any restrictions on using newer versions of the XML, XML Schema, Schematron or XPath specifications. Conforming implementations are encouraged to investigate the possibility of applying the most recent editions of the [Normative-References] indicated below.
Created attachment 486 [details] updated SML document
Pratul's comments on the sml mailing list : The first para states that SML uses a profile of XML Schema 1.0 - which is not true any longer. I also don't understand the phrase "and defines datatypes depending on definitions in XML 1.0" - the SML datatypes are based on XML Schema 1.0 and not XML 1.0 I am not comfortable with the last para since we are not providing any guidance on how the "most recent versions" should be used. Plus, the para appears to be redundant since the 2nd para has already made it clear that implementations can use newer versions of the spec.
Re comment #5 Pratul: The first para states that SML uses a profile of XML Schema 1.0 - which is not true any longer. Valentina : I tried to use the existing statements. In section 4.Schemas, the first paragraph reads : 'SML uses a profile of W3C XML Schema 1.0 [XML Schema Structures, XML Schema Datatypes] to define constraints on the structure of data in a model.' If this not true anymore than this section should be updated as well. Pratul: I also don't understand the phrase "and defines datatypes depending on definitions in XML 1.0" - the SML datatypes are based on XML Schema 1.0 and not XML 1.0 Valentina: Probably not the best description on how SML relates to XML 1.0. The only reference I could find on XML 1.0 in the SML document is on section 2.2 Terminology : Document is a 'A well-formed XML 1.0 document, as defined in [XML 1.0].' I am not quite sure how to put this into a normative dependency, I need suggestions. Pratul:I am not comfortable with the last para since we are not providing any guidance on how the "most recent versions" should be used. Valentina: This is the 'open ceiling' agreed to in the f2f. If more is to be said here I think we need some brainstorming on what this should would be. Pratul:Plus, the para appears to be redundant since the 2nd para has already made it clear that implementations can use newer versions of the spec. Valentina: Not identical. The last paragraph talks about ANY of the Normative references as defined in the References section; this is more than XML, XML Schema, Schematron and XPath. Second paragraph talks only about those 4
James comments on public list I agree with Pratul's comments regarding the last para. I'm not sure how best to reword the "investigat the possibility of applying" part. Something tells me MSM will have a suggestion. I suggest the pharase "most recent editions" be changed to "later versions" since the workd "version" is used in W3C specs, and because if we use the phrase "most recent" in might be interpreted as "the most recent but not 2nd most recent" by some.
*** Bug 4628 has been marked as a duplicate of this bug. ***
*** Bug 4629 has been marked as a duplicate of this bug. ***
Pratul : I have opened a new bug for removing the "profile" verbiage from Section 3. I think that the existing para 2 will suffice for the normative dependency section, and para 1 and para 3 can be removed Conforming implementations of this specification MUST support XML 1.0 [XML 1.0], XML Schema 1.0 [XML Schema Structures, XML Schema Datatypes], Schematron [ISO/IEC 19757-3] and XPath 1.0 [XPath 1.0]. However, the current specification does not impose any restrictions on using newer versions of the XML, XML Schema, Schematron or XPath specifications.
fixed by using Pratul's suggested content from comment #10
Looks good. Recommend approval by the WG
I'm happy with the change made to resolve this issue, as far as it goes, but I would like to propose two further changes: 1) In the running text, change all references to "XML 1.0", "XML Schema 1.0" (etc.) to read just "XML", "XML Schema", etc., without specific version numbers. 2) For However, the current specification does not impose any restrictions on using newer versions of the XML, XML Schema, Schematron or XPath specifications. read However, conforming implementations MAY additionally support later versions of the XML, XML Schema, Schematron or XPath specifications.
fixed