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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

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


Subject: Re: 2.4.1 requirements document


Scott,

Please take a look at this comment on Registry and Repository requirements, and advise
us.

Thanks,

Mike


Peter Kacandes wrote:

> 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

--
Michael C. Rawlins, Rawlins EDI Consulting
http://www.metronet.com/~rawlins/




[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