[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-dev] RE: OASIS Members to Develop Universal Business Language
There isn't a mystical set of know all people who will be buiding and maintaining the core component library in global isolation! What will be done is to collate and harmonise contributed core component definitions from any business area or source. Of course, each business area almost certainly has some specific core components and some have very many indeed such as healthcare. But it is also true that we all share the need for some common core component structures and definitions. Semantic harmonisation is the key to success but it is also the hardest job of all to achieve.
Senior Director, Document Standards, Commerce One Labs
Tel: +44 1332 342080
From: Paul Horan [mailto:email@example.com]
Sent: 18 October 2001 20:13
To: 'Duane Nickull'
Subject: RE: [ebxml-dev] RE: OASIS Members to Develop Universal Business
Probert, Sue wrote:
> Hi Duane
> I guess I speak for the whole ebXML UN/CEFACT core components team in
> stating that it is definitely not in the interests of future e business
> interoperability to talk of encouraging anyone to build their own core
> component library separately from the global effort.
Agreed. I think that is also expressed in the document I pointed out
(COre Components Discovery and Analysis). Use what exists set rather
than developing your own, don't duplicate etc.
However, there will be situations where people feel it necessary to
build their own (or have already built them) and ebXML does allow and
Sue (et. al.),
I don't understand how a "global effort" will be able to build a set of core
components for our industry (Television/Cable Advertising). We're going to
*have* to do this ourselves and develop our own (unless I misunderstand the
concept of a core component). Sure, we have RFPs and Purchase Orders and
Contracts and Invoices like somebody that sells toner cartridges, but our
clients are selling "time", and that's definitely apples and oranges.
Now, we want to be ebXML/OASIS-compliant (whatever that means), and as soon
as this all settles down and I can see an example of a working set of
applications that support this standard, I'll have something to model to.
Video Communications Inc.
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
Powered by eList eXpress LLC