OASIS Universal Business Language (UBL) TC

Hi folks!

I am reviewing and polishing the SGTG strategy document based on 
valuable feedback and introspection triggered by Fulya's review 
(thank you, Fulya!).

In my work today, I have unveiled another possibility of working with 
the new UBL unqualified data types in conjunction with the existing 
UN/CEFACT schema fragments.

If you recall from the current issue of the strategy:

http://www.oasis-open.org/committees/document.php?document_id=34338

... I am currently mechanically deriving a version of the UN/CEFACT 
unqualified data type schema fragment in order to remove the code 
lists, and then I add in the absent supplementary components we need 
by using the UBL unqualified data type schema.

Today in my work I found in our existing UBL 2.0 delivery directory a 
UN/CEFACT published schema that appears to be both without code lists 
and with supplementary components that we need (I cannot fathom how I 
missed this in the first go-around, other than I was too focused on 
the UBL 2.0 use of the UN/CEFACT UDT module):

http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/CCTS_CCT_SchemaModule-2.0.xsd

... but it seems incomplete in that it doesn't have Name Type and 
Graphic Type (perhaps others).

It has the following metadata in the comments:

At 2009-12-20 09:17 +0100, JAVEST by Roberto Cisternino wrote:
>it seems this is the latest available at CEFACT D09A:
>
>

Going back to the original reasons for including
the Core Components Types as a schema in UBL 1.0,
we did so for information reference only since no
other schema 'uses' it. It is a bit like an abstract
concept schema and the only connection of other
artefacts to it is conceptual. The unqualified
datatypes depend on these core component types
in the model, not in the schema package. The
unqualified datatypes have no schema reference to
the core component types but their *design* stems from
the core component types. It is the qualified datatypes
which have the UBL-specific details such as code lists
choices determined by the modelers. The UBL business
model architects should have no influence at all on
the core component types or the unqualified datatypes
but only on the qualified datatypes (such as codelist
bound qualified code types). So it still seems confusing
to even include the CCT schema in the package (though
I don't recollect if the NDR says to do so).

Best regards

Steve
---
Stephen D Green




2009/12/20 G. Ken Holman