[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] Would a webinar make sense for everyone on NIEM,EDXL and CAM?
If there's insufficient time for the TC to schedule a presentation, I can suggest it for the EM-RIM SC as a way to integrate our thinking wrt NIEM. Cheers, Rex At 7:44 AM -0700 7/15/09, David RR Webber \(XML\) wrote: >It suddenly hit me - I'm doing a presentation today internally here >on developing IEPDs and the CAM toolkit - and I'm also scheduled to >present this at the NIEM expo' in Baltimore in September. > >What I think makes sense is for me to use the free Adobe webinar >service that OASIS has to show this same slide deck - but morphed to >EDXL HAVE. > >I think we'll all be on the same page then - and I can show you all >the details much more easily than trying to explain it in email! > One hour probably equals 1000 emails! > >If we schedule this for a couple of weeks time - depending on >peoples availability...? > >Thoughts? > >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> > >#wmMessage #WMMESSAGE p.MSOAUTOSIG {mso-style-priority:99;} >#wmMessage #WMMESSAGE li.MSOAUTOSIG {mso-style-priority:99;} >#wmMessage #WMMESSAGE div.MSOAUTOSIG {mso-style-priority:99;} >#wmMessage #WMMESSAGE p {mso-style-priority:99;} #wmMessage >#WMMESSAGE span.E-MAILSIGNATURECHAR {mso-style-priority:99;} >#wmMessage #WMMESSAGE p.MSOCHPDEFAULT1 {mso-style-priority:99;} >#wmMessage #WMMESSAGE li.MSOCHPDEFAULT1 {mso-style-priority:99;} >#wmMessage #WMMESSAGE div.MSOCHPDEFAULT1 {mso-style-priority:99;} >#wmMessage /* Font Definitions */ @font-face {font-family:Tahoma; >panose-1:2 11 6 4 3 5 4 4 2 4;} #wmMessage @font-face >{font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4;} #wmMessage >@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} >#wmMessage /* Style Definitions */ p.MsoNormal, #wmMessage >li.MsoNormal, #wmMessage div.MsoNormal {margin:0in; >margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New >Roman";} #wmMessage p.MsoAutoSig, #wmMessage li.MsoAutoSig, >#wmMessage div.MsoAutoSig {mso-margin-top-alt:auto; >margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; >font-size:12.0pt; font-family:"Times New Roman";} #wmMessage p >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage p.msochpdefault, >#wmMessage li.msochpdefault, #wmMessage div.msochpdefault >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage p.msochpdefault1, >#wmMessage li.msochpdefault1, #wmMessage div.msochpdefault1 >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage p.msochpdefault2, >#wmMessage li.msochpdefault2, #wmMessage div.msochpdefault2 >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage span.e-mailsignaturechar1 >{font-family:Calibri;} #wmMessage p.msochpdefault3, #wmMessage >li.msochpdefault3, #wmMessage div.msochpdefault3 >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage p.msochpdefault11, >#wmMessage li.msochpdefault11, #wmMessage div.msochpdefault11 >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage p.msochpdefault21, >#wmMessage li.msochpdefault21, #wmMessage div.msochpdefault21 >{mso-margin-top-alt:auto; margin-right:0in; >mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; >font-family:"Times New Roman";} #wmMessage span.EmailStyle34 >{mso-style-type:personal; font-family:Calibri; color:#1F497D;} >#wmMessage span.EmailStyle350 {mso-style-type:personal; >font-family:Calibri; color:#1F497D;} #wmMessage span.EmailStyle36 >{mso-style-type:personal; font-family:Calibri; color:#1F497D;} >#wmMessage span.EmailStyle37 {mso-style-type:personal; >font-family:Calibri; color:#1F497D;} #wmMessage span.EmailStyle38 >{mso-style-type:personal; font-family:Arial; color:navy;} #wmMessage >span.EmailStyle39 {mso-style-type:personal; font-family:Calibri; >color:#1F497D;} #wmMessage span.EmailStyle40 >{mso-style-type:personal; font-family:Arial; color:navy;} #wmMessage >span.EmailStyle42 {mso-style-type:personal-reply; font-family:Arial; >color:navy;} #wmMessage @page Section1 {size:8.5in 11.0in; >margin:1.0in 1.25in 1.0in 1.25in;} #wmMessage div.Section1 >{page:Section1;} >David, > >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. > >Respectfully, > >Gary > > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. Follow this link to all your TCs in OASIS at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- 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]