Upload
merry-shaw
View
220
Download
6
Embed Size (px)
Citation preview
1
UBL Library Content Sub-Committee
November 1st 2001
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.
Tim McGrath (Chair)Mark CrawfordEric ArnoldMichael JacobsLisa SeaburgSue ProbertPhillip EngelGarret Minikawa
Jeffery EckVinod ViswanathanMarion RoyalPeter YimJack GagerDavid LewisArijit SenguptaArofan Gregory Adam Cheyer
Members
RolesChair (Tim)Vice Chair (Marion)Editor (Vinod)• ReportsTechnical Editor/Librarian (Lisa)• Manage RepositoryLiaisons • CEFACT (Eric, Sue, Mark)• xCBL (Arofan, Jack)• xBRL (Phillip)
CONTEXTCore Component Type
Core Component Type
Core Business
Basic Core ComponentBasic Core Component
Aggregate Core Component
Aggregate Core Component
Business Information Entity
Business Information Entity
AggregateBusiness Information
Entity
AggregateBusiness Information
Entity
Message/DocumentMessage/Document
We Started This Way
UBL
CBL
text
date
etc.
data type
“root” coreComponent?
account
Core Component
Business InformationEntity
financial account
UBL focus of effort
CCI focus of effort
checking account
savings account
stock account
bond account
appliedBusiness Information Entities
Aggregate ABIE using BIE AppliedABIE’s
CC-UBLOverlap
Aggregate ABIE using BIEAggregate ABIE using BIE
orBIE instantiations
CONTEXTCore Component Type
Core Component Type
Core Business
Basic Core ComponentBasic Core Component
Aggregate Core Component
Aggregate Core Component
Business Information Entity
Business Information Entity
AggregateBusiness Information
Entity
AggregateBusiness Information
Entity
Message/DocumentMessage/Document
We Ended Up This Way
UBL
CBL
The BIE Catalog
UBL000170 Country. Code Code.Type Basic A nation w ith its ow n government
UID Dictionary Name CCT UsedBasic or
Aggregate Definition Remarks
# 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.
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.
Deliverables
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
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.
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. ArchivalAutogeneratedHow to integrateStandards convergence
Deliverables
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
Scope of WorkTwo phases:
Rapid DevelopmentOngoing Maintenance
Documents as our scope:Core Library category:
PurchaseOrderPurchaseOrderResponsePurchaseOrderChange
Trade Procurement category:DespatchAdvice
Materials Management category:Planning Schedule/ShippingScheduleGoodsReceipt
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
Scope of Work
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:
HeaderDetail: ItemDetail: Packaging
Work in teams, peer team review.
Schedule of Work
Develop Project Schedule – Nov 6th
Develop Information/Starter Kit – ASAP xCBL navigation tools UML class diagrams xCBL documentation UBL BIE template