ubl-lcsc message

Subject: [QA] Agenda for 29 Aug Teleconference Call

From: "Lisa-Aeon" <lseaburg@aeon-llc.com>
To: "Ubl-Lcsc" <ubl-lcsc@lists.oasis-open.org>
Date: Wed, 27 Aug 2003 14:16:20 -0500

Please note that the next meeting of the UBL Library Content subcommittee
will be held on FRIDAY 29th August between 8 and 10a.m  California time


http://www.timeanddate.com/worldclock/fixedtime.html?day=15&month=8&year=2003&hour=11&min=0&sec=0&p1=263

#############################################
STANDING INFORMATION FOR UBL CONFERENCE CALLS
U.S. domestic toll-free number: (866)839-8145
Int. access/caller paid number: (865)524-6352
Access code: 5705229
#############################################

The agenda will be:

1. Welcome from Team Leader (Lisa) and appointment of Secretary to take
minutes.

2. Review of Package and update on naming.

 Overview of directory structure:
  UBLv1-alpha
    xml (examples): Stephen Green, Bill Meadows
    xsd (schema):  Chee-Kai Chin
    sss (spreadsheets): Tim McGrath
    uml (models): Tim McGrath
    fs (formatting specs, samples): Ken Holman
     include external links to implementations
    asn (ASN from Paul and John): Paul
    bin (perls scripts and tools): Chee-Kai Chin, Gunther Stuhec
    index.html (Lisa Editor): Lisa Seaburg
    releasenotes.html (Lisa Editor): Lisa Seaburg

3. Status from Package Owners

4.  Review Index.html and ReleaseNotes.html files (attached)
    These files are rough drafts, I took the old files and started from
there.  We need to decide some structure here, do we create sections for
each directory (ie, xsd, xml, sss), or do we put them in Appendices?

    Index.html
        Introduction
        1.0 Scope
        2.0 Normative References
        3.0 ...etc.

AI:  Lisa to work on outline for the Index.html file before Friday.  Will
send out email when done.

5. Review of 1.0 Schedule

6. Reviewing Milestones for Packaging Team

7. FAQ Report (Anne)

8. Other Business

10. Next meeting
 Friday 5 Sept 2004 8:00am PDT


++++++++++++++++++++++++++++++++++++++++++++++++++++
Lisa Seaburg
AEON Consulting
Website: http://www.aeon-llc.com
Email:  lseaburg@aeon-llc.com
Alternative Email: xcblgeek@yahoo.com
Phone: 662-562-7676
Cellphone: 662-501-7676

"If you obey all the rules, you miss all the fun."
                       -Katharine Hepburn
++++++++++++++++++++++++++++++++++++++++++++++++++++



---

File has not been scanned

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003

Title: Universal Business Language — Library Content — 1.0 alpha Review

Universal Business Language — Library Content —
1.0 Review

For our absent friend, Michael J. Adcock - il miglior fabbro

Introduction

Notes about this Release

The downloadable version of this release is available here: UBLv10-alpha Downloadable Release. (This is a zip file that will unpack to give you a replica of the online release directories.)

If there are any problems with the links in this document, you can find the full online version at http://www.oasis-open.org/committees/ubl/lcsc/UBLv10-alpha/ .

Submitting Public Comments on this Release

The OASIS UBL Technical Committee invite other interested parties to comment on this release directly to the Library Content Subcommittee Editor, Bill Meadows using the recommended feedback form, UBL_Comment-0p1.rtf.

This release comment period applies from NEW DATES - Friday, October 31, 2003 through ________________ We welcome your comments and will ensure to advise you of our dispositions to any suggestions.

General comments about OASIS UBL TC

The work of the OASIS UBL Technical Committee is open to public view through the mail archives linked from the UBL home page:: http://oasis-open.org/committees/ubl/
Formal input to UBL from industry data exchange organizations is provided through the UBL Liaison Subcommittee:: http://oasis-open.org/committees/ubl/lsc/
Input from the general public is accepted through the ubl-comment mail list:: http://lists.oasis-open.org/archives/ubl-comment/
Interested parties are invited to comment on the work of the UBL TC by subscribing to the ubl-comment list using the OASIS list manager:: http://lists.oasis-open.org/ob/adm.pl

Disclaimer

This document and its associated components are Copyright © 2003 OASIS and are protected by applicable law as works in progress within the OASIS Universal Business Language Technical Committee. As works in progress, they do not yet have the status of an OASIS Standard or an OASIS Committee Specification. This draft and its associated components are provided on a royalty-free basis and may be freely circulated for purposes of experimentation and review. While the construction of experimental prototypes based on these materials is encouraged for the purpose of generating input back to the committee process, implementers are strongly advised against basing commercial or mission-critical applications on the draft specifications contained in this package. THESE MATERIALS ARE FURNISHED WITH NO WARRANTY, EXPRESS OR IMPLIED, AS TO THEIR SUITABILITY FOR ANY APPLICATION.

1. Scope DO WE WANT TO KEEP THIS?

The Library Content part of UBL specifies a library of business information entities to be used in the construction of business documents together with a set of common XML business documents assembled from those entities.

This document contains normative and non-normative references used by UBL: the context scenario and business rules used to construct the business models and business documents; and the schema instances of the business documents.

2. Normative References WE PROBABLY DO WANT TO KEEP THIS, MAYBE MOVE TO APPENDIX??

[ISO11179] International Standards Organisation's Specification and Standardization of Data Elements for Information Technology: http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm??Redirect=1
[ISO 8601] Data elements and interchange formats -- Information interchange -- Representation of dates and times: http://www.iso.org/iso/en/CombinedQueryResult.CombinedQueryResult?queryString=8601
[CCTS] UN/CEFACT ebXML Core Components Technical Specification 1.90: http://xml.coverpages.org/CCTSv190-2002.pdf
[NDR] Universal Business Language Naming and Design Rules: http://www.oasis-open.org/committees/sc_home.php?wg_abbrev=ubl-ndrsc
[UML] Unified Modeling Language 1.4 (formal/01-09-67): http://www.omg.org/cgi-bin/doc?formal/01-09-67
[XML] Extensible Markup Language (XML) 1.0 (Second Edition),W3C Recommendation 6 October 2000: http://www.w3.org/TR/2000/REC-xml-20001006
[XSD1] XML Schema Part 1: Structures, W3C Recommendation 2 May 2001: http://www.w3.org/TR/xmlschema-1/
[XSD2] XML Schema Part 2: Datatypes, W3C Recommendation 02 May 2001: http://www.w3.org/TR/xmlschema-2/

3. Terms and Definitions AGAIN, KEEP AND MOVE TO APPENDIX??

Business Context: The formal description of a specific business circumstance as identified by the values of a set of context categories, allowing different business circumstances to be uniquely distinguished.
Class Diagram: A graphical notation used by the UML [UML] to describe the static structure of a system, including object classes and their associations.
Container: A modular and self-contained group of data components.
Containership: Aggregating components (nested elements in an XML schema [XML]).
Context: The circumstance or events that form the environment within which something exists or takes place.
Dependency Diagram: A refinement of a class diagram that emphasises the dependent associations to between object classes.
Document: A set of information components that are interchanged as part of a business activity; for example placing an order.
Document Assembly: A description of an hierarchical pathway through a normalized model of information components.
Hierarchical Model: A tree-structured model that can be implemented as a document schema.
Normalization: A formal technique for identifying and defining functional dependencies.
Normalized Model: A representation of normalized data components.
Schema: An XML document definition based on the W3C XML Schema language [XSD1][XSD2].
schema: Any XML document definition.
Spreadsheet Model: A representation of a data model in tabular form.

The terms Core Component and Business Information Entity are used in this specification with the meanings given in [CCTS].

The terms Object Class, Property, Representation Term, and Qualifier are used in this specification with the meanings given in [ISO11179].

4. Symbols and Abbreviations AGAIN, KEEP AND MOVE TO APPENDIX??

ABIE: Aggregate Business Information Entity
ACC: Aggregate Core Component
ASBIE: Association Business Information Entity
ASCC: Association Core Component
BBIE: Basic Business Information Entity
BCC: Basic Core Component
BIE: Business Information Entity
CC: Core Component
EAN: European Article Numbering Association
EDI: Electronic Data Interchange
ISO: International Standards Organisation
NDR: UBL Naming and Design Rules [NDR]
UML: Unified Modeling Language [UML]
UN/CEFACT: United Nations Centre for Trade Facilitation and Electronic Business
XML: Extensible Markup Language [XML]
XSD: World Wide Web Consortium's XML Schema Language [XSD1][XSD2]

6. UBL Library

6.1 Description

Need text here.

Annex A contains the UBL Conceptual model.

Annex B contains the hierarchical document structures assembled from this model. The non-normative UBL document models contain enough meta-data to allow the automatic generation of XML Schemas based on the UBL Naming and Design Rules.

7. UBL Document Schemas

Annex A: UBL Conceptual Data Model (informative)

A.1 Introduction

The conceptual data model describes all the Object Classes, Properties and Associations involved in a general trade procurement process, as defined by Section 5 of this Specification.

This data model is presented graphically as a UML Class diagram.

Figure 2. UBL Conceptual Class Diagram

Note that this model does not represent any specific document type. It is a conceptual view of all the necessary information components involved in any of the UBL document types. All the current UBL document types were derived using object classes and associations taken from this model.

Annex B UBL Document Descriptions (informative)

B.1 UBL Document Spreadsheets

All Business Documents are defined in their individual spreadsheets, each references the Re-usable Component Library spreadsheet.

These are provided in both Microsoft(R) Excel (.xls) and Open Office formats (.svc).

UBL Order (MS Excel) or UBL Order (Open Office)
UBL Order Response (Simple) (MS Excel) or UBL Order Response (Simple) (Open Office)
UBL Order Response (Complex) (MS Excel) or UBL Order Response (Complex) (Open Office)
UBL Order Change (MS Excel) or UBL Order Change (Open Office)
UBL Order Cancellation (MS Excel) or UBL Order Cancellation (Open Office)
UBL Despatch Advice (MS Excel) or UBL Despatch Advice (Open Office)
UBL Receipt Advice (MS Excel) or UBL Receipt Advice (Open Office)
UBL Invoice (MS Excel) or UBL Invoice (Open Office)

All Aggregate Business Information Entities are expressed in the UBL Re-usable Component Library spreadsheet (MS Excel) or UBL Re-usable Component Library spreadsheet (Open Office)

B.2 UML Class Diagrams

Class diagrams for the UBL documents are referenced through the identifiers below.

These are provided in both GIF and PDF formats.

B.2.1 Document Models

UBL Order (GIF) and UBL Order (PDF)
UBL Order Response (GIF) and UBL Order Response (PDF)
UBL Order Change (GIF) and UBL Order Change (PDF)
UBL Order Cancellation (GIF) and UBL Order Cancellation (PDF)
UBL Despatch Advice (GIF) and UBL Despatch Advice (PDF)
UBL Receipt Advice (GIF) and UBL Receipt Advice (PDF)
UBL Invoice (GIF) and UBL Invoice (PDF)

B.2.2 Packages

Address (GIF) and Address (PDF)
Delivery (GIF) and Delivery (PDF)
Item (GIF) and Item (PDF)
Hazardous Item (GIF) and Hazardous Item (PDF)
Party (GIF) and Party (PDF)
Payment (GIF) and Payment (PDF)
Procurement (GIF) and Procurement (PDF)
Tax (GIF) and Tax (PDF)

B.3 XSD Schema

The XSD schema for the UBL Business documents are contained in the XSD directory in the Release.

Descriptive text goes here.

B.2.1 UBL XSD Schema

Placeholder
Placeholder

Title: Universal Business Language — Library Content — 0p80 Release Notes

Universal Business Language — Library Content — 0p80 Release Notes

1. A Note on the UBL Extension Methodology

We need to update this.

2. A Note on Global Element Declarations

The decision on Global is that all elements are declared globally except codelists and id's that will be declared locally.

Last modified: 27 August 2003