[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-cppa] Discussion about support for simple part
-----Original Message-----
From: Himagiri.Mukkamala@sybase.com [mailto:Himagiri.Mukkamala@sybase.com]
Sent: Friday, October 10, 2003 9:21 AM
To: ebxml-cppa@lists.oasis-open.org
Subject: [ebxml-cppa] Discussion about support for simple part
Importance: Low
From section 8.6.2
"The CompositeList element SHALL be omitted from
Packaging when no security encapsulations or composite multiparts are used".
Have no idea from this statement. which link for packaging indicates
the simple part being used.
What I was proposing was to change the description of composite element
to indicate that if there was only one constituent without encapsulation, then
mimetype does not correspond to composite mime types like multipart/signed, etc.
In this case mime/type of composite is same as constituent.
This is true where MSH acks do not carry a payload and can be sent as single mime parts.
Reason I was heading in this direction was to see packaging as source
of content description and hence later on when we make schema changes
provide a link to simple part without gong through composite.
Problem I see with dales suggestion is implementors looking to find a
"Packaging" element with packaingID from the ActionBinding, will
be returned with a SimplePart and will amount to some changes.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]