[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] keyXMLContent Versus embeddedXMLContent
On 23 Nov 2005, at 14:33, Ellis, David wrote:
I am assuming, and again, I could be wrong, was that the DE's role is for distribution.
Hence, all the DE elements are used for that purpose. The <contentObject>s are intended
for the "end user" recipient(s). That is, any DE processor in the chain will be parsing the DE elements
to make decisions on routing. When it gets to the recipients, they will look at the contentObject and
do whatever they are supposed to do.
The reason for this is that we (at the DE level) have no knowledge of what is inside the <contentObject>s
and hence, we cannot make any reference to them in the specification that may influence distribution.
Of course, this does not stop someone from building a CAP/EDXL-DE processor that understands both.
But from the EDXL-DE specs point-of-view, we are only limited to the elements we define (and control).