MHonArc v2.5.0b2 -->
emergency message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject
Hi Elysa and TC members,
I wanted to clarify Elysa's timetable below. The TC is currently getting the document ready for a 15-day public review. This
review will be limited to only those items changed since the 60-day public review. Hence the need for a red-lined/change-marked
copy.
Once the 15-day review is completed, the TC will need to consider any/all comments received and log them, along with their
disposition.
The committee will then vote to a) approve as committee spec and b) submit for OASIS standard vote. That ballot will run for 7
days.
Since standard submissions must be in by the 15th of the previous month, this timetable means that the earliest EDXL-DE can be
approved would be 30 April 2006.
Regards,
Mary
> >
> >At 8:47 AM -0600 1/30/06, Elysa Jones wrote:
> >>As to where we are with the documentation to OASIS, we still must
> >>1) populate the Revision History table (I am working on
> that now and
> >>should have something for the group to review by COB tomorrow); 2)
> >>Make the correction to the DOM as per Dave Ellis comment on
> the list
> >>this weekend (action: Patti) and 3) If we agree on the
> list that the
> >>recommended change as further discussed this weekend on the list by
> >>Dave and below by Tim, then we can make this change. We
> need to get
> >>these final - FINAL changed in by 2/1 if possible and vote
> by CoB that
> >>day. This will keep us on the same schedule for an OASIS wide vote
> >>the end of March. Stay tuned for a meeting to be called for a vote
> >>2/1. If you are a voting member and cannot be available
> during some
> >>part of that day (Wed), please let me know. Thanks, Elysa
> >>
> >>At 08:12 AM 1/30/2006, you wrote:
> >>>All,
> >>>
> >>>Just to make sure we are clear, the incidentID and Description are
> >>>already included in the ContentObject as optional. Being
> optional,
> >>>an incident may or may not be related to the content, and the spec
> >>>contains a business rule that each DE may contain only one
> content object.
> >>>
> >>>Mark is suggesting addition of an optional incidentKeyword to
> >>>classify the incident, which is not a complicated request.
> I think
> >>>the decision really comes down to where we draw the line
> and get the
> >>>DE published, and where we begin considering additional
> requests for the next version.
> >>>
> >>>Regards,
> >>>
> >>>Tim Grapes
> >>>Evolution Technologies, Inc.
> >>>Disaster Management egov Initiative
> >>>Science and Technology Directorate/OIC Department of Homeland
> >>>Security
> >>>Office: (703) 654-6075
> >>>Mobile: (703) 304-4829
> >>>tgrapes@evotecinc.com
> >>>tim.grapes@associates.dhs.gov
> >>>
> >>>
> >>>