ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ebxml-msg] Additional feedback to ebMS2.0 and CPPA
- From: iwasa <kiwasa@jp.fujitsu.com>
- To: ebXML Messaging <ebxml-msg@lists.oasis-open.org>
- Date: Wed, 05 Mar 2003 18:30:42 +0900
All,
Here is a reminder for issues to be captured in
Requirements List, hopefully in the F2F meeting.
Thanks,
Iwasa
> > > 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.
> >
> > Agreed. Isn't it fun tracing everything back to RFC 2822?
> > > 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:href
> > > 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"
> >
> > I'm not entirely certain what the issue is here. Are you commenting on
> > another ambiguous interaction between the CPP/A or BPSS documents and an
> ebXML
> > Message conforming to those requirements, something similar to our
earlier
> > discussions around the Service and Action values? If I remember
> correctly,
> > those earlier discussions were resolved (after discussion between the
TC's
> and
> > with UN/CEFACT) in the CPP/A or BPSS specifications. Our current
> > specification certainly does not describe the specific source in a BPSS
or
> > CPP/A instance for the Service or Action values. Are you suggesting a
> > different approach for the Role element value or am I missing the real
> issue?
>
> As Cliff helped me to explain the issue, it seems
> to be clarified now.
> There were some interoperability problem
> when one company is using a name and the other is
> using xlink:href. But spec doesn't describe which
> value we have to use. So we just need a clarification.
>
> Thanks,
>
> Iwasa
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]