[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Collaboration Services (was: Business Service Interface)
Good point, however I imagine we could also collaborate in a business realtionship on a shared building design plan or on the needed color corrections on a new fashion image or share access to a catalog of new record sound samples hosted at a 3rd party site. Would you classify those business relationships as expressed in a "message" ? Sorry but I'm trying to get away from sending copy's of PO's and invoices back and forth .... Dave -----Original Message----- From: Nikola Stojanovic [mailto:nhomest1@twcny.rr.com] Sent: Monday, October 23, 2000 10:06 AM To: 'ebXML-BP@llists.ebxml.org'; ebxml-tp@lists.ebxml.org Subject: Re: Collaboration Services (was: Business Service Interface) <David Welsh> Ok, I can buy some of the suggested terms ... So ... we can say ebXML is ... "Collaborating business activities representing (core) business processes (made from core components) hosted in a Repository and normally qualified thru standard methods when a trading relationship is negotiated and maintained." </David Welsh> I wouldn't neglect very important -> TR&P aspect of it (ebXML). I don't have the right modification yet, but something like: "Collaborating (via ... Messages) business activities representing (core) Business Processes (made from Core Components) hosted in a Repository and normally qualified thru standard methods when a trading relationship is negotiated and maintained." Regards, Nikola
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC