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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-requirements message

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

Subject: Re: 2.4.1 requirements document

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
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.

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
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,
Subject:  2.4.1 requirements document

I have a question with regard to section 2.4.1 of the document that makes
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
welcome to do it. I think it will be highly impractical to try and develop
maintain two apis. I have made these thoughts known within the architecture
but am not aware that we came to any kind of conclusion on the topic.




Peter Kacandes

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

[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