[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
"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. --=_alternative 0059C84B88256DBB_= Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">From section 8.6.2 </font> <br> <br><font size=2 face="sans-serif">"The CompositeList element SHALL be omitted from</font> <br><font size=2 face="sans-serif">Packaging when no security encapsulations or composite multiparts are used".</font> <br> <br><font size=2 face="sans-serif">Have no idea from this statement. which link for packaging indicates</font> <br><font size=2 face="sans-serif">the simple part being used.</font> <br> <br><font size=2 face="sans-serif">What I was proposing was to change the description of composite element </font> <br><font size=2 face="sans-serif">to indicate that if there was only one constituent without encapsulation, then</font> <br><font size=2 face="sans-serif">mimetype does not correspond to composite mime types like multipart/signed, etc.</font> <br><font size=2 face="sans-serif">In this case mime/type of composite is same as constituent.</font> <br><font size=2 face="sans-serif">This is true where MSH acks do not carry a payload and can be sent as single mime parts.</font> <br> <br><font size=2 face="sans-serif">Reason I was heading in this direction was to see packaging as source</font> <br><font size=2 face="sans-serif">of content description and hence later on when we make schema changes</font> <br><font size=2 face="sans-serif">provide a link to simple part without gong through composite.</font> <br> <br><font size=2 face="sans-serif">Problem I see with dales suggestion is implementors looking to find a</font> <br><font size=2 face="sans-serif">"Packaging" element with packaingID from the ActionBinding, will </font> <br><font size=2 face="sans-serif">be returned with a SimplePart and will amount to some changes.</font> --=_alternative 0059C84B88256DBB_=--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]