Upload
halia
View
32
Download
2
Tags:
Embed Size (px)
DESCRIPTION
Universal Business Language. Gunther Stuhec SAP AG. 1. 2. Evolution & Success of Business Standards. What is XML?. 3. UBL Initiative. 4. ebXML Core Components. 5. Guidelines, Inputs & Outputs. 6. Modelling Steps. 8. Summary. 7. Benefits. Overview . 1. What is XML?. 4. - PowerPoint PPT Presentation
Citation preview
Universal Business Language
Gunther StuhecSAP AG
SAP AG 2001, Title of Presentation, Speaker Name 2
Overview
4 ebXML Core Components
Guidelines, Inputs & Outputs5
Modelling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
SAP AG 2001, Title of Presentation, Speaker Name 3
Overview
4 ebXML Core Components
Guidelines, Inputs & Outputs5
Modeling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
SAP AG 2001, Title of Presentation, Speaker Name 4
What is XML?
Is XML really
a „egg-laying wool milk pig“ ?
Not really!
XML is a universal data description format based on markups. It can be used for all kinds of applications.
SAP AG 2001, Title of Presentation, Speaker Name 5
<Article><Number standard="EAN13">1234567890123</Number><Type>Strawberrys</Type><Quantity>
<Value>15</Value><UnitType
standard="UoMISOXXX">Piece</UnitType></Quantity><Amount>
<Value>14.12</Value><Currency standard="ISO4217">USD</Currency>
</Amount></Article>
Reusability of XMLNon-common structure- and content
definition
Different XML Parser
Document Exchange
Buyer Seller
BUY SALE
selection, comparison
Payment Invoicinginvoice
Order Supply
order or statistics
Reception DeliveryDelivery
Number Type Quantity UnitType Amount Currency1234567890123 Strawberry 15 Piece 14.12 USD1234567890124 Apples 24 Piece 12.34 USD… … … … … …
Storing and Querying in Databases
Articles:Articles:NumberNumber TypeType QuantityQuantity Amount Amount 1234567890123 Strawberrys 15 Piece 14.12 USD....
Layout and Publishing of Documents
Data Modelling
ArticleNumber: string
Type: stringStandard: string
QuantityValue: integer
UnitType: stringStandard: string
AmountValue: float
Currency: stringStandard: string
Inputa
b
c
d
e
f
g
h
i
m
l
n
j
k
Outputa
cm
n
k
d
e
f
g
h
i
o
l
j
b
k
Transformation APIs
:Applicaton
Send: Article
Ask: Quantity
Send: Quantity
Ask: Amount
:XML
Send: Amount
Closed
SAP AG 2001, Title of Presentation, Speaker Name 6
Applications with XML based Markup-Languages
HTTP, FTP, STMP ...
Definition Languages for Interfaces
Horizontal Business Applications
Business Framework
Vertical Business Applications
TransformationXSLT, XMI
QueryXPath, XQL,
XML-QL, XQuery
StructureXML Schema,
XDR, SOX,RELAX NG
APIsDOM, SAX, JSAX, JAXB
HyperlinksXLL,
XPointer,XML Base
Syntax
Locations (URI) Unicode Namespaces DTDEntities
LayoutXSL-FO,
CSS, XForms, SVG, XHTML
XML Version 1.0
Web ServicesMessaging Services
SOAP, ebXML MSG, W3C XP
Directory ServicesUDDI, ebXML RegRep,
DSML, XMLDir
Security ServiresAuthXML, XML-Signature,
ebXML Sec., SAML, XAML
Defintion: WSDL, NASSL, SDL, CDL ...
ebXML, BizTalk
Consumer: UCC, GCI Discrete: AIAG, RosettaNet
Financial: ACORD, FinXML Oil & Gas: PIDX, PetroXML
Process: CIDX, CML Public Sect.: HL7, LegalXML
Services: ICE, TranXML
BW: PMML SRM: OBI, cXML, eBIS-XML
FIN: OFX, SWIFT, IFX HR: HR-XML
PLM: PDX, STEPml, MatML SCM: BSL, GML, MESA, OAG
CRM: CIQ, ECML, CPExchange
FunctionalService
View(FSV)
BusinessOriented
View(BOV)
TCP/IP
Negotiation ServicestpaML, ebXML CPPA
SAP AG 2001, Title of Presentation, Speaker Name 7
Overview
2 Evolution & Success of Business Standards
4 ebXML Core Components
5
Modeling Steps6
UBL Initiative3
Summary8
Benefits7
1 What is XML?
Guidelines, Inputs & Outputs
SAP AG 2001, Title of Presentation, Speaker Name 8
Evolution of XML Standards
Sep. 98
Visi
blity
"XML-Hype" driven by Industry-Oriented
Groups
Number of Standards
Hype
Source: IAO (according Gartner Group, 1999)
Repetition of „Tower of Babel“
Same mistakes as the earlier EDI times
Driven by Technology
SAP AG 2001, Title of Presentation, Speaker Name 9
Criteria for successful XML business standardization effort (I)
User-driven Royalty-free Not project driven Human- and machine-readable
Focused on Global Requirements Independent of the technical environment Intention for normative status under international law Compatible with existing EDI systems Designed for A2A and B2B
Clear development process and high quality documentation Feedback through early implementations Inclusion of business processes and business codes
SAP AG 2001, Title of Presentation, Speaker Name 10
Criteria for successful XML business standardization effort (II)
Reuse of existing standards Completely based on XML technology, not XML-syntax only Technically logical structure for the simple implementation in the most
different kinds of devices Common development and co-operation with the relevant experts of the
used standards and technologies
Modularized structure Rules for extensibility, restrictibility and conclusive versioning –
enables an easy adjustment of all given requirements Based on reusable building blocks – this guarantees an increased
interoperability with other industries or applications Common repository for providing standardized modules
SAP AG 2001, Title of Presentation, Speaker Name 11
Reengineering the Standards Process
TODAY(informal description)
ScopeFieldspecs
Formatspecs
Usageguidelines Usage
rules
Example ValidationrulesInformation
flow
TOMORROW(rigorous and formal description)
WHY
Business Analysis
Requirements Analysis
BUSINESS MODELS
WHAT
Logical AnalysisMessage
Design
-SWIFTIdent: BIC
InstructingParty
-SWIFTIdent: BIC
ExecutingParty
-Security: ISIN-Action: {Buy/Sell}
Trade
-TradeDate: Date-PriceCondition: Real-OrderedQty: Real
TradeCondition
OrderToBuyOrSell
TRANS-ACTIONS
COMPONENTS
HOW
Technical Design
Technical Implementation
DOCUMENTS
XML CODE
Purchase OrderSender Recipient________ ________ ________ ________________ ________Position__ ________ __________ ________ __________ ________ __________ ________ __________ ________ ________Account Summary________ ______ __________ ______ __________ ______ __
BusinessDocuments
Purchase OrderSender Recipient________ ________ ________ ________________ ________Position__ ________ __________ ________ __________ ________ __________ ________ __________ ________ ________Account Summary________ ______ __________ ______ __________ ______ __
SAP AG 2001, Title of Presentation, Speaker Name 12
The Success of Standardization
No Forward-Looking Standards
Mergingtrafficahead
Mergingtrafficahead
Dead End
StandardOrg. A
StandardOrg. B
StandardOrg. C
StandardOrg. D
StandardOrg. E
StandardOrg. F
StandardOrg. G
StandardOrg. H Standard
Org. I
SAP AG 2001, Title of Presentation, Speaker Name 13
Overview
4 ebXML Core Components
5
Modelling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
Guidelines, Inputs & Outputs
SAP AG 2001, Title of Presentation, Speaker Name 14
What is UBL?
UBL defines naming and design rules for the creation of XML based building blocks.
These building blocks will be the used for the creation of business documents.
All rules are based on internationally accepted standards and recommendations. This includes especially ebXML, UN/CEFACT, ISO and all relevant W3C recommendations.
It will use UML and UMM for supporting the development of appropriate building blocks and business documents.
methodologies for the derivation of context specific building blocks and business documents. This makes all building blocks interoperable for every vertical and horizontal business
an example library of building blocks and a standard set of electronic business documents
UBL is a Technical Committee of OASIS, because OASIS itself is a nonprofit organization dedicated to XML standards development. The standardization process is completely democratic and all results are public and available without any fees.
SAP AG 2001, Title of Presentation, Speaker Name 15
UBL participation
APACS
Boeing
Commerce One
Danish Bankers Association
France Telecom
General Electric
Government of Hongkong
Government of Korea
HP
Intuit
KPMG
LMI
Northrup Grumman
Oracle
PricewaterhouseCoopers
SAP
SeeBeyond
Sterling Commerce
Sun Microsystems
UK Cabinet Office
United Parcel Service
U.S. GSA
U.S. Navy
Visa International
SAP AG 2001, Title of Presentation, Speaker Name 16
ebXML CC and UBL adoption plans
Organizations & Government European Commission US Government & Defense Department eBES (e-Business Board for European
Standard by CEN/ISSS)
Industry groups ACORD (insurance industry) ARTS (retail sales) EIDX (electronics industry) NACS (convenience stores) RosettaNet (IT industry) XBRL (accounting professionals) SWIFT (financials) EAN.UCC (retail and consumer products) SMDX (statistical information)
De jure standards organizations ANSI X12 (EDI) UN/CEFACT (EDI)
Software Vendors SAP SUN Microsystems Commerce One Sterling Commerce Oracle SeeBeyond
SAP AG 2001, Title of Presentation, Speaker Name 17
UBL Subcommittees
TTSCTools and Techniques SC
LCSCLibrary Content SC
CMSCContext Methodology SC
Develops a methodology and tools for applying
context.
CDSCContext Drivers SC
Works on improvement and further development of the
context drivers.
Evaluates and recommends the tools and techniques for development, quality, docus,
maintenance and revision
NDRSCNaming and Design Rules SC
Develops guidelines for normative-form schema design, instance design,
and markup naming,
Defines business documents and a library of XML and
ebXML CCTS based building blocks
MSCMarketing SC
LSCLiasion SC
ASCAdministration SC
Administrates and coordinates the UBL efforts
Does marketing and promotion for the UBL effort
Organizes liasons with other organizations.
SAP AG 2001, Title of Presentation, Speaker Name 18
Overview
4 ebXML Core Components
Guidelines & Inputs5
Modelling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
SAP AG 2001, Title of Presentation, Speaker Name 19
WorkingGroup TMG
WorkingGroup TMG
TechnicalCommittee
TechnicalCommittee
TechnicalCommittee
TechnicalCommittee
The ebXML Initiative
System
ebXML CPPCollaboration
PartnerProfile
System
ebXML CPPCollaboration
PartnerProfile
HTTP/SMTP/FTP
ebXML BPSSBusiness ProcessesSchema Specification
ebXML CPACollaboration
PartnerAgreement
ebXML MSGMessaging Protocol
ebXML RRRegistry &Repository
ebXML CCTSCore Components
Technical Specification
WorkingGroup TMG
ebXML EBAElectronicBusiness
Architecture
Initiated Initiated
XML basedSyntaxRules
SAP AG 2001, Title of Presentation, Speaker Name 20
ebXML Core Components
A set of the lowest common denominator that captures information about the real world (business) concept.
Core Components are neutral in the notation for every kind of industry in the syntax for every kind of business document standard or implementation
Reusable pieces (objects) of contents that can be atomic or aggregate Enables interoperability among different industry domains and areas Are using common semantic units at any level consistent across context Hold any related information together and avoiding fragmented semantic
dispersal Facilitate multilingual support
Accompanied by methodology for extensibility Enable users to define meaningful business and process data Ensure maximum interoperability
The actual specification (Core Components Technical Specification, Part 1, is at V1.8) is in public review.
SAP AG 2001, Title of Presentation, Speaker Name 21
What is „Core“?ProductLifecycleManage-
ment
SupplyChain
Manage-ment
CustomerRelation-
shipManage-
ment
BusinessIntelligence,Process &Workflow
BusinessProcure-ment &
Collabor-ation
Financials HumanResources
Consumer Industries
DiscreteIndustries
FinancialIndustries
Oil & Gas
ProcessIndustries
PublicSector
ServiceIndustries
Vert
ical
Bus
ines
s
Horizontal Business
SAP AG 2001, Title of Presentation, Speaker Name 22
Structure of Core Components (CCs) Core Component Types are:
Amount Monetary unit with currency
Code Brief language-independent replacement
or representation for a definitive value DateTime
Particular point in progression Graphic
Diagram, graph, math. curves Identifier
Identifying and distinguishing uniquely an instance of object
Indicator List of two bolean values (True/False)
Measure Physical measure (size, volume, mass...)
Numeric Representation of a number
Picture Visual representation
Quantity Number of nonmonetary units
Text Character string (specified language)
for creation of
Value Component
carries the actual value
1
Basic CoreComponent
(BCC)
CoreComponentType (CCT)
Supplementary Component
gives extra definition to the value
1..n
Aggregate Core
Component (ACC)
Core Components without
Business Context
SAP AG 2001, Title of Presentation, Speaker Name 23
Core Components and Business Information Entities
Basic Business
InformationEntity (BBIE)
Aggregate Business
InformationEntity (ABIE)
ObjectMessage
Document (ABIE)
Business Information Entities(BIEs)
withBusiness Context
for creation of
Value Component
carries the actual value
1
Basic CoreComponent
CoreComponentType (CCT)
Supplementary Component
gives extra definition to the value
1..n
Aggregate Core
Component(ACC)
Core Components(CCs)
without Business Context
SAP AG 2001, Title of Presentation, Speaker Name 24
Context of Business Information Entities
Context Categories Business Process Product Classification Industry Classification Geopolitical Official Constraints Business Process Role Supporting Role System Capabilities
Naming Rules according ISO 11179:
Basic Business
InformationEntity (BBIE)
Aggregate Business
InformationEntity (ABIE)
ObjectMessage
Document(ABIE)
Object Class Property Term RepresentationTerm
Specific composition of
the context categories
Characteristic or property of
each BIE
Type of the representation of
a valid content
Unit Price. Base. Quantity
Unit. Pricing. Details
Purchase. Order. Message
Business Information Entities with
Business Context
SAP AG 2001, Title of Presentation, Speaker Name 25
ebXML Core Components are „syntax neutral“, it will be a basis for all another business document dialects and standards
Why UBL (Universal Business Language)?
UBL is formed to develop XML business document design rules, XML syntax core component structures and ebXML (UN/CEFACT) CC
compliant XML document schemas
UN/ EDIFACTXML X.12 UN
Layout etc.
ebXMLCore Components
ebXML compliant syntax-implementations
But we must have concrete standard XML syntax to enable wide use and cheap commercial software Given a concrete XML syntax for business, users will adopt it
SAP AG 2001, Title of Presentation, Speaker Name 26
Overview
4 ebXML Core Components
Guidelines, Inputs & Outputs5
Modelling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
SAP AG 2001, Title of Presentation, Speaker Name 27
Guiding Principles
The design of UBL must be as simple as possible be consistent with its definition enable customization and maintenance use Oxford English
The design of UBL types must ensure that context-sensitive document types aren't precluded be as "content-oriented" (as opposed to merely structural) as possible
The design of UBL should provide the 20% of features that accommodate 80% of the needs share as many common features as possible
The design of UBL will leverage expertise in a variety of domains through interaction with appropriate
development efforts. balance prescriptiveness in any one usage scenario with prescriptiveness across
the breadth of usage scenarios supported be cautious about making dependencies on other namespaces.
SAP AG 2001, Title of Presentation, Speaker Name 28
General Rules
UBL messages must represent a single logical unit of information and have a unique
business function correspond to the business process models like ebXML BPSS be modeled for the abstractions of the user, not the programmer use markup to make data substructures explicit express semantics fully in schemas
UBL schemata of messages must realize instances which are readable, intuitive and understandable provide for the expressed correspondences between data elements in
different classification schemes ("mappings") as metadata metadatause well known data types
Code lists should be cited by external reference
SAP AG 2001, Title of Presentation, Speaker Name 29
What UBL is based upon
The UBL design will avail itself of standard XML processing technology wherever possible (XML itself, XML Schema, XSLT, XPath, and so on)
The UBL schemata will be based on the W3C XML Schema Recommendations
All UBL components will be based on ebXML CCTS (Core Component Technical Specification) and ISO 11179 recommendations
Documents/expertise from: The members of the Library Content SC Organizations with a liaison to the UBL TC Feedback from the general public
xCBL 3.0 as a starting library A working XML business vocabulary for several years Has lots of EDI knowledge baked into it
UBL is not responsible for catering to legacy formats
SAP AG 2001, Title of Presentation, Speaker Name 30
Output of the UBL Group
Normative recommendation of naming and design rules for the creation of XML-based building blocks and messages
Representation of UBL in XML/XSD Efficient usability of UBL by external modules
Some non-normative forms of representations UML ASN.1 Other schema representations Modified XSD
Stylesheets for Viewing UBL documents Generating EDI-compliant instances
Context methodologies for extension or restriction of building blocks according to a specific business context
The UBL Library Reusable building blocks Standard business document types
SAP AG 2001, Title of Presentation, Speaker Name 31
First Set of Business Documents
1. Trade/procurement Purchase Order/Purchase Order Response/Purchase Order Change
2. Materials Management Despatch Advice (ASN) Planning Schedule/Shipping Schedule Goods Receipt
3. Trade/payment Commercial Invoice Remittance Advice
4. Transport/Logistics Consignment Status Request/Consignment Status Report Transport Contract (bill of lading)
5. Content Price/Product Catalog
6. Statistical Reports Accounting Report
SAP AG 2001, Title of Presentation, Speaker Name 32
Overview
4 ebXML Core Components
5
Modeling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
Guidelines, Inputs & Outputs
SAP AG 2001, Title of Presentation, Speaker Name 33
The Approach of UBL
XML FormsWeb
Pages
DatabasesData-
modelsEDI
XML FormsWeb
Pages
Databases Data-models
EDI
The Real Worldmessages/documents
Conceptual View (BOV)logical models
Technology View (FSV)physical models
UNSM (UN Standard Messages)
Schemas(XML-Schemas, DTDs)
Directories
Core Component BIEs + Context
designan
alys
e
UBL basedXML-Schemas
impl
emen
t
? ? ?? ???
? ?
No common interface
description
Common interface
description
SAP AG 2001, Title of Presentation, Speaker Name 34
The modeling steps
1. Working from an xCBL document type, analyze its constituent constructs to identify BBIEs and ABIEs
2. Establish each BIE’s dictionary name, UBL name, definition, and business context
3. Establish its cardinality/optionality within its object class
4. Identify missing BIEs
5. Identify which BIEs are reusable
6. Assemble an appropriate UBL document type from the BIEs
SAP AG 2001, Title of Presentation, Speaker Name 35
Some major design rules developed so far
The choice of normative schema language
Naming and construction of elements, attributes, and types (mostly done) Fully qualified dictionary entry names with object class names Reusability by allowing properties (elements) to “inherit” parent object classes
(types), XPath-style “DeliveryScheduleID” and “OrderID” could both be represented by the element <ID> Each would be identifiable by means of //Order/ID and //DeliverySchedule/ID
respectively
Modularity, namespaces, and versioning (partial)
Embedded schema documentation (draft)
Handling code lists UBL will seek to import external datatype definitions in conventional XSD form Helping external organizations to create rigorous schemas Defining a unique UBL element for each kind of code
SAP AG 2001, Title of Presentation, Speaker Name 36
Mapping the CC world to XML and XSD
XSD has an indirect cascade of types and elements
XSD’s OO-like approach can neatly be mapped to ISO 11179 object classes and properties
Object ClassObject Class (complexType)
<xsd:complexType name="Coordination.Details"><xsd:sequence>
…</xsd:sequence>
</xsd:complexType>
Property (Element)Property (Element Declaration)<xsd:element name="SystemId“ type="Identifier.Type"/><xsd:element name="LongitudeMeasure“ type="Measure.Type"/><xsd:element name="LatitudeMeasure“ type="Measure.Type"/>
Type (Definition)«type»
M easure.Type
-M easure.Content : xsd:decim al-unitCode : xsd:token
Type (Definition)<xsd:complexType name="Measure.Type">
<xsd:simpleContent><xsd:extension base="xsd:decimal">
<xsd:attribute name="unitCode" type="xsd:token" use="required"/>
</xsd:extension></xsd:simpleContent>
</xsd:complexType>
hasreferences
is defined in terms ofis bound to
SAP AG 2001, Title of Presentation, Speaker Name 37
Header SummaryParty
Composition of a Building-Block-System
TradingPartnerProfile
Purchase Order
LineItem
<<Creates>>
CoreComp.
CoreComp.
CoreComp.
CoreComp
SupportedBusinessProcess
Contact
NameAddressIdentifier
Pric
ing Item
Identifier
Amount
Tax Amount
Value Tax
TextQuantity
CoreComp.
Identifier
Dat
eTim
e
Identifier
NameAddressIdentifier
Contact
NameAddressIdentifier
Amount
Value Tax
TextDat
eTim
e
Pric
ing Item
Identifier
Amount
Tax
QuantityContact
Identifier
Core Comp.
Dat
eTim
e
CoreComp.
Address Name Amount TextTax
<<Creates>>
<<References>>
<<References>>
SAP AG 2001, Title of Presentation, Speaker Name 38
Example of Core Components and Business Information Entities
Core Component Business Information Entity
SAP AG 2001, Title of Presentation, Speaker Name 39
Comparison of the Address structure of two different Standards
OAG xCBL
Differences in
tags & meaningsDifferences in
positions
Differences in informational content
Different information elements
SAP AG 2001, Title of Presentation, Speaker Name 40
UBL as a Meta-Structure
XSLT Scriptbased on
UBL Rules
OAG
xCBLXSLT-Processor
SAP AG 2001, Title of Presentation, Speaker Name 41
UBL as a Reference System
Class Diagram
UML2XML
Based onUBL-Rules
SAP AG 2001, Title of Presentation, Speaker Name 42
Overview
4 ebXML Core Components
5
Modelling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
Guidelines, Inputs & Outputs
SAP AG 2001, Title of Presentation, Speaker Name 43
Benefits of UBL
Leverages the ebXML Core Components effort by building ebXML-compliant and XML-specific document structures in conjunction with X12 and UN/EDIFACT
Is applicable across any sector or domain of electronic trade, transport, and administration
Plugs directly into existing traditional business practices and is interoperable with existing EDI systems
Fills the “payload” slot in B2B frameworks such as the UN/CEFACT & OASIS ebXML initiative (http://ebxml.org)
But it offers much more ….ebXML Registry & Repository
ebXML CCUBL CC
Business Document,(exp. Purchase Orders)
Part of Document(exp. Purchase Order Position)
Context(exp. Net. Amount)
Aggregate CoreComponent
Component 1Component 2
...
Definition of business
documents in particular
context
SAP AG 2001, Title of Presentation, Speaker Name 44
<Item><Id
schemeAgencyId=“19“>1234567890123</Id><Description>Strawberrys</Description><Quantity unitCode=“C62">15</Quantity><Amount currencyId=“USD“>14.12</Amount>
</Item>
Reusability of UBLCommon and normative structure and content definition will be a basis for
UBL Parser
Number Type Quantity UnitType Amount Currency1234567890123 Strawberry 15 Piece 14.12 USD1234567890124 Apples 24 Piece 12.34 USD… … … … … …
tables of databases
Items:Items:NumberNumber TypeType QuantityQuantity Amount Amount 1234567890123 Strawberrys 15 Piece 14.12 USD....
layouts for publishing of documents
objects ofworkflows
:Applicaton
Send: Item
Ask: Quantity
Send: Quantity
Ask: Amount
:XML
Send: Amount
Closed
business documents
Buyer Seller
BUY SALE
selection, comparison
Payment Invoicinginvoice
Order Supply
order or statistics
Reception DeliveryDelivery
data and interfacemodelling
ItemNumber: string
Type: stringStandard: string
QuantityValue: integer
UnitType: stringStandard: string
AmountValue: float
Currency: stringStandard: string
UBLa
b
c
d
e
f
g
h
i
m
l
n
j
k
Anya
cm
n
k
d
e
f
g
h
i
o
l
j
b
k
transformation into another structures
XML Query
XSL-FO
SOAP, ebXML MSG
UML2XML
XML Schema
XPointer,XLink
DOM, SAX, JSAX, JAXB
ebXML BPPS
XSLT
SAP AG 2001, Title of Presentation, Speaker Name 45
ProviderApplication
Seller
App
licat
ion
Buyer
App
licat
ion
RepositoryStand-ards Services Temp-
lates
Purchasing Process
Purchase Order
Purchase OrderResponse
Partner Profile
Partner Profile
Partner Agreement
Registry
Partner Services Product
Usability of UBL
Order
Order-Response
Catalog
Profiles
Partner-Profiles
ProfilesAgreement
Core Comp. &Documents
Templates & Standards
Display
Browser
Objects for Internal
Workflows
Partner Profiles, like Address, Communication,
Branch, Organizationname, etc..
Providing of Standardized Components
Templates and Standards of
Building Blocks and Documents
Products and Services
Visual Representation
Business Documents
Definition of User
Intefaces
SAP AG 2001, Title of Presentation, Speaker Name 46
ODETTE or AIAG
ISO or CEFACT
Distribution and Harmonization
EAN.UCC SWIFT
BMW Ford WalMart USB Deutsche Bank
SAP AG 2001, Title of Presentation, Speaker Name 47
UBL Benefits for Customers
Reduction of Total Cost of Ownership
Transparent and efficient interface naming and design rules: Minimization of the development effort for the mapping to other XML or EDI
message standards Better reusability of mapping content for different integration projects Reduction of integration costs
Harmonization and standardization of business objects: Better recognition of common business object semantic and structure Decrease of the training effort for the users
Transparent rules for customer specific interface modifications: Reduction of development costs regarding the modifications (design and run
time) Ease of business partner’s development regarding the support of the
modifications Possibility of feeding back the modifications to standard bodies in order to
trigger a harmonization of the industry standard
SAP AG 2001, Title of Presentation, Speaker Name 48
UBL Benefits for Software Vendor
Reduction of Total Cost of Ownership
Transparent and efficient interface naming and design rules: Minimization of the development effort for interface implementation Higher reusability of building blocks for different interface implementations Reduction of development costs
Harmonization and standardization of business objects: Better recognition of common business object semantic and structure Decrease of training effort and costs for development, support and
consultancy
Transparent rules for sector specific interface modifications: Reduction of development costs regarding the modifications (design and run
time) Possibility of feeding back the modifications to the internal standard
development in order to trigger a harmonization of the industry standard
SAP AG 2001, Title of Presentation, Speaker Name 49
Overview
4 ebXML Core Components
5
Modelling Steps6
2 Evolution & Success of Business Standards
UBL Initiative3
Summary8
Benefits7
1 What is XML?
Guidelines, Inputs & Outputs
SAP AG 2001, Title of Presentation, Speaker Name 50
Compare to:Criteria for successful
XML business standardization effort
UBL could be a successful XML business standardization effort
User-driven Royalty-free Not project driven Human- and machine-readable
Focused on Global Requirements Independent Normative status Compatible with existing EDI systems Designed for A2A and B2B
Clear development process and high quality documentation Feedback through early implementations Inclusion of business processes and business codes
Reuse of existing standards Completely based on XML technology Technically logical structure for simple implementation Common development and co-operation with relevant experts
Modularized structure Rules for extensibility, restrictibility and conclusive versioning Based on reusable building blocks Common repository for providing standardized modules
SAP AG 2001, Title of Presentation, Speaker Name 51
Summary
UBL defines XML based and ebXML compliant Core Components and Business Documents
ebXML enables individuals and small, midsized, and large companies to do eBusiness with anyone else over the Internet
Supports vertical and horizontal segments of industry and business participants
Business Documents and Core Components are multiuseable in business and technology
UBL & ebXML will move companies one more step closer to achieving quality and consistency in collaborative commerce
This is understood by big software vendors and competitors like SUN, Oracle, HP, IONA, SAP, CommerceOne etc.
Many of these software vendors and competitors are working on their implementations of UBL and ebXML CCTS yet.
SAP AG 2001, Title of Presentation, Speaker Name 52
Meeting schedule
The UBL TC meets only F2F; it has met four times since October/November 2001 We often try to co-locate with groups that we have liaisons with F2F #5 is 1-4 October 2002 in Burlington, MA, USA Email ballots are allowed by our rules
The larger SCs meet frequently by phone and do most work by email The main focus is the Library Content (LC) SC and the Naming and
Design Rules (NDR) SC
If you’re interested in joining, let me know You must be an organizational or individual OASIS member Individual membership is US$250/year
SAP AG 2001, Title of Presentation, Speaker Name 53
Where to find more information
OASIS UBL TC www.oasis-open.org/committees/ubl/ www.oasis-open.org/committees/ubl/lcsc/ www.oasis-open.org/committees/ubl/ndrsc/ www.oasis-open.org/committees/ubl/cmsc/ White papers, presentations, and specifications are available All mailing list archives are open to public view
ebXML www.ebxml.org
Core Components www.ebtwg.org
SAP AG 2001, Title of Presentation, Speaker Name 54
How to comment
The UBL comment list is open to the public Archive:
lists.oasis-open.org/archives/ubl-comment Signup:
lists.oasis-open.org/ob/adm.pl
The Library Content and NDR SCs have spreadsheet forms for providing feedback
SAP Gunther Stuhec ([email protected])
SAP AG 2001, Title of Presentation, Speaker Name 55