--- markup/xml/xmlcc/xmlcc-work.en.html 2007/11/14 11:40:48 1.12 +++ markup/xml/xmlcc/xmlcc-work.en.html 2007/11/14 12:28:40 1.13 @@ -124,11 +124,33 @@

Parsing XML Document

@@ -204,6 +226,13 @@ fatal error) that is not classified to any other error category. @@ What errors fall into this category? +
xml-misc-recommendation
+
+

An + xml-misc-recommendation + will be raised if a SHOULD‐level requirement + in XML specification is not met.

+
xml-validity-error
A violation of validity constraint in XML document.
xml-well-formedness-error
@@ -260,7 +289,14 @@ then raise an xml-misc-warning.
  • @@ XML 1.1 support
    • -
  • @@ If U+000D, round-trip-error
    • +
  • If s contains a U+000D +CARRIAGE RETURN character, then +raise a +round-trip-error. +@@ We should not raise duplicate errors for U+000D +in attribute values. In addition, we should support a mode where +U+000D will be serialized as (so that no round-trip-error +will be raised).

    • The algorithm @@ -342,14 +378,30 @@ check nc recusrively. +

  • If nodeName attribute of n is + xml:space @@ or {xml namespace}:space ? + and value attribute of n is neither + default nor preserve, then it is an + xml-misc-error.
    • +
  • @@ xml:lang value is not a language tag [RFC 3066 or its + successor] or an empty string, then xml-misc-warning + (a "fact"-level error; not an XML error).
  • @@ specified, manakaiAttributeType
    • +
    If n is an AttributeDefinition node
    1. +
    2. If nodeName attribute of n is + xml:space @@ or {xml namespace}:space ? + and its declared type is different from (default|preserve), + (default), or (preserve), then raise an + xml-misc-error.
    3. For each node nc in the childNodes list of n,
        @@ -453,6 +505,21 @@
        1. Validate the nodeName attribute value as an NCName.
          2. +
        2. Follow the following substeps: +
            +
          1. If ownerDocument attribute of n is + null, then abort these substeps.
            2. +
          2. If documentElement attribute of the node + set to ownerDocument attribute of n is + null, then abort these substeps.
            3. +
          3. If nodeName attribute of the node set to + documentElement attribute of the node set to + ownerDocument attribute of n is + different from nodeName of n, + then raise an + xml-validity-error.
            4. +
          +
        3. Validate the publicId attribute value as a public identifier.
        4. If the systemId attribute value contains @@ -582,22 +649,27 @@
          If n is a ProcessingInstruction node
            -
          1. Validate the - target attribute value as an NCName.
            2. -
          2. If the target attribute value matches to - XML case-insensitively, then it is a +
          3. If the target attribute value matches to the string + xml in any case combination, then raise a xml-well-formedness-error.
            4. -
          4. Validate the - data attribute value as an XML character +
          5. Otherwise, validate the + target attribute value as an NCName.
            6. +
          6. Then, + validate + the data attribute value as an XML character data.
            7. -
          7. If the data attribute value contains - a string ?>, or starts with either - U+0009, U+000A, - U+000D, or U+0020 - character, then it is a - round-trip-error.
            8. +
          8. If the data attribute value contains a string + ?>, then raise a + xml-well-formedness-error.
            9. +
          9. If the data attribute value starts with either + U+0009 CHARACTER + TABULATION, U+000A LINE + FEED, U+000D CARRIAGE + RETURN, or U+0020 + SPACE character, then raise a + round-trip-error.
          10. If the childNodes list of n contains - any nodes, they are in + any nodes, then raise an xml-well-formedness-error.