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


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [ebxml-dev] ebXML core components derivation by restriction

Bryan/Joe/et al.

I concur with Joe's assessment that the current CCTS does not adequately
address the need for core component extension. The need exists due to
the simple fact that there is no such thing as a one size fits all
purchase order or invoice or .. or .. etc. Too many industry-unique data
requirements preclude one size fits all schema for most ebusiness
transactions. Extensibility is essential at the core component building
block level.

If you agree with the requirement stated above, then a centralized
online source and global registry for finding core component building
blocks with the associated capability to extend those building blocks
(as necessary) in a controlled fashion is an essential requirement. A
proposed approach to this essential requirement is highlighted in the
concept of operation (Figure 7) in the ebXML Forum article at

Ron Schuldt
Senior Staff Systems Architect
Lockheed Martin Enterprise Information Systems
11757 W. Ken Caryl Ave.
#F521 Mail Point DC5694
Littleton, CO 80127


-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Wednesday, July 28, 2004 7:10 AM
To: Bryan Rasmussen
Cc: ebxml-dev@lists.ebxml.org
Subject: Re: [ebxml-dev] ebXML core components derivation by restriction


Commenting solely on the Core Components Technical Specification, not on
UBL's implementation:

According to my highly detailed analysis of the CCTS (current version
and several versions past) has - in my opinion - shown that the Core
Components methodology, as documented in the CCTS, has not given
adequate consideration to the notions of inheritance and extension. I
have communicated this to the UN/CEFACT CCTS team in the past.

Kind Regards,
Joe Chiusano
Booz Allen Hamilton
Strategy and Technology Consultants to the World

Bryan Rasmussen wrote:
> Hi,
> The core components work basically via derivation by restriction, I've
> noticed a little grousing about that here and there, will future
usages of
> core components allow derivation via other methodologies?
> It seems to me that this has affected the derivation methodologies of
> reference:
> where it looks to me that what one has to do if one wants to add
elements is
> first off derive by restriction, quoting from the referenced url
> derive by restriction, eliminating the element referring to
> from the myns:MyOrderType, then derive by extension adding an element
> refers to myns:MyPartyType.
> "

Kind Regards,
Joseph Chiusano
Booz Allen Hamilton

<<attachment: winmail.dat>>

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