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

 


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng message

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


Subject: Re: Issue: <element name="foo"/> v <attribute name="foo"/>



> I don't want to allow <element name="foo"?> to have arbitrary attributes.

Do you mean you are happy for it to have arbitrary children but not 
arbitrary attributes? If so, why?

The argument for the status quo that I find strongest is that whereas I 
think it is obvious to a (human) reader that

  <attribute name="foo"/>

matches an attribute foo with any value, it is not obvious what

  <element name="foo"/>

means: they might guess it means any of

- text only
- anything
- empty

James







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


Powered by eList eXpress LLC