Re: 2.4.1 requirements document

[srh@us.ibm.com]

This may be a late response to the 2-API topic,
since I am in travel, but I agree with Peter K's comments. My assumption
here is "API" could mean a "messaging API" vrs a programatic-language API.
Further, assuming a single API, I do not believe ebXML should sanction any
UI
implementation that may be built on that single API.

-sorry if I annoyed any requirements people; I know there has been some
discussion on email/list discipline.

Thanks,
Scott R. Hinkelman
IBM Austin
SWG Java Solutions
XML/Java Standards Architecture
Office: 512-823-8097 TL793-8097
Home: 512-930-5675
Cell: 512-940-0519
srh@us.ibm.com
Fax: 512-838-1074



Peter Kacandes <Peter.Kacandes@ebay.sun.com> on 03/07/2000 02:12:03 PM

Please respond to Peter Kacandes <Peter.Kacandes@ebay.sun.com>

To:   ebXML-Requirements@lists.oasis-open.org,
      ebxml-architecture@lists.oasis-open.org
cc:
Subject:  2.4.1 requirements document




I have a question with regard to section 2.4.1 of the document that makes
reference
to maintaining two apis, one for machines and another for people. This
seems to me
to be extroardinarily inefficient. It seems to me that there should be only
one API
to the system. If somebody wants to write a gui to the system, then they
are
welcome to do it. I think it will be highly impractical to try and develop
and
maintain two apis. I have made these thoughts known within the architecture
group,
but am not aware that we came to any kind of conclusion on the topic.

thanks

regards

pk


Peter Kacandes

Application Planning, Architecture & Strategy      phone number:
X36529
WWOPS IT/Supply Chain Management         email:    peter.kacandes@ebay