CR013 proposed text

Here's some proposed text for the solution discussied today.

Changes:

6.8.2 Serialization as "application/x-www-form-urlencoded"

  Remove:

    Because the IRI Style constrains the instance data not to contain
    multiple children elements declared with the same local name,
    elements can be serialized in the request IRI with their local
    names unambiguously.

6.8.1.1 Construction of the request IRI using the {http location}
property

  Remove:

    An element MUST NOT be cited more than once within the {http
    location} property.

  Replace:

    When constructing the request IRI, each pair of curly braces (and
    enclosed element name) is replaced by the possibly empty single
    value of the corresponding element.

  By:

    When constructing the request IRI, each pair of curly braces (and
    enclosed element name) is replaced by the possibly empty single
    value of the corresponding element. If a local name appears more
    than once, the elements are used in the order they appear in the
    instance data.

  Replace:

    any other strings enclosed within single curly braces are a fatal
    error.

  By:

    local names not corresponding to an element in the instance data
    and any other strings enclosed within single curly braces are a
    fatal error.

4.2 IRI Style

  Remove:

    , and the attributes minOccurs and maxOccurs MUST have a value 0
    or 1

  Remove:

    The sequence MUST NOT contain multiple children elements declared
    with the same local name.

I believe that this implements:

1) remove minOccurs/maxOccurs
2) remove restriction on duplicate element names
3) removing the restriction in 6.1.1 (about the element MUST NOT be cited ...)
4) add some text matching up tokens with data in order
5) more tokens than data is a fatal error

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Monday, 27 February 2006 15:44:37 UTC