--- markup/xml/xmlcc/xmlcc-work.en.html 2007/11/15 10:03:02 1.15 +++ markup/xml/xmlcc/xmlcc-work.en.html 2007/11/26 12:38:53 1.16 @@ -18,7 +18,7 @@

manakai's XML Conformance Checking

-

Working Draft

+

Working Draft

This Version
@@ -222,6 +222,9 @@ xml-misc-warning. +
  • If there is an element type declaration whose Name +value is already declared, then raise an +xml-validity-error.
  • If attribute definition whose Name is xml:space has declared type different from (default|preserve), (default), or (preserve), then raise an @@ -245,6 +248,9 @@ #uniqattspec Well-formedness constraint: Unique Att Spec #NoExternalRefs Well-formedness constraint: No External Entity References #CleanAttrVals Well-formedness constraint: No < in Attribute Values +#vc-PEinGroup Validity constraint: Proper Group/PE Nesting +"For interoperability, if a parameter-entity reference appears in a choice, seq, or Mixed construct, its replacement text SHOULD contain at least one non-blank character, and neither the first nor last non-blank character of the replacement text SHOULD be a connector (| or ,)." +"For interoperability, an XML processor MAY at user option issue a warning when more than one attribute-list declaration is provided for a given element type, or more than one attribute definition is provided for a given attribute, but this is not an error." @@ Need detailed review, but maybe should be in parsing phase @@ -405,6 +411,72 @@
  • @@ specified, manakaiAttributeType (#ValueType Validity constraint: Attribute Value Type)
    • +
  • Let v be the value of the + attribute value of n.
    • +
  • Validate the n against the declared + type as following: +
    +
    ID_ATTR
    +
    +
      +
    1. Validate v as an + Name. If it fails, then raise an + xml-validity-error.
      2. +
    2. If ID v is defined, + then raise an + xml-validity-error.
      3. +
    +
    +
    IDREF_ATTR
    +
    +
      +
    1. Validate v as an + Name. If it fails, then raise an + xml-validity-error.
      2. +
    2. If ID v is NOT + defined, then raise an + xml-validity-error.
      3. +
    +
    +
    IDREFS_ATTR
    +
    @@
    +
    ENTITY_ATTR
    +
    +
      +
    1. Validate v as an + Name. If it fails, then raise an + xml-validity-error.
      2. +
    2. If Entity v is NOT + defined, then raise an + xml-validity-error.
      3. +
    +
    +
    ENTITIES_ATTR
    +
    @@
    +
    NMTOKEN_ATTR
    +
    +
      +
    1. Validate v as an + Nmtoken. If it fails, then raise an + xml-validity-error.
      2. +
    +
    +
    NMTOKENS_ATTR
    +
    @@
    +
    NOTATION_ATTR
    +
    v must be one of enumerated values. + If not, then raise an + xml-validity-error.
    +
    ENUMERATED_ATTR
    +
    v must be one of enumerated values. + If not, then raise an + xml-validity-error.
    +
    @@
    +
    +
    • +
  • If default is NOT #IMPLIED or #REQUIRED, then + raise an + xml-validity-error.
    • If n is an AttributeDefinition node
    @@ -429,6 +501,15 @@ check nc recusrively. +
  • If NOTATION_ATTR, enumerated values MUST + be declared. If not, then raise an + xml-validity-error.
    • +
  • If NOTATION_ATTR or ENUMERATED_ATTR, + values MUST all be distinct. If not, then raise an + xml-validity-error.
    • +
  • If NOTATION_ATTR on an EMPTY + element, then raise an + xml-validity-error.
    • If n is a CDATASection node
    @@ -590,6 +671,22 @@
  • If the childNodes list of n contains any nodes, they are in xml-well-formedness-error.
    • +
  • @@ At user option, an XML processor MAY issue a warning when a declaration mentions an element type for which no declaration is provided, but this is not an error.
    • +
  • @@ For compatibility, it is an error if the content model allows an element to match more than one occurrence of an element type in the content model.
    • +
  • @@ #vc-MixedChildrenUnique + Validity constraint: No Duplicate Types
    • +
  • @@ At user option, an XML processor MAY issue a warning if attributes are declared for an element type not itself declared, but this is not an error.
    • +
  • If there is more than one AttributeDefinition node + with attribute type ID in the + NamedNodeMap list contained in the + attributeDefinitions attribute of n, then raise an + xml-validity-error.
    • +
  • If there is more than one AttributeDefinition node + with attribute type NOTATION in the + NamedNodeMap list contained in the + attributeDefinitions attribute of n, then raise an + xml-validity-error.
    • +
  • "For interoperability, the same Nmtoken SHOULD NOT occur more than once in the enumerated attribute types of a single element type."
    • If n is an Entity node