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: [relax-ng] externalRef v external; notAllowed

> > One reason is that I find mixedCase keywords a bit strange.  Making this
> > change leaves us with only one mixed case keyword, "notAllowed", which,
> > my mind, now sticks out like a sore thumb.  But I'm not sure what to do
> > about it. Does this bother anybody else?  Alternatives that occurred to
> > were:
> We could use "forbidden" or "disallowed" or "illegal" or "invalid".

All of these raise the question of which is worse

- the ugliness of a single mixedCase keyword

- the possible confusion and decrease in ease of learning/use (for somebody
already familiar with the XML syntax) resulting from the XML syntax and the
compact syntax using a different name for the same thing


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

Powered by eList eXpress LLC