[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ubl-lcsc] Agenda for the next UBL Library Content subcommittee to beheld on MONDAY 30th December between 8 and 10 a.m California time
The regular meeting of the UBL Library Content subcommittee will be held on MONDAY 30th December between 8 and 10 a.m California time http://www.timeanddate.com/worldclock/fixedtime.html?year=2002&mon=12&day=30&hour=16&min=0&sec=0 The numbers (for this week only) are... International: 646 441 1003 U.S. domestic: 866 680 0148 Participant code: 701188 NOTE: This is yet another NEW call number. You may be placed on hold until Jon or I join the call. Once again we shall run a MetMeeting in conjunction with this call. For access details consult the message: http://lists.oasis-open.org/archives/ubl-lcsc/200201/msg00032.html It would be helpful if those using NetMeeting or VNC would connect 5 minutes prior to the call. The agenda will be: 1. Welcome from Chair and appointment of Secretary to take minutes 2. Acceptance of previous minutes 3. Analysis Team report (Sue/Michael) 4. Assembly Team report (Mike) * Document Types/Reusable components spreadsheets * XSD generation 5. QA Team report (Marion) * Scope Statement * Normalized Model 6. Packaging Team (Lisa/Tim) Draft Document (see attached) 7. Review work plan and schedule 8. Other Business -- regards tim mcgrath fremantle western australia 6160 phone: +618 93352228 fax: +618 93352142Title: Universal Business Language — Part 2: Library Content
This document has been prepared to assist parties wishing to comment on the UBL Library. It attempts to explain the various components of the UBL release and how they fit together to form an architecture for UBL.
The UBL Library is…
The UBL Library is a collection of business information entities expressed in a logical model. These are then transformed using the UBL Naming and Design rules into XML Schema syntax.
This methodology position paper (Ref: ) describes the process by which the UBL logical model has been developed. The logical model itself is shown in UML class diagram notation (Ref: ) and as a spreadsheet (Ref: ).
For example, the document Order Response may have a limited audience, but the re-usable component Party or Item will have relevance to many applications. We are keen to hear from experts who can suggest supplementary components used in the context of their industry or geopolitical environment.
The UBL methodology can be applied by both UBL members and the broader community. This will enable a broader range of interested parties to understand, refine and extend the UBL Library and to develop models for contextualized situations.
UBL establishes a system for the concrete representation of documents to be used in electronic commerce.
This part of UBL specifies an XML library of simple and aggregate business information entities to be used in the construction of business documents together with a set of basic XML business documents assembled from entities in the library.
The UBL Library is a collection of business information entities expressed in a logical model. These are then transformed using the UBL Naming and Design rules into XML Schema syntax.
This methodology position paper (Ref: ) describes the process by which the UBL logical model has been developed. The logical model itself is shown in UML class diagram notation (Ref: ) and as a spreadsheet (Ref: ). Reviewers are asked to consider this model in terms of its potential value to their work at either the component or document level. For example, the document Order Response may have a limited audience, but the re-usable component Party or Item will have relevance to many applications. We are keen to hear from experts who can suggest supplementary components used in the context of their industry or geopolitical environment.
The UBL methodology can be applied by both UBL members and the broader community. This will enable a broader range of interested parties to understand, refine and extend the UBL Library and to develop models for contextualized situations.
[Normative references go here:
XML
XML Schema
CCTS
[Terms and definitions go here; can point to CCTS for most of them...]
Normalization
Containership
Normalized Model
Document Assembly
Hierarchical Model
Context
Class Diagram
Busines Information Entity
Core Component
Object Class
Property
Representation Term
Type
BIE,BBIE, ABIE, ASBIE
CC, BCC, ACC, ASCC
XSD
UML
[The former “Scope Document” and the 'implementation guidelines' go here. Note that we cannot use “Scope” for the name of this section; that's reserved for the scope statement at number 1 above.]
The current spreadsheet matrix used by UBL has proven the most versatile and manageable in developing a logical model of the UBL Library. However, we have also found it useful to have a view that encapsulates the big picture of the structure of UBL. Therefore, we have included a graphical notation in the form of UML Class Diagrams. Such a notation provides a top-level, exploding view.
The UBL logical model contains enough meta-data to allow the automatic generation of XML Schemas based on the rules of the UBL Naming and Design Rules sub-committee. This process is managed by an automated Perl1 script also included in this realse (Ref: ).
The final artifacts for the UBL Library are the XML Schemas themselves. These represent the physical implementation of the logical UBL models.
[Explanatory text goes here.]
Normative XSD schemas for the UBL documents and core component types are referenced through the identifiers below.
[The methodology document goes here.]
[Intro goes here.]
[An explanation of these pieces goes here, including caveats about their non-normative status.]
[An explanation of these pieces goes here, including caveats about their non-normative status.]
Spreadsheets for the UBL documents are referenced through the identifiers below.
[Note to SC: I'll include these as soon as someone sends me an exported set of JPEGs.]
Class diagrams for the UBL documents are referenced through the identifiers below.
Note: This section is a placeholder for materials that will be supplied in the final specification. In the current review cycle, they are scheduled for release after the ASN.1 team processes the normative materials given above. When available, those materials will be found in a supplementary package linked from the UBL Library Content Subcommittee portal at http://oasis-open.org/committees/ubl/lcsc/.
ASN.1 schemas for the UBL documents are referenced through the identifiers below.
Note: This section is a placeholder for materials that will be supplied in the final specification. In the current review cycle, they are scheduled for release after the RELAX NG team processes the normative materials given above. When available, those materials will be found in a supplementary package linked from the UBL Library Content Subcommittee portal at http://oasis-open.org/committees/ubl/lcsc/.
RELAX NG schemas for the UBL documents are referenced through the identifiers below.
Note: This section is a placeholder for materials that will be supplied in the final specification. In the current review cycle, they are scheduled for release after the XSL-FO team processes the normative materials given above. When available, those materials will be found in a supplementary package linked from the UBL Library Content Subcommittee portal at http://oasis-open.org/committees/ubl/lcsc/.
XSL-FO stylesheets for the UBL documents are referenced through the identifiers below.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC