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] Emergency Management Vocabulary alignments?


Thanks Don,

This is truly good news.

Cheers,
Rex

At 12:11 PM -0500 2/14/08, Ponikvar, Donald <CTR> wrote:
>Interesting discussion.  FYI, I have been invited to attend the next
>meeting of the NBAC here in Washington DC on 28-29 Feb. 
>
>The DHS Domestic Nuclear Detection Office (DNDO) has formally adopted
>EDXL DE (along with CAP 1.1) as part of their overarching data model.
>We have been asked by DHS to document our messaging approach in the
>approved NIEM IEPD format, for submission to the DHS NIEM office for
>consideration as an extension to the NIEM core.  That work is well
>underway.
>
>So yes, there are some initial efforts to gain recognition of the OASIS
>standards as part of the DHS NIEM implementations.  We are actually
>fielding a messaging system through our Southeast Transportation
>Corridor Pilot effort, and it will use the messaging protocols (with
>OASIS standards) that we are submitting to NIEM.  This exercise involves
>nine States and the District of Columbia, and will provide some
>real-world benchmarks for how well it all works together.  We anticipate
>initial capabilities in the April-May time frame, with a full
>demonstration in the Fall.
>
>Just an encouraging word that SOME folks at DHS are hearing the gospel
>message.
>
>Don Ponikvar
>
>Donald R. Ponikvar, PhD
>SETA Support, Mission Management Directorate
>DHS/Domestic Nuclear Detection Office
>Washington, DC  20528
>
>voice:  202-254-7530
>fax:  202-254-7751
>Blackberry:  202-368-4922
>
>
>-----Original Message-----
>From:
>emergency-return-835-Donald.Ponikvar=associates.dhs.gov@lists.oasis-open
>.org
>[mailto:emergency-return-835-Donald.Ponikvar=associates.dhs.gov@lists.oa
>sis-open.org] On Behalf Of Timothy Grapes
>Sent: Thursday, February 14, 2008 11:14 AM
>To: 'David RR Webber (XML)'
>Cc: 'Lee Tincher'; Vandame, Richard; emergency@lists.oasis-open.org
>Subject: RE: [emergency] Emergency Management Vocabulary alignments?
>
>David,
>You got it.  I don't know about future plans.  Although they do have a
>formal template for domain content submission, there is no current
>governance to deal with submissions.  I understand they are trying to
>stand
>up the NBAC (NIEM Business Architecture Committee) again.  NIEM
>governance
>would be their responsibility - but you are right, ownership and process
>outside of NIEM is also key. 
>
>Thanks,
>
>Tim
>
>-----Original Message-----
>From: David RR Webber (XML) [mailto:david@drrw.info]
>Sent: Thursday, February 14, 2008 11:04 AM
>To: Timothy Grapes
>Cc: 'Lee Tincher'; 'Vandame,Richard'; emergency@lists.oasis-open.org
>Subject: RE: [emergency] Emergency Management Vocabulary alignments?
>
>Tim,
>
>OK got it. 
>
>The NIEM is just a giant vocabulary intended to be the base definitions
>for
>building conforming message exchanges from.
>
>So - no surprise they shredded OASIS messages into their base
>components.
>In future probably best to submit just the bsse definitions!  They may
>have
>made changes to names of things to make sure they are fully NDR
>compliant.
>Again - that's something we can make sure of ahead of time too - but
>would
>be best to get agreement with NIEM on conformance and their signoff.
>
>The current NIEM V2.0 is from June 2007.  My guess is that at some point
>NIEM V3.0 work will occur.  They do have a formal submission process for
>domain stuff.  The ownership and process for that though - obviously
>that's
>the trick here - to ensure our stuff is incorporated, corrected and
>updated
>for that.  Would be nice also - since its domain, not core or universal
>definitions - if we could get those updated and corrected sooner than
>that...
>
>Some sleuthing into current contact points and so on.
>
>DW
>
>>  -------- Original Message --------
>>  Subject: RE: [emergency] Emergency Management Vocabulary alignments?
>  > From: "Timothy Grapes" <tgrapes@evotecinc.com>
>>  Date: Thu, February 14, 2008 10:41 am
>>  To: "'Vandame,  Richard'" <Richard.Vandame@dhs.gov>,  "'David RR
>Webber
>>  \(XML\)'" <david@drrw.info>,  <emergency@lists.oasis-open.org>
>>  Cc: "'Lee Tincher'" <ltincher@evotecinc.com>
>>
>>  Rich is correct - some EDXL messages were the first non-Justice
>content
>>  entered into NIEM, before harmonization processes were defined.  At
>that
>>  time, (to our surprise) the messages were broken apart and the
>elements
>put
>>  in the EM domain as well as in core.  That's when we realized NIEM
>wasn't
>>  addressing standard messages.  The content is now old and incorrect
>(to
>what
>>  degree I don't know).
>>
>>  Since that time (2 years ago) there has been no governance, process or
>>  funding to deal with this.  Though we forwarded a detailed proposal
>with
>>  DHS-OIC and NIEM for EDXL alignment (EDXL consume and maintain NIEM as
>a
>>  common data dictionary), I don't think it has moved forward.  That
>proposal
>>  called for evolution into NIEM-compliant EDXL messaging standards
>through
>>  re-use of NIEM data dictionary components, which are then evaluated as
>NIMS
>>  "approved" messaging standards.  The intended result is grant language
>and
>>  program alignment such that implementation of EDXL messaging standards
>by
>>  any entity results in the sending and receiving system deemed as NIMS,
>NIEM,
>>  OIC-program and OASIS compatible. 
>>
>>  Thanks,
>>
>>  Tim Grapes
>>  Evolution Technologies, Inc.
>>  Office:  (703) 654-6075
>>  Mobile:  (703) 304-4829
>>  tgrapes@evotecinc.com
>>  http://www.evotecinc.com/
>>
>>  -----Original Message-----
>>  From: Vandame, Richard [mailto:Richard.Vandame@dhs.gov]
>>  Sent: Thursday, February 14, 2008 10:08 AM
>>  To: David RR Webber (XML); emergency@lists.oasis-open.org
>>  Subject: RE: [emergency] Emergency Management Vocabulary alignments?
>>
>>  If I remember correctly, EDXL information was entered into NIEM
>sometime
>>  back.  Some of it is incorrect, but no one was able to get it changed.
>>
>>  Anyone else?
>>
>>  Rich
>>
>>  Richard Vandame
>>  Program Specialist
>>  Standards & Technology Branch
>>  Incident Management Systems Integration Division
>>  DHS/FEMA
>>  office: 202-646-7666
>>  BB: 202-412-9072
>>  richard.vandame@dhs.gov
>>
>>  -----Original Message-----
>>  From:
>emergency-return-829-Richard.Vandame=dhs.gov@lists.oasis-open.org
>>
>[mailto:emergency-return-829-Richard.Vandame=dhs.gov@lists.oasis-open.or
>>  g] On Behalf Of David RR Webber (XML)
>>  Sent: Thursday, February 14, 2008 9:27 AM
>>  To: emergency@lists.oasis-open.org
>>  Subject: [emergency] Emergency Management Vocabulary alignments?
>>
>>  I just found out that the NIEM V2.0 has a whole domain for Emergency
>>  Management that supports the National Incident-Based Reporting System
>>  (NIBRS).
>>
>>  You can use NIEM online tools to explore these:
>>
>>   http://ncsconline.org/niemwayfarer  (best)
>>
>>  and also
>>
>>   http://niem.gtri.gatech.edu/niemtools/ssgt/SSGT-SearchSubmit.iepd
>>
>>  There's a whole raft of information for emergency stuff - that we have
>-
>>  that is duplicative - such as vehicle, bed, etc.
>>
>>  I see others have already been here ahead of me.
>>
>>  So for example we have bed, vehicle, etc information - searching in
>>  Wayfarer shows those.
>>
>>  Bed search results:
>>
>>  Matching Elements
>>  em:AdditionalCapacity24HrQuantity
>>  em:AdditionalCapacity72HrQuantity
>>  em:AvailableQuantity
>>  em:BaselineQuantity
>>  em:BedCapacity
>>  em:BedCategoryCode
>>  em:Capacity
>>  em:CapacityStatusCode
>>
>>  Obviously we also have these in our schema.
>>
>>  Now of course the NIEM is a giant boat anchor of a XSD fur ball.
>>
>>  However - I could see the case for aligning to the dictionary - so
>that
>>  names/definitions are equivalent - so you have published 100%
>  > correspondence for interoperability.
>>
>>  This may be as simple as producing a spreadsheet with OASIS item and
>>  then the NIEM equivalent item... have we done that already?
>>
>>  Of course one may want to create subset schema that include only those
>>  definitions extracted from the NIEM xsd fur ball - and built as a
>>  standalone xsd that is maintained independently thru OASIS.
>>
>>  Is that essential what we have done?
>  >
>>  Thoughts?
>>
>>  Just coming up the learning curve here!
>>
>>  Thanks, DW
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe from this mail list, you must leave the OASIS TC that
>>  generates this mail.  You may a link to this group and all your TCs in
>>  OASIS
>>  at:
>>  https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>>
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe from this mail list, you must leave the OASIS TC that
>>  generates this mail.  You may a link to this group and all your TCs in
>OASIS
>>  at:
>>  https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and 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]