Core Components Riddle

Now that our V3.0 
specs are in OASIS public review, I have a general question on Core Components 
please:

 

The basic question 
is: What precise value do Core Components bring for data 
exchanges?

 

More 
details:

 

Scenario #1: 

 

- Suppose 2 trading 
partners are exchanging data. 

 

- Also suppose that 
none of the Core Components that are used in the exchange are part of the TBG17 
Core Component Library (this will be the variable for the next scenario). 

- The sending 
trading partner decides to indicate in their XML document the various Core 
Component entities (CC's, BIEs, etc.) using a content model (set of 
elements/attributes) near each entity (where does not matter - but let's assume 
just below) that indicates what type of entity it is. 

 

- The receiving 
trading partner processes the XML document, but does not process the entity 
information because all it "cares" about is the actual data, not the data model. 
What value 
does using Core Components bring here?

 

Scenario #2: 

 

- Same as 
above, except that all 
of 
the Core Components that are used in the exchange are part of the TBG17 Core 
Component Library (and stored in the UN/CEFACT Core Component registry - assume 
it is in production), and are indicated as such using their registry 
identifiers.

- The receiving 
trading partner processes the XML document, but should they "care" about 
the entity information this time? What value does using Core 
Components bring here? Is it different than the value in Scenario 
#1?

 

A third question: 
Absent any data exchanges, what would motivate someone to "Core 
Component-enable" all of their data? (for example, creating a relational 
representation of the CCTS Core Component entity metadata, and populating the 
tables/fields with the metadata values + the original data).

 

Thanks,

Joe

 

Joseph Chiusano

Booz Allen Hamilton

Visit us online@ http://www.boozallen.com