[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject
The latest documents should
be consistent with the wording below.
Patti From: Tim Grapes [mailto:tgrapes@evolutiontechinc.com] Sent: Mon 2/6/2006 2:02 PM To: 'Tim Grapes'; Aymond, Patti; 'Rex Brooks'; emergency@lists.oasis-open.org Cc: 'Lee Tincher' Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject All, Assuming that the DE standard reflects Rex’s recollection (pasted below), then I will remove the issue I submitted. I can live with this.
“…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.”
Thanks,
Tim Grapes Evolution
Technologies, Inc. Science and Technology Directorate/OIC Department of Homeland Security Office: (703)
654-6075
From: Tim
Grapes [mailto:tgrapes@evolutiontechinc.com]
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. Science and Technology Directorate/OIC Department of Homeland Security Office: (703)
654-6075
From: Aymond,
Patti [mailto:Patti.Aymond@iem.com]
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] All, IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE: IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE: -- -- -- -- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]