OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-tp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: Explanations about examples of CPP/CPA based on CPP/CPASpecificationV1.0



Yukinori,

Thank you for the suggestion for fixing the example.  At this time, we are
making no further content changes in the specification or the ASCII files.
Your posting will serve to alert team members about the errors.

I am adding this to the list of errors to be corrected by the new OASIS
technical committee.

Regards,
Marty


*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



"Yukinori Saito" <y-saito@ecom.or.jp> on 05/17/2001 09:14:34 PM

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:   "TP-Team" <ebxml-tp@lists.ebxml.org>, "EDIgr)H.Sugamata"
      <sugamata@ecom.or.jp>, "EDIgr)K.Mizoguchi" <mizoguchi@ecom.or.jp>,
      "EDIgr)K.Wakaizumi" <waka@ecom.or.jp>
Subject:  Re: Explanations about examples of CPP/CPA based on CPP/CPA
      SpecificationV1.0



Marty,
Thank you very much for your comments.
I embedded my farther comments below written by 'YS'.
Best Regards,
Yukinori Saito

----- Original Message -----
From: Martin W Sachs <mwsachs@us.ibm.com>
To: Yukinori Saito <y-saito@ecom.or.jp>
Cc: TP-Team <ebxml-tp@lists.ebxml.org>; EDIgr)H.Sugamata
<sugamata@ecom.or.jp>; EDIgr)K.Mizoguchi <mizoguchi@ecom.or.jp>;
EDIgr)K.Wakaizumi <waka@ecom.or.jp>
Sent: Thursday, May 17, 2001 11:25 PM
Subject: Re: Explanations about examples of CPP/CPA based on CPP/CPA
SpecificationV1.0


>
> Yukinori,
>
> My responses to your questions are embedded below.
>
> Regards,
> Marty
>
>
****************************************************************************

*********
>
> Martin W. Sachs
> IBM T. J. Watson Research Center
> P. O. B. 704
> Yorktown Hts, NY 10598
> 914-784-7287;  IBM tie line 863-7287
> Notes address:  Martin W Sachs/Watson/IBM
> Internet address:  mwsachs @ us.ibm.com
>
****************************************************************************

*********
>
>
>
> Yukinori Saito <y-saito@ecom.or.jp> on 05/16/2001 09:44:04 PM
>
> To:   TP-Team <ebxml-tp@lists.ebxml.org>
> cc:   "EDIgr)H.Sugamata" <sugamata@ecom.or.jp>, "EDIgr)K.Mizoguchi"
>       <mizoguchi@ecom.or.jp>, "EDIgr)K.Wakaizumi" <waka@ecom.or.jp>
> Subject:  Explanations about examples of CPP/CPA based on CPP/CPA
>       Specification V1.0
>
>
>
> I made brief explanation documents about examples of CPP/CPA based on
> CPP/CPA Specification V1.0.
> I revised some descriptions of explanation documents that were indicated
in
> Vienna meeting.
> If anyone noticed some comments about these explanation documents, please
> let me know.
>
> Followings are my doubt about CPA example.
> (1)The contents of Service element of both companies are different each
> other.
> One (for buyer) is 'uri:example.com/services/buyerService' and the other
> one
> (for seller) is 'uri:example.com/services/sellerService'.
> Is this possible?
>
> MWS:  The service element refers to the service facility of the party
under
> which
> the service element list listed.  The values of the service elements of
the
> two
> parties may be the same or different.
>
> (2)Communication protocol of company '123456789' (buyer) is HTTP and
SMTP.
> Communication protocol of company '987654321' (seller) is HTTP only.
> Is this correct?
>
> MWS:  The CPA example in the published specification shows that the
> communication
> protocols of both parties are HTTP only.  One party has transport N05,
the
> other
> has transport N35.  In the CPP, there is a transport N08 which has
Receive
> HTTP and
> send SMTP but this is not used in the CPA.
>
YS: But there is another transport N18 (This number may be mistaken.) in
Line 44-48 in the CPA.
This transport element has Sending HTTP and Receiving SMTP.
This transport is used associated with Override element
(action='orderConfirm').

> MWS: There is another problem in the CPA.  One Override element
references
> channeId="N08" and one DeliveryChannel element references transportId
> ="N08". Nothing
> in the CPA has an ID attribute with value "N08".  In addition, the same
ID
> attribute
> value cannot be used on two different elements.  The parser should detect
> these
> errors. This will not be fixed now.  It should
> be on the list for fixing later by the OASIS TC.
>
YS: This kind of troubles are fixed errors in the CPA example. These kind
of
errors were pointed out in the CPP example.
We forgot to change these errors in Vienna meeting.
 If my understanding is correct, following changes should be done.
(Line23) 'N08' of channelId attribute under Override element should be
'N07'.
'N07' is a ID number of DeliveryChannel. (Line32)
(Line 44) 'N18' of transportId attribute under Transport element should be
'N08'.
'N08' is reffered from DeliveryChannel. (Line32)

Line number in my comments is associated with my explanation documents of
CPP/CPA examples that were posted yesterday.

> Best Regards from Japan,
> Yukinori Saito
> --------------------------------------------------
> Yukinori Saito
> Electronic Commerce Promotion Council of Japan(ECOM)
> E-mail:y-saito@ecom.or.jp
> TEL:+81-3-5500-3642   FAX:+81-3-5500-3660
> --------------------------------------------------







[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC