RE: [ebxml-msg] Additional feedback to ebMS2.0 and CPPA

[Dale Moberg <dmoberg@cyclonecommerce.com>]

Regarding item 4 below: 
minOccurs on SecurityDetails and Certificate are now both zero.
Fixed in
http://www.oasis-open.org/committees/ebxml-cppa/schema/cpp-cpa-2_0b.xsd
and being voted on currently for OASIS approval.

Thanks
Dale Moberg

<element name="PartyInfo">
- <complexType>
- <sequence>
  <element ref="tns:PartyId" maxOccurs="unbounded" /> 
  <element ref="tns:PartyRef" maxOccurs="unbounded" /> 
  <element ref="tns:CollaborationRole" maxOccurs="unbounded" /> 
  <element ref="tns:Certificate" minOccurs="0" maxOccurs="unbounded" /> 
  <element ref="tns:SecurityDetails" minOccurs="0" maxOccurs="unbounded"
/> 
  <element ref="tns:DeliveryChannel" maxOccurs="unbounded" /> 
  <element ref="tns:Transport" maxOccurs="unbounded" /> 
  <element ref="tns:DocExchange" maxOccurs="unbounded" /> 
  <element ref="tns:OverrideMshActionBinding" minOccurs="0"
maxOccurs="unbounded" /> 
  </sequence>
  <attribute name="partyName" type="tns:non-empty-string" use="required"
/> 
  <attribute name="defaultMshChannelId" type="IDREF" use="required" /> 
  <attribute name="defaultMshPackageId" type="IDREF" use="required" /> 
  </complexType>
  </element>

-----Original Message-----
From: iwasa [mailto:kiwasa@jp.fujitsu.com]
Sent: Monday, October 28, 2002 11:32 PM
To: ebXML Messaging
Subject: [ebxml-msg] Additional feedback to ebMS2.0 and CPPA


All,

Here are some feedback to ebXML MS2.0 spec.
These are came from ECOM ebXML interoperability
activity that Fujitsu is one of the leading vendor.

1. xlink:type should be REQUIRED.
   In detail, XLINK specification defines that xlink:type
   to be REQUIRED, but ebXML MS spec defines that
   SOAPBody-Manifest-Reference-xlink:type
   is OPTIONAL. So ebXML MS spec should
   make it mandatory to conform to XLINK.

2. The format of start parameter in the sample of
    section "2.1.2 Message Packaging" is wrong.
    Currently the spec has:
         start=messagepackage-123@example.com
    But it should be :
        start="<messagepackage-123@example.com>"
    The sample of "B.2.2 Sending ebXML Service
    messages over HTTP" is correct.

3. It is ambiguous which value you should use
    for Role element under From and To element
    in the MessageHeader.
    CollaborationProtocolAgreement/PartyInfo/CollaborationRole/Role@name
                    or
CollaborationProtocolAgreement/PartyInfo/CollaborationRole/Role@xlink:hr
ef
    There is description that URI is recommended for the value
    but sample of the CPPA specification is using the other one:
    @name : "Buyer"
    @xlink:href : "http://www.rosettanet.org/processes/3A4.xml#Buyer";

And the following feedback is for CPPA. But it might be
good to inform to MS TC also.

4. Currently, SecurityDetails, Certificate in CPA is
   required "one or more". However we believe
   it should be "zero or more".

Thanks,

Iwasa
Fujitsu Limited


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>