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 the normative parts in the data dictionary

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

I need to stress that this submission was supposed to be in complete relational xml structure as a message – the NIEM people selected to rip it apart to the element/attribute level.  It was never supposed to be made public and it was presented as an exercise to see if external standards could be utilized in NIEM – it failed miserably and we fought very hard to have it removed.  We lost the initial battle and it went out public – the good news is that they are putting in change management and governance that will allow a community of interest (OASIS TC?) to add/delete/modify these elements and attributes – so this can be fixed if the TC chooses to be involved…..


Should the TC elect to use NIEM as part of the RIM we can make the changes necessary to the NIEM Emergency Management Domain as necessary to support the EDXL standards – one of the key points we have discussed with NIEM is that the name  “National” in the name does not meet our needs internationally.  They are excited about the international concept and are willing to put up the governance to allow for international involvement…..




'We the unwilling, led by the unknowing have been doing the difficult with little for so long that we are now ready to tackle the impossible with nothing.' -- Local Fire communications reserve volunteer motto

From: Rex Brooks [mailto:rexb@starbourne.com]
Sent: Friday, September 28, 2007 9:37 AM
To: Renato Iannella; emergency@lists.oasis-open.org
Subject: Re: [emergency] HAVE comments - explicitly identifying the normative parts in the data dictionary


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]