The objective is to establish the basic information entity of an xCBL element at a conceptual level. For example, with the xCBL element Currency, the fact that there are two sub-elements (CurrencyCoded and CurrencyCodedOther) does not affect that fact that there is one BIE, Currency which is expressed as a code. The xCBL convention of creating "..Other" elements is merely a means of extending code lists, CurrencyCodedOther is not a separate entity. We should try and avoid designing the new structures at present and focus on the analysis of information - the semantic value of the xCBL elements.
One of the important distinctions to make early in this analysis is whether the entity is of a Simple or Complex type. If the entity holds actual data values(string, number, datetime, code, etc.), then it will be a Simple type and likely to map into a single BIE. If the element has sub-elements, then it is a Complex type and likely to map into an Aggregate BIE. The columns to be completed for these two types are different.
To assist in understanding the data structures, UML class diagrams are provided in the starter kit, to help clarify the contexts of various substructures.
Finally, if it helps in your analysis, refer to the ebXML Core Component Dictionary and attempt to match the xCBL elements with entries in the CC Dictionary.
Each heading has a comment describing the purpose and example content of the column.
If you are comfortable with the ebXML CC naming rules, you can apply them (combine the ObjectClass, Property Term, and Representation term).
If you have difficulty classifying under these concepts, then use either the xCBL names, or something that is meaningful to you. We are attempting to harmonize names across teams as we go, so consult with the mailing list if you have issues with a specific name.
If you are not comfortable with "context", then leave the context drivers columns empty and we shall address them during the review.
Each team will then review the catalog of one other team.
The consolidated catalog will then be used to generate a UBL Order structure, expressed in its XML form (as specified by the Naming and Design Rules subcommittee)and submitted for review by both the membership of UBL and the organizations represented by the UBL Liaison subcommitee.
Following this review the revised catalog will form part of the submission for an OASIS standard.
We shall follow a similar process, but with revisions based on experienced gained.
>From here, we should have established a meaningful 'core' library of entities, suitable for being extended to form many other business documents.