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] EDXL HAVE and NIEM 2.1 dictionary =?UTF-8?Q?alignment=3F?=


No - that is not correct - the wantlist.xml carries the components you are using from the EXISTING dictionary of NIEM collection of "stuff".

See my reply on what goes into an IEPD.  The idea is that an exchange designer should maximize reuse of items that are already in NIEM - and then only define domain specific new peices in your XSD that are not currently in NIEM - outside of the wantlist.xml items. This is exactly what we have in EDXL HAVE already - bits that are in the NIEM - and bits that OASIS has defined.

What I've done for CAM is take the NIEM Access database for v2.0 - convert it into an XML format for the dictionary and properties - and then written xslt - that will compare the CAM template of your exchange XSD (in this case EDXL) to that NIEM XML dictionary and build the wantlist.xml for you. 

What NIEM teaches is doing this manually online using the SSGT to search and find the matching parts. Needless to say that is a tedious and slow process!

Fortunately the SSGT includes ability to save and then upload wantlist.xml - so I'm merely automating this all - so you can simply upload the wantlist.xml that CAM created instead - check that it works OK - and then you are done - minutes instead of days of work!

Hope that is clearer now.
Thanks, DW

-------- Original Message --------
Subject: RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?
From: "Gary Ham" <hamgva@cox.net>
Date: Wed, July 15, 2009 7:15 am
To: "'David RR Webber (XML)'" <david@drrw.info>
Cc: <emergency@lists.oasis-open.org>, "'Timothy Grapes'"
<tgrapes@evotecinc.com>, "'Lee Tincher'" <ltincher@evotecinc.com>

My understanding of the IEPD process is that a wantlist is required only for brand new elements.  Reuse of an approved external standard does not require a wantlist. In fact it would be confusing because it would appear that we are submitting individual HAVE elements for inclusion in the NIEM vice HAVE as a whole. The wantlist is for LOCAL data structures that have not been standardized and need to be. We do not have to create a wantlist for the HAVE standard.  Just get it approved as an external standard and define a NIEM adapter.
You may be confused because the subschema generator uses the same “wantlist” format for storing the items you need out of NIEM prior to generating the one ore more subset schemas that you build in order back the specific (separately name spaced) reference schema that you use for your exchange schema.  But, you do not need to submit a “wantlist” separately for elements that the subschema generator can build for you. Just for the new stuff. And approved external standards are not new stuff. In fact, the HAVE schema with its adapter is actually just another subset schema as far as the IEPD process goes.
The larger question is alignment of our RIM with NIEM, which is a RIM of its own.  We may need to think about something there, because there could be value in aligning basic constructs. But my warning is simple:  “there be monsters lurking!!!!”  It is not simple at all.

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