This is a much more complicated issue than can be discussed via
email. The issue has been worked literally for years, and now again another
effort to work with NIEM without them enforcing rules that do not work for this
domain and without breaking EDXL standards. We need to let the governance and
this “pilot” that is being put forth to play out. That governance is through a
partnership between OIC and FEMA with the knowledge and cooperation of OASIS
and others that have tracked this issue for so long. It may now get solved in
2.1 (or at least a path forward for governance and cooperation), but we’ll see.
Thanks,
Tim Grapes
Evotec
"When your work speaks for itself, don't interrupt"
- Henry J. Kaiser
I'm looking for one piece of XML - no xslt band-aiding and most
certainly NOT one standard for use - and another for publication in the IEPD.
The schema et al in the IEPD should be identical to what is being used in
actual production.
Original Message
--------
Subject: RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?
From: "Lee Tincher" <ltincher@evotecinc.com>
Date: Sun, July 12, 2009 8:38 pm
To: "'David RR Webber (XML)'" <david@drrw.info>
Cc: <emergency@lists.oasis-open.org>
Uhmmm – isn’t that exactly what I just said we are doing?
"I was wondering why that Frisbee was getting bigger - then
it hit me."
IMHO - that makes zero sense! Band-aiding like that is
nasty...
Obviously best outcome is to put the HAVE pieces in NIEM 2.1
Failing that - having an extended dictionary that includes the new
HAVE pieces - so we can generate two wantlists.xml automatically. One
that works with the SSGT - and one that works locally - and will include the
missing pieces as extensions.xsd into the subset schema.
What we need poste haste though is the exact list of missing
parts. I have the cross-reference dictionary between EDXL HAVE and
current NIEM 2.0 - that should work as pick list of things that need to be added.