UBL Library Content Sub-Committee

1. UBL Library Content Sub-Committee November 1st 2001

2. Mission Statement To rapidly develop standard XML business library content by taking an existing library as a starting point and modifying it to incorporate the best features of other existing business and core component libraries.

3. Members Jeffery EckVinod ViswanathanMarion RoyalPeter Yim Jack Gager David Lewis Arijit Sengupta Arofan Gregory Adam Cheyer Tim McGrath (Chair) Mark CrawfordEric ArnoldMichael JacobsLisa SeaburgSue ProbertPhillip EngelGarret Minikawa

4. Roles • Chair (Tim) • Vice Chair (Marion) • Editor (Vinod) • Reports • Technical Editor/Librarian (Lisa) • Manage Repository • Liaisons • CEFACT (Eric, Sue, Mark) • xCBL (Arofan, Jack) • xBRL (Phillip)

5. CONTEXT Business Business Information Entity Basic Core Component Aggregate Business Information Entity Aggregate Core Component Message/Document We Started This Way CBL Core Core Component Type UBL

6. “root” core Component? Core Component data type applied Business Information Entities Business Information Entity or BIE instantiations text account financial account checking account savings account date stock account bond account etc. Aggregate ABIE using BIE Aggregate ABIE using BIE Aggregate ABIE using BIE Applied ABIE’s CC-UBL Overlap CCI focus of effort UBL focus of effort

7. CONTEXT Business Business Information Entity Basic Core Component Aggregate Business Information Entity Aggregate Core Component Message/Document We Ended Up This Way CBL Core Core Component Type UBL

8. The BIE Catalog

9. Deliverables # Deliverable Dependencies Steps Comments 1 Create a BIE Catalog - Identifying the BIE’s out of the xCBL Library. Have a documented xCBL Library. UML models of the documents. Tools and Techniques Group should recommend final format to actually deliver work. The priority documents are Order and Invoice as outlined by xCBL. We will start with looking at the high level tree, then chop off sections and hand out to everyone. Work to go through Peer Group Review. We are associating context as we build the catalog. * This work will be presented to UN/CEFACT as candidate core components. We should tune and document the process as we go.

10. Deliverables 2 XML (XSD) Schemas for business document types Task #1 must be in progress for this to be started. Schema Design Rules and Naming Conventions must be defined before these can be started. Tools and Techniques Group to give us guidance on use of XSD Schema and tools selection and usage. Start with ABIE for business document (ie, Order). At what point do we apply and identify context? There will be ongoing development as tools and techniques become available.

11. 3 Example instance for each schema #2 These are done after the schemas are written. Task will be distributed amongst the group. A case study of different types of samples would be desirable. (ie, xCBL, EDI, OAGI, RosettaNet) Deliverables

12. 4 Customization methodology During Task #1 documentation will be taking place.  #2 must have been well fleshed out (and the decision about an extension vs. restriction design principle must have been made)  Tools and Techniques Group to give us guidance on tools selection and usage. The methodology should include guidelines on ways in which to restrict divergence in extensions. This is a "harmonization" aide. There will be ongoing development as tools and techniques become available.

13. Deliverables 5 Documentation for business documents Dependant on #3 Tools and Techniques Group need to give us the guidance on how to do this. Contribute to the UBL FAQ about syntax and use of the documents we are building. Archival Autogenerated How to integrate Standards convergence

14. 6 Publication into Public Registries Tasks #2, #3, and #4 must be completed. Identification of the Registries by the TC. (example: UN/CEFACT or ebXML) Deliverables

15. Scope of Work Two phases: • Rapid Development • Ongoing Maintenance Documents as our scope: Core Library category: • PurchaseOrder • PurchaseOrderResponse • PurchaseOrderChange Trade Procurement category: • DespatchAdvice Materials Management category: • Planning Schedule/ShippingSchedule • GoodsReceipt

16. Scope of Work • Trade/Payment category: • CommercialInvoice • RemittanceAdvice • Transport/Logistic category: • ConsignmentStatusRequest/ConsignmentStatusReport • TransportContract or BillOfLading • Catalog category: • PriceCatalog/ProductCatalog • Statistical Reports category: • AccountingReport • Candidate Documents • Control Acknowledgement/Functional Acknowledgement • NOTE: Experience shows there needs to be something here, further discussion is needed

17. Manner of Work The priority documents are Order and Invoice as outlined by xCBL. We will start with looking at the high level tree, then chop off sections and hand out to everyone.  Starting with Order, we can break it up into several different parts: • Header • Detail: Item • Detail: Packaging Work in teams, peer team review.

18. Schedule of Work • Develop Project Schedule – Nov 6th • Develop Information/Starter Kit – ASAP • xCBL navigation tools • UML class diagrams • xCBL documentation • UBL BIE template