[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-cppa] Discussion Invitation: Certificate cardinality edit andsemantics of empty content for ebXMLXXXBinding elements
The consensus at today's CPPA teleconference was to: 1. add a "minoccurs=0" qualification to the 2.0 schema for the Certificate element. and 2. adjust text in the specification to reflect this change, in the appendix for the schema and in the Certificate documentation section. I do not believe this will require any changes to the examples. Please voice any concerns promptly. We should probably re-affirm TC approval for the specification. Discussion whether to do this as an errata entry of just fix the text can also be posted to the list. ============== One other text addition is under study to specify what it means if the ebXML[Sender|Receiver]Binding element has no content. A proposal is that it would default to SOAP or maybe SOAP with attachments? Or should it just default to just sending the message according to the packaging and over the transport/transfer protocol selected, in accordance with one of the IETF specified modes? If you have a preferred interpretation for what is implied by empty content int the ebXMLXXXBinding element please advocate on the list!
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC