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 tocontentObject
Excuse me, Please, if my memory has turned to
swiss cheese, but I would have sworn we agreed
that EDXL-DE could have multiple contentObjects
with one and only one payload each, and one and
only one DistributionType, so that no
contentObjects could be of a type different than
the DistributionType.
Cross-eyed with Alzheimer's,
Rex
At 2:17 PM -0500 1/30/06, Tim Grapes wrote:
>Whoops - somehow I missed that change along the
>way. In fact, during the most recent review
>(1/16/06) Elysa asked me whether a related issue
>I submitted was satisfied and I responded "yes"
>based on the committee decision to install that
>business rule. Thus, this means that the issue
>I submitted in fact has not been addressed� In
>response to this issue, the business rule was
>added stating that the DE may contain only one
>contentObject, to eliminate the related
>complexities.
>
>I don't want another 60-days, but now don't understand the resolution offered.
>Thanks,
>Tim
>
>------------------
>(Submitted 11/29/05)
>ISSUE 1 - Multiple payloads / distribution types
>
>DE can carry multiple payloads, and I just now
>see a change that shows that DistributionType
>can be one or MANY as it should be (so that
>different payloads in the same DE may have
>different distrType). E.g. A DE with 2
>payloads - one payload may be a "response" and
>the other be a "request". This is a valid
>requirement, but then requires a way to
>associate distibutiontype(s) with different
>payloads. There are also other business needs
>to relate together multiple payloads within the
>same distribution.
>
>OPTIONS:
>1- Formalize a business rule where payloads must
>always have the same DistributionType.
>Otherwise, separate messages must be created for
>each, or
>
>2- How to associate things to payloads? Perhaps
>add an element to the DE contentObject segment
>called something like "contentID", providing a
>unique way to identify each payload?
>
>ISSUE 2 - Incident Identifier and Description 1 or many?
>
>Same issue as above. If the business rule above
>is implemented, then multiple payloads within a
>DE need to be related to the same incident.
>Otherwise, need a way to relate Incident ID's
>and Desc's with each payload (the
>"contentObject" thought above?).
>-------------------
>
>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
><mailto:tgrapes@evotecinc.com>tgrapes@evotecinc.com<mailto:tgrapes@evolutiontechinc.com>
><mailto:tim.grapes@associates.dhs.gov>tim.grapes@associates.dhs.gov
>
>
>From: Aymond, Patti [mailto:Patti.Aymond@iem.com]
>Sent: Monday, January 30, 2006 1:19 PM
>To: Tim Grapes; Rex Brooks; emergency@lists.oasis-open.org
>Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject
>
>Tim,
>
>Actually that business rule got changed along
>the way. As it stands now, each DE can have 0 or
>more Content Objects, and each Content Object
>can have 0 or more payloads.
>
>I personally think is should be each DE can have
>1 or more Content Objects, and each Content
>Object must have exactly one payload. IMHO
>
>Patti
>
>
>From: Tim Grapes [mailto:tgrapes@evolutiontechinc.com]
>Sent: Mon 1/30/2006 8:12 AM
>To: 'Rex Brooks'; Aymond, Patti; emergency@lists.oasis-open.org
>Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject
>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
>
>
>