Re: [emergency] Breakdown of contentObject

[Michelle Raymond <michellearaymond@gmail.com>]

Tim, Gary, ...

Personally, I'm not wed to the names <messageSenderRole> and
<messageRecipientRole> in the, formerly named, <messageElement>.  Make
suggestions for alternatives.

As to the definitions, I see the definitions as extremely similar, if
not identical to that of <senderRole> and <recipientRole> within the
<EDXLDistribution>. The difference is a matter of scope.  The
<senderRole> and <recipientRole> apply to the entire distribution
"package" scope.  The <messageSenderRole> and <messageRecipientRole>
apply to meta and content data of the <contentObject> scope.

Perhaps the best way to differentiate the two sets would be in the
examples given within the definitions.  As such, suggestions for
appropriate roles in each of the cases are needed.

- Michelle

On 8/9/05, Ham, Gary A <hamg@battelle.org> wrote:
> Very Much concur with Tim's suggestion.
> 
> Gary A. Ham
> Senior Research Scientist
> Battelle Memorial Institute
> 540-288-5611 (office)
> 703-869-6241 (cell)
> "You would be surprised what you can accomplish when you do not care who
> gets the credit." - Harry S. Truman
> 
> 
> -----Original Message-----
> From: Timothy Grapes [mailto:tgrapes@evolutiontechinc.com]
> Sent: Tuesday, August 09, 2005 1:54 PM
> To: michellearaymond@gmail.com
> Cc: emergency@lists.oasis-open.org
> Subject: Re: [emergency] Breakdown of contentObject
> 
> 
> Michelle,
> 
> I waited too long for an opening to comment, and then didn't have the
> heart after you started discussing a follow-up date...!
> 
> I recommend we change the name of the following elements:
> From <messageSenderRole>, To "originalSource" or "originatorRole" From
> <messageRecipientRole> To "consumerRole"
> 
> I know this is semantics but it goes to clarity and simplicity for the
> end user (developer).  On the last call I struggled to understand the
> purpose of <messageElement>.  Then couldn't understand the reason for
> sender and recipient roles in both the <EDXLDist> segment and the
> <messageElement> (and the definitions are nearly identical).  I
> recommend we change the names and write better definitions for these
> elements to reflect their real purpose.
> 
> Thanks,
> Tim
> --
> Tim Grapes
> DHS Disaster Management
> Mount Weather:  (540) 542-3239
> Mobile:         (703) 304-4829
> tgrapes@evolutiontechinc.com
> tim.grapes@associates.dhs.gov
> 
> 
> On Tue, August 9, 2005 12:18 pm, michellearaymond@gmail.com said:
> > <contentObject>
> >   <contentKeyword> (optional - Only 1)
> >   <keyXmlContent>  (use only in case only xmlObject)
> >   <messageSenderRole> (optional - Multiple)
> >   <messageRecipientRole> (optional - Multiple)
> >   <confidentiality> (optional - Only 1)
> >   <description> (optional - Only 1)
> >   <mimeType> (required - Only 1)
> >   <size>(optional - Only 1
> >   <digest> (optional - Only 1)
> >   choice (required - only 1)
> >    <uri>
> >    <derefUri>
> >    <namespacedXMLcontent>
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
>