----- Original Message -----
Sent: Thursday, April 19, 2001 8:03
AM
Subject: RE: Just what is a Core
Component? Well, it depends on what "is" is.
William (or should I say William JJ?)
Very interesting,
however the question still remains - where in the single expected ebXML core
component specification (or in any of the supporting documents identified in
the is a firm definition of a core component. The latest version
of the discovery and analysis document still doesn't explain what it is we are
discovering and analyzing. Each of the ebXML CC Documents have vague
references to the concept of a core component, but I have yet to find a clear
definition, much less a more detailed explanation of the concept of core, in
any of them (and that includes the BP and CC overview document). I know
the ebXML glossary has a definition ( lowest level, industry neutral building
blocks which are used within the construction of ebXML business processes),
but does that really say what we need to say. I don't think so as one of
the most frequently asked questions I receive from folks when I am talking
about ebXML, is what is a core component. And the questions are usually
from folks who have tried to read the draft documents. If they don't get
it, what hope do we have of anyone using this stuff?
If I am missing it,
perhaps the editors can point out the exact location for my tired eyes (too
many ebXML specs, not enough resting time!)
Mark
> -----Original Message-----
>
From: William J. Kammerer [mailto:wkammerer@foresightcorp.com]
> Sent: Wednesday, April 18, 2001 11:55 AM
> To: ebXML Core
> Subject:
Just what is a Core Component? Well, it depends on what "is"
> is.
>
>
> Mark Crawford asked "when are we going to see a
standard definition of
> what a core component
is?"
>
> There's stuff
under the legend "Core Component Definition and
>
Relationship with CBOs" at the ebXML Core Components page at
> http://www.ebxml.org/project_teams/core_components/Method.htm,
which
> includes
CC-Definition_2000-10-18.doc. This was contributed by Mike
> Adcock, dated 2000-10-18 (see, I'm using ISO 8601
Extended Data
> formats!!). It seems like a
workable definition, and is accompanied by
>
pictures and diagrams. Is there anything wrong with this
> document? And
>
if so, why is it still available at the web site?
>
> William J. Kammerer
>
FORESIGHT Corp.
> 4950 Blazer Pkwy.
> Dublin, OH USA 43017-3305
>
+1 614 791-1600
>
>
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
>
"accelerating time-to-trade"
>
>
>
>
------------------------------------------------------------------
> To unsubscribe from this elist send a message with the
single word
> "unsubscribe" in the body to:
ebxml-core-request@lists.ebxml.org
>