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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

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

Subject: Re: [emergency] Groups - EDIT of emergency-CAPv-1.1

Why is simpletype naming being re-inserted into the schema?

on another tangent...

I also want to bring up (again) the problem with using named enumeration
types for schema elements like category. If we were using a
lookup/reference (in the form of a secondary XML file) table as I had
previously suggested, the schema would not have to be modified every
time to include values like CBRN. 

It also encourages developers not to take shortcuts by hardcoding the
categories into their applications.

Done the right way, any added category would only mean a change to a
lookup table (be it plaintext, stored in a db, whatever in terms of the
user's application space), with no schema or server/client code
modification required.

Instead, the only current solution if one wants to remain within spec is
to flag the category as other and then wait until a new category can be
included in the spec.

I realize the argument against this is that people can simply expand the
category list making theirs incompatible with someone else's, but that
is easily dealt with - include the lookup table as part of the spec and
have parsers flag & categorize unknown content as... 'Unknown' or
'Other' (or simply expand their local lookup table on the fly). :-P


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