W3C home > Mailing lists > Public > public-sml@w3.org > December 2007

[Bug 4774] definitional schema documents should be preferentially used over all other sources when validating instances

From: <bugzilla@wiggum.w3.org>
Date: Tue, 04 Dec 2007 16:21:40 +0000
To: public-sml@w3.org
Message-Id: <E1IzaWi-0007Mf-VE@wiggum.w3.org>


------- Comment #9 from sandygao@ca.ibm.com  2007-12-04 16:21 -------
1. Not sure whether this is intentional. Seems many spaces are inserted into
the pseudo schema in section 4.1. Most elements are indented further than
before. And
            <documentAlias/> * should be
            <documentAlias/> +
(I probably had this wrong in the proposal.)
2. In section 4.4, for "schema-incomplete". "A required schema is not included
..." Maybe it's more accurate to say "Some required schema documents *may* not
be included ...".
3. In the following paragraph "... distinguish between these two cases and that
is not always ...". Suggest to change "and" to "because".
4. In the same paragraph "... then, for the instance to be valid, its schema
definition documents and ...". The goal here is not "for the instance to be
valid". Maybe "... then schema validity of schema definition documents and
instances documents depend only on built-in components and components from
5. Before the first example in section 4.4: "whose alias specified in its alias
attribute" -> "whose aliases are specified in its aliases attribute". And "...
to be assessed against this set of schemas is specified ..." -> "... to be
assessed against this set of schemas *are* specified ..."
6. Before the second example: "The defaultSchema can be used cover ..." -> "The
defaultSchema can be used *to* cover ..."
7. Section 5.5 doesn't implement the "Processors are not required to support
<schemaBindings>" portion of the proposal. Maybe it should start with something
like "SML-IF consumers MAY choose to ignore <schemaBindings> the element when
it is present in an SML-IF document, in which case the SML-IF consumer SHOULD
make its invoker aware of this situation. The rest of this section applies to
processors who choose to process the <schemaBindings> element."
8. In the IF schema.
  <xs:element name="schemaBindings"/> should be
  <xs:element name="schemaBindings" type="smlif:schemaBindingCollectionType"/>
9. In IF schema,
      <xs:element ref="ns1:namespaceBinding"/> should be
      <xs:element ref="smlif:namespaceBinding" minOccurs="0"
10. Also in IF schema:
  <xs:element name="namespaceBinding" type="ns1:namespaceBindingType"/> should
  <xs:element name="namespaceBinding" type="smlif:namespaceBindingType"/>
11. IF schema:
    <xs:attribute name="namespace" type="xs:NCName" use="required"/>
    <xs:attribute name="alias" use="required"> should be
    <xs:attribute name="namespace" type="xs:NCName" use="optional"/>
    <xs:attribute name="aliases" use="required">
12. It's not clear to me whether "namespaceBindingType" should also allow
extension points using wildcards.
13.   <xs:element name="defaultSchema"/> should be
  <xs:element name="defaultSchema" type="smlif:defaultSchemaType"/>
14. defaultSchemaType should be:
  <xs:complexType name="defaultSchemaType" mixed="false">
      <xs:element ref="smlif:namespaceBinding" minOccurs="0"
      <xs:any namespace="##other" processContents="lax" minOccurs="0"
    <xs:anyAttribute namespace="##other" processContents="lax"/>
15. Maybe it's helpful to have a default value for "schemaComplete":
    <xs:attribute name="schemaComplete" type="xs:boolean"/> becomes
    <xs:attribute name="schemaComplete" type="xs:boolean" default="true"/>
Received on Tuesday, 4 December 2007 16:21:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:56:08 UTC