Lists Home |
Date Index |
I agree with all of Tony's points, and will add some:
Since CCTS is most prevelant within international trade, its adoption is
of greatest advantage if interacting with others in that arena (for
example, for an international supply chain). If outside of that arena,
one must weigh the advantages and disadvantages, based on business needs
Recognizing first that Core Components are syntax-neutral,
"core-componentizing" existing XML schemas (for example) may require a
good amount of effort and update, so the proper level of justification
needs to exist (e.g. are you involved in exchanges with others that use
CCTS? If so, are there enough parties involved to reap the benefits of a
standard data modeling methodology such as CCTS, as well as semantic
alignment?). For example, if one is exchanging information with a few
parties using an existing set of schemas, there may be no advantage to
"core-componentizing" the schemas.
As Tony alluded to, there is currently a scarce level of product support
for Core Components. UN/CEFACT is in the process of establishing a
CCTS-enabled ebXML Registry implementation (i.e. one that natively
recognizes Core Components and their associated artifacts), and when
this is done the availability of Core Components, BIEs, etc. in a
registry that can combined and recombined to create new artifacts will
be very valuable. To my knowledge, there is also a void regarding Core
Components assembly tools. If this changes, the ability to serialize
Core Components as XML schemas (as well as other data exchange formats)
will also be very powerful.
Booz Allen Hamilton
700 13th St. NW, Suite 1100
Washington, DC 20005
Visit us online@ http://www.boozallen.com
> -----Original Message-----
> From: email@example.com
> Sent: Tuesday, January 17, 2006 2:22 AM
> To: firstname.lastname@example.org
> Subject: Re: [xml-dev] Why CCTS?
> Dear David,
> Hi. I think we met at XML 2005 last year. I've recently
> become a UK representative to the UN/CEFACT TMG that produces
> CCTS (http://www.untmg.org/).
> --- David Carver <email@example.com> wrote:
> > 1. Why make the switch to CCTS?
> > 2. What are the short term and long term benefits.
> > 3. Are there any down sides to migrating to CCTS?
> The long term advantage to everyone will be if we adopt a
> common methodology, so that we aren't all re-inventing the
> same wheel every time one of us starts a new project. That
> is what I am looking for CCTS to deliver.
> Pragmatically, my experience is that data and methodology
> standards often don't pay for themselves until there are
> software applications available which support those
> standards. As a really early adopter, you have to write as
> much software as you would for a proprietary approach, and
> possible more (if your proprietary approach is narrower in
> scope than the standards approach).
> I expect UBL to make CCTS use widespread, but people won't be
> using it *because* it is CCTS, they will be using it because
> that is what their trading partners are using. They won't
> realise they are using CCTS under the hood/bonnet. Once
> there is that momentum in the market, I think there will be a
> business case to do new work using CCTS, and possible move
> some existing work. SAP is moving to using CCTS in its
> products too, that will cause other folks to move to CCTS,
> possibly without realising it.
> You are going to have to make a serious decision about where
> on the adoption curve you want to be. I think it's fair to
> say that CCTS is still at the early adopters stage, and
> possibly will be for a couple more years.
> Cheers, Tony.
> Anthony B. Coates
> Senior Partner
> Miley Watts
> Experts In Data
> +44 (79) 0543 9026
> Data standards participant: ISO 20022 (ISO 15022 XML), ISO
> 19302, UN/CEFACT TMG, MDDL, FpML, UBL.
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an initiative of OASIS
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>