Forwarding a message that should be of interest ... especially to those
who are planning to contribute to the CCT-Rep] project feedback and
recommendations document. (01)
... incidentally, the existance of the eBSC inititiative came up in last
week's NIST-Ontolog meeting in Gaithersburg too. (02)
-ppy (03)
--- Begin Message ---
If we could consider UBL the source for the common element names, etc.,
then we're well beyond an F but not yet an A. Their body of work isn't
nearly as rich as the existing EDI standards. (01)
The problem is that we can't consider UBL as the single, common
source. There are several families of XML business document standards that
purport to be based on ebXML Core Components. UN/CEFACT's approach, while
not as mature as UBL, differs in a few areas. While the OAG has stated the
intent to support ebXML Core Components, their OAGIS represents yet a
different implementation. And, there is the recently approved X12.7 from
ANSI ASC X12, which lays out yet another approach to XML. And these are
just a few of the more significant examples. One of the work items of the
eBSC Forum, sponsored by the U.S. National Institute for Standards and
Technology (NIST), is to facilitate forging a consensus in this area. (02)
Given the current state of affairs, I think a lot of us that were involved
in the original ebXML effort wish very much that it had taken on and
completed this work item. (03)
If we consider the big picture, that is, not just UBL but all of these
other efforts, my preliminary assessment right now would be a D or a
"Gentleman's" C. I hope to see significant improvement, but I'm not
betting the farm on it. (04)
Regards, (05)
Mike (06)
At 02:42 PM 7/15/2004 +0200, Bryan Rasmussen wrote: (07)
>In Mike Rawlin's article 'ebXML and Interoperability'(
>http://www.rawlinsecconsulting.com/ebXML/ebXML3.html) he grades ebXML on
>various aspects of interoperability.
>One of the aspects was "Common Expression" defined as "Common set of XML
>element names, attributes and common usage of those attributes, common
>approach to document structure" - ebXML didn't address this at all. One of
>the main reasons is that, as noted in my opening article, ebXML's strategy
>was to enable several existing XML approaches to interoperate rather
>choosing only one. It also tried to address a very broad scope, with
>applicability to technologies other than XML." which he gave a grade of F.
>
>If we were to suppose ebxml as the framework and UBL as providing the common
>set of xml element names etc. could we then change that grade to something
>closer approaching an A?
>This is based on my understanding of UBL, although not requiring ebXML, as
>being designed to be ebXML compatible. If this is a misapprehension on my
>part please point it out. Thanks.
>
>The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The
>list archives are at http://lists.ebxml.org/archives/ebxml-dev/
>To subscribe or unsubscribe from this list use the subscription manager:
><http://www.oasis-open.org/mlmanage/> (08)
---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
Using XML with Legacy Business Applications (Addison-Wesley, 2003)
www.awprofessional.com/titles/0321154940 (09)
The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The
list archives are at http://lists.ebxml.org/archives/ebxml-dev/
To subscribe or unsubscribe from this list use the subscription manager:
<http://www.oasis-open.org/mlmanage/> (010)
--- End Message ---
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Unsubscribe/Config:
http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (01)
|