[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency-msg] Groups - EDXL-SitRep Data Dictionary V3.1 (EDXL-SitRep-Data-Dictionary_OASIS-DraftV3.1_09-03-2010.doc) uploaded
Re the following: Action item: EDXL-DE contains the “dateTimeSent”
(SEE highlighted excerpt below).
Are these equal and can this requirement be met through the DE? If so, refer to this requirement in the
“routing section” of the spec and state
that the DE “dateTimeSent” will be used to meet this requirement.
This is back to the fundamental question of how to use the DE. In RM we deliberately forced a level of coupling between the DE (or an alternative routing wrapper????) and its content. The forces the two to be kept together to provide full clarity. OTOH CAP and NIEM IEPs are entirely independent of the DE. They can be routed using a DE, but also stripped and used on their own after routing. The difficulty arises when a single DE is used with multiple content items if some can be stripped and some cannot. The appears to be an inconsistency in our design. Full encapsulation or content or integrated connection to content. This is a DE philosophical question that seems to be applied differently for different message content types. Which is right? R/s Gary On Sep 3, 2010, at 1:59 PM, tgrapes@evotecinc.com wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]