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] HAVE comments - explicitly identifying thenormative parts in the data dictionary

Title: Re: [emergency] HAVE comments - explicitly identifying the
Hi Renato,

I wish this were an isolated instance, but NIEM is not the first or only place that unfinished OASIS TC specification work has turned up before a TC or working group (OASIS-wide, not just our EM TC) have approved a final document as a standard. One of the problems we are all working through is that the process of standard-writing and the requirements of the end-products are both still moving targets, and the recent addition of a Conformance Section requirement in OASIS is a case in point.


At 1:18 PM +1000 9/28/07, Renato Iannella wrote:
On 28 Sep 2007, at 11:59, Lee Tincher wrote:

NIEM is based on the Dublin-Core metadata descriptions (which specify normative definitions) and it has a well defined set of Naming and Design Rules (NDR).   Why do we need to continually re-invent the wheel? 

NIEM 2.0 is a bit confusing!

I looked at the XSD for Emergency Management [1] Domain Schema and can see a lot of the HAVE and RM
elements/attributes already in there.

How did they get in there "so quick" when we have not finished?

Cheers...  Renato Iannella

[1] <http://www.niem.gov/niem-2/niem/domains/emergencyManagement/2.0/emergencyManagement.xsd>

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670

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