Small change, large consequences. Attributes then either accumulate
values (so foo="bar" foo="baz" results in a pseudo-normalized foo="bar
baz"), on the model of HTTP headers, or sequence begins to matter for
attributes (they become effectively simple-typed elements). If
sequence matters, existing APIs that assume that ordering doesn't
matter break. Canonicalization must take a different approach.
*shrug* I don't think this is a win. The element/attribute
distinction is currently interesting (attributes are unique-in-scope,
elements may reappear; attribute sequence isn't significant, element
sequence may); this would reduce it to "attributes are simple types;
elements may be complex."
Amy!
On Thu, 9 Dec 2010 14:22:28 +0000, Stephen Green wrote:
> Has anyone yet suggested the allowing of multiple attributes with the
> same name to enable a more succinct XML (more comparable to JSON)?
>
> Regards
>
> Stephen D Green
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe:
> subscribe:
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
