OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [ubl-ndrsc] Elements vs. attributes: discussion kickoff

Title: RE: [ubl-ndrsc] Elements vs. attributes: discussion kickoff

My position on this is use attributes only for document level information. This means that for the most part only built-in document level attributes such as xml:lang, id and idref should be used and elements should be used for all other transmitted data.  My understanding is there are parsing, ordering, and performance issues surrounded with attributes.  I also believe that by enforcing attributes at the document level, we will provide clarity, avoid confusion, and enable better structuring.

Here, here! My tendency would be to throw down the gauntlet and ask: why ever use attributes? Most of the reasons raised by Gunther are no longer relevant now that XSD lets elements do most of what attributes can (i.e. be simple types, hold enumerations, have default values, etc.). Using both elements and attributes is just confusing for the user, developer and others, poorly supported by authoring environments, etc. I would suggest that use of attributes be restricted to real metadata: identifiers, links, etc. as proposed by Mark.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC