Re: [ebxml-cppa] A straw man Implementation Architecture document forebXML

[Yukinori Saito <y-saito@ecom.jp>]

Dear Tony,

(1) My issue about Relationship between ebXML MS and CPPA
I suppose that the first and effective implementation case of ebXML is ebXML
MS specification.
Many EDI users are wanting to shift to Internet based EDI system to avoid
high cost of VAN based EDI system. And they want to adopt secure and
reliable messaging architecture. I suppose today that the best solution
about this view point is adoption of ebXML MS specification comparing
several standards
in the world (e.g. EDIINT, SOAP, and RosettaNet RNIF).

In Japan, all of several implementation cases adopted ebXML MS first. And
they adopted ebXML MS only at first step.
AS you know, there is close relationships or dependency between ebXML MS and
CPPA specification.
But they don't want to adopt CPPA specification at first step, because they
know the concerning parties very well each other, they don't have needs to
have several CPP's, and the infrastructure to build
application system based on full spec of CPPA specification is a little bit
difficult and require additional cost for users.
What is the best solution how to build an Internet based EDI system that
will adopt ebXML MS specification only?
I suppose that one solution is they develop the common CPA and use the CPA
commonly among the parties.
The other solution is they develop simple configuration file that describes
the relating data that are necessary for Headers of Business document based
on ebXML MS. If someone would describe some kind of method, it would be very
helpful for ebXML MS users.

This is our important issue.
For me, while regrettable, I am not a software engineer, so I cannot
describe technically detailed method or guideline about this point of
solution.

(2) My capable contribution to your specification
As I said before, In Japan, We (ECOM) is now developing 'Internet EDI
(XML/EDI) Introduction Guidebook' in Japanese language.
The object of this guidebook is how to introduce XML based Internet EDI
system for users in Japan. This guidebook describes not only how to
construct ebXML based EDI system, but also how to construct basic Internet
XML/EDI system.
The basic Internet XML/EDI system is a system that adopt XML as syntax only.

I suppose that the following item of our guidebook is relating to your
activity.
-How to adopt B2B standards in the view point of about some layers (from
messaging to business process) (6pages)
-Scenarios and observation to introduce Internet XML/EDI system (Basic
XML/EDI system and collaboration XML/EDI system based on ebXML) (5 pages)
This guidebook is written in Japanese language.
If you think these contents might be some kind of information or material
of your activity, I will translate to English and provide to your activity.
I suppose this translation requires one or two months.

(3) Consideration about Compatibility
We (ECOM) are wanting to describe compatibilities status of ebXML
specifications, and how to deal with different versions for ebXML users in
the our 'Internet EDI (XML/EDI) Introduction Guidebook'.
If anyone knows current information about compatibilities status of ebXML,
please let me know.

Regards,
Yukinori Saito

----- Original Message -----
From: "Tony Fletcher" <Tony.Fletcher@choreology.com>
To: "Yukinori Saito" <y-saito@ecom.jp>; "UN/CEFACT TMG General Discussion
List" <uncefact-tmg-general@listman.disa.org>; "Ebxml-Cppa List"
<ebxml-cppa@lists.oasis-open.org>
Sent: Monday, September 30, 2002 10:42 PM
Subject: RE: [ebxml-cppa] A straw man Implementation Architecture document
for ebXML


Dear Yukinori,

Thank you for your interest and input.  I hope you will track this work and
continue to input as it develops.

I have added all three of your points to the requirements section (at least
for the moment so we do not forget them).

<(1) Relationship among MS, CPPA, BPSS, and others
This is the main aim of the document.  Your input on how to describe these
relationships will be much appreciated.

<(2) Practical Implementation Scenarios of XML/EDI system based on ebXML
(e.g. ebMS→CPPA→BPSS)
The main part of the document should cover all the allowed possibilities so
we do not appear to be constraining ebXML to certain scenarios only.
However adding some illustrative scenarios in an Appendix might be very
helpful.  If you (or anybody else reading this message) are able to provide
one, or more, I will add as an appendix.

<(3) Consideration about Compatibilities
<-Current status of compatibilities among several specifications (e.g. MS,
CPPA, R&R, BPSS)
<-Policy about downward compatibility about next version (e.g. Version 3.0)
<-How to deal with several versions of specifications for users.
 These matters are being dealt with in the joint UN/CEFACT - OASIS team and
I would not want to attempt to duplicate their effort.  If this
'Implementation Architecture' or 'Users Guide' document finds favour then we
could use it to publish their findings on compatible version sets.  Perhaps
a better alternative would be to reference their document when they produce
one - can anyone bring me up to date on this effort and how it is intended
to publish the results??

Best Regards,

Tony

 <http://www.choreology.com/>

Tony Fletcher

Technical Advisor
Choreology Ltd.
13, Austin Friars, London EC2N 2JX UK

Phone:  +44 (0) 20 7670 1787
Mobile: +44 (0) 7801 948 219
Fax:    +44 (0) 20 7670 1785

eMail:  tony.fletcher@choreology.com

Web:www.choreology.com <http://www.choreology.com/>

Cohesions 1.0?

Business transaction management software for application coordination

Home: amfletcher@iee.org


-----Original Message-----
From: Yukinori Saito [mailto:y-saito@ecom.jp]
Sent: 28 September 2002 12:37
To: Tony Fletcher; UN/CEFACT TMG General Discussion List; Ebxml-Cppa List
Subject: Re: [ebxml-cppa] A straw man Implementation Architecture document
for ebXML


Dear Tony Fletcher,

This activity is very useful for users and implementers of ebXML
specification.
In Japan, We (ECOM) is now developing 'Internet EDI (XML/EDI) Introduction
Guidebook' in Japanese language.
Your activity is very helpful for this guidebook.

If it will be acceptable, please add the following description in your
Specification.
(1) Relationship among MS, CPPA, BPSS, and others
(2) Practical Implementation Scenarios of XML/EDI system based on ebXML
  (e.g. ebMS→CPPA→BPSS)
(3) Consideration about Compatibilities
-Current status of compatibilities among several specifications (e.g. MS,
CPPA, R&R, BPSS)
-Policy about downward compatibility about next version (e.g. Version 3.0)
-How to deal with several versions of specifications for users.

Regards,
Yukinori Saito
------------------------------------------------------
Yukinori Saito
Electronic Commerce Promotion Council of Japan (ECOM)
E-mail: y-saito@ecom.jp
Tel: +81-3-3436-7542    Fax: +81-3-3436-7570
------------------------------------------------------