Date post: | 12-Jan-2016 |
Category: |
Documents |
Upload: | jonah-lucas-strickland |
View: | 215 times |
Download: | 0 times |
© OASIS 2003
The Key Role of OASIS Standards in Asian
e-Business
OASIS Open Standards DayOASIS Open Standards DayTokyo, 20 November 2003Tokyo, 20 November 2003
Karl Best, VP OASISKarl Best, VP OASIS
© OASIS 2003
oasis-open.orgoasis-open.org
Who is OASIS Introduction to ebXMLWhat are Web Services?What is required for web services to be
successfulThe need for web services standardsOASIS work in e-Business standards
Agenda
© OASIS 2003
Who is OASIS?
© OASIS 2003
oasis-open.orgoasis-open.orgOverview
OASIS is an international consortium dedicated to developing and promoting the adoption of e-business specifications
Member-elected Board of Directors and Technical Advisory Board; member-driven standards process
Members of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals, industry groups, and government agencies.
International, not-for-profit, open, independent Successful through industry-wide collaboration
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS technical work
The OASIS technical agenda is set by our members; bottom-up approach
Technical committees formed by the proposal of our members
Each TC sets its own scope, schedule, and deliverables
More than 60 Technical Committees in a variety of topic areas E-business Security Web services Public sector
© OASIS 2003
ebXML (Electronic Business XML)
© OASIS 2003
oasis-open.orgoasis-open.orgebXML Project
Joint initiative of UN/CEFACT and OASIS Phase 1: 1999-2001, initial specifications Phase 2: 2001-2003, enhancements and deployments
“Next generation” EDI Leverage XML, Web technology
Service-oriented architecture ebXML was designed for B2B transactional reliability
and enforceability
© OASIS 2003
oasis-open.orgoasis-open.orgebXML design requirements
Open availability Modularity Interoperability Vendor-neutrality Simplicity
These design rules have proven to be farsighted and effective guideposts for widespread, global electronic business
© OASIS 2003
oasis-open.orgoasis-open.orgebXML architecture
Business Process Specification Schema Core ComponentsCollaboration Protocol Profiles and
Agreements (originally “Trading Partner Agreements”)
Message Service (originally “Transport”) Registry & Repository
© OASIS 2003
oasis-open.orgoasis-open.orgebXML substantive layersBusiness Process Specification Schema (BPSS)
Public processes only, not for private processes Role-based, “neutral perspective” An XML document, capable of carrying many other types of content
Core Components (CC) A methodology for developing common, re-useable elemental data
objects, in place of the many competing document formats: EDIFACT, X12, xCBL, RosettaNet PIPs, OAGI BODs, Bolero DTDs, etc. etc.
Deliverable within XML documents Collaboration Protocol Profiles and Agreements (CPP/A)
Express capabilities of a partner to perform a role (CPP) Expresses bilateral agreement (CPA) on how to execute a shared
process XML documents
© OASIS 2003
oasis-open.orgoasis-open.orgebXML substantive layers Message Service (MSG)
Provides reliability and security XML message, based on SOAP standard Contains some simple business signals for systems
that can only process signals at the “envelope” level Registry & Repository
Information system for storing transactional artifacts, such as XML schemas, data elements, and supporting documents, as registered data objects (the repository) and their metadata (the registry).
Promotes efficient discovery and maintenance of re-usable data objects.
Ensures availability of authoritative XML, which promotes interoperability between trading partners.
© OASIS 2003
oasis-open.orgoasis-open.org
The birth of “web services” concepts
Components that provide a service to a user Human or computer based users Can be located anywhere
Grew from inside-the-firewall methods to coordinate multiple software systems of a single user Somewhat like traditional distributed object paradigms,
such as RMI or DCOM Works across multiple programming languages Interaction uses a service-specific interface Access through Internet-based protocols Synchronous (waits for a response) Did not address B2B functions such as reliability,
repudiation and business processes
© OASIS 2003
oasis-open.orgoasis-open.orgWeb services evolution
Through 2001 and 2002, vendors elaborated the concept of “web services” to extend into B2B applications
Multiple road maps for aggregating web services were published, some mutually exclusive
© OASIS 2003
What Are Web Services?
© OASIS 2003
oasis-open.orgoasis-open.orgWhat are Web Services?
Before Web Services, web-based e-Business was: Browsing of linked documents Manually initiated transactions & purchases Downloading files All initiated manually via a Web browser
Web Services is a model for using the Web to: Automatically initiate processes via the Web using programs Method for describing, publishing, promoting, registering, &
initiating processes dynamically in a distributed environment New ways of using the web, including intelligent agents,
marketplaces & auctions And… Not necessarily using a Web browser!
Actually, the Web is not required How about "Net Services?"
All done using XML standards
© OASIS 2003
oasis-open.orgoasis-open.orgA Web Services Scenario
Travel Agency Travel Network Hotel
Airline
Car RentalAgencyCredit Card
Network
Bank
Slide from Eve Maler, Sun Microsystems
Check availability, then reserve
Validate and authorize card
Collect itinerary data
Check availability, then reserve
Check availability, then reserve
Aggregate data; request
reservation
Request credit card
authorization
Route request to member bank
Request reservation
© OASIS 2003
oasis-open.orgoasis-open.orgWeb Services Terminology
Web Services-Interoperability (www.ws-i.org) defines “Basic Web Services” as applications built with: SOAP WSDL UDDI XML Schema
© OASIS 2003
oasis-open.orgoasis-open.org
Web Services Terminology (cont.)
W3C Web Services Architecture WG definition:
“A Web service is a software application identified by a URI, whose interfaces and bindings are capable of being defined, described and discovered as XML artifacts. A Web service supports direct interactions with other software agents using XML based messages via internet-based protocols.”
"Our definition of the term ‘Web Services’ does not presuppose the use of SOAP as a packaging format or a processing model. Nor does it presuppose the use of WSDL as a service description language....”
© W3C 2002
© OASIS 2003
oasis-open.orgoasis-open.org
Web Services Terminology (cont)
OASIS sees “web services like” approaches to building e-business platforms A continuum from “simple” to
“complex”, increasing in robustness, adoption, volume
e.g. ebXML can be considered as “complex web services”
© OASIS 2003
oasis-open.orgoasis-open.orgComplexity of Web Services
Simple No side effects Non-transactional Context free Session-less, no
roles Minimal security Call-response
model Point-to-point Not developmentally
scalable
Complex, e-Business Impacts other steps Transactional Context sensitive
conversions, ordering of steps
Session based, personalized
Exactly once semantics Sophisticated security Messaging based Scalable
© OASIS 2003
What is Required for Web Services to be Successful?
© OASIS 2003
oasis-open.orgoasis-open.org
Complete Picture
Complete set of specificationsInvolvement of broad spectrum of
vendors, users and implementors, government in the development of specifications
© OASIS 2003
oasis-open.orgoasis-open.org
What Makes Web Services Possible?
Reliable & Transparent Interconnectivity Web Protocols
Structured Information XML Schemas & validation
Application Interface Standards UDDI, WSDL, SOAP
Consistent Definitions Profiles, Test Suites & Scenarios
Business Process Interface Standards ebXML, BTP, WSBPEL, etc.
Security / Infrastructure Standards SAML, XACML, etc.
© OASIS 2003
oasis-open.orgoasis-open.org
Broad Participation
Global participation required, including from Asia
Government agencies can help drive development and adoption of standards through open standards processes Government-sponsored research and pilot
projects (e.g. Singapore IDA starting the OASIS FWSI TC; Hong Kong CECID development of open source ebXML software)
© OASIS 2003
oasis-open.orgoasis-open.org
Do’s and Don’ts of Web Services
Do: Participate in standards committees (W3C, OASIS, WS-I)
by offering real-world scenarios that can be used as test cases for ensuring reliable, secure, and high-performance Web services.
Participate in semantic committees (such as RosettaNet, ebXML, cXML and others) that are working on the descriptions of business documents for use in Web services.
Don’t: Wait for vendors to define the market for you; voice your
issues through the standards committees.
(Source: AMR Research, quoted in ZDNet 29 Oct 2003)
© OASIS 2003
oasis-open.orgoasis-open.org
Greatest Concern Preventing Adoption of Web services
“There's a sordid history in the technology world of everybody trying to get a little leverage over somebody else by developing proprietary extensions or vendor-specific add-ons to the core technology. In general, those have been bad, because they don't end up being sustainable over time and that costs companies like us a lot of money.”
CIO of a Fortune 100 corporation
© OASIS 2003
oasis-open.orgoasis-open.org
Issues Impacting Web Services for the Global Business Market
Moving proprietary WS specifications through an open standards process Core specifications (SOAP, WSDL) at W3C Registry specifications (UDDI, ebXML Registry)
at OASIS Infrastructure specifications (security,
management, business process, etc.) at OASIS Coordinating and demonstrating related
infrastructure standards Adapting industry business vocabularies and
business scenarios to WS framework
© OASIS 2003
The Need for Web Services Standards
© OASIS 2003
oasis-open.orgoasis-open.org
Formula for Sustainable StandardsM
arke
t Ado
ptio
n
Open Standardization
Traction
SanctionProprietary JCV Consortia SDO
SGMLISO
XMLW3C
SOAP v1.1 SOAP v1.2W3C
UDDI v2,3UDDI.org
WSDL v1.2W3C
ebMSG v2OASIS
WSDL v1.1
eb Reg v2OASISWS-S v1.0
BPEL4WS WS-BPELOASIS
WS-SOASISWS--*
? UDDI v2,3OASIS
© OASIS 2003
oasis-open.orgoasis-open.org
Delphi Group Research on the Value of Open Software Standards
Greatest benefit to support open standards1. Increases the value of existing and future investments in
information systems
2. Provides greater software re-usability
3. Enables greater data portability
Factors driving participation in standards1. Vendor neutral environment
2. Access to a community of developers
3. Membership comprised of both end-users and software developers
© OASIS 2003
oasis-open.orgoasis-open.org
Delphi Group Research on the Value of Open Software Standards
“Compliance with standards in software development is not simply a strategic direction, but a business imperative.”
“Even those who took a very practical approach and stated that standards might slow down their efforts initially, agreed that in the long run the presence of a standard represented a much more secure investment.”
© OASIS 2003
oasis-open.orgoasis-open.org
What Should an Open Standards Process Provide?
Opportunity to pursue technical work in a neutral environment – level playing field
Balanced participation by technology vendors, end users & governmental agencies
Opportunity to set the technical agenda – member driven
Active support from relevant industry associations Visibility and sanction by an internationally
recognized standards body
© OASIS 2003
OASIS Work in e-Business Standards
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS TCs
Total of 63 TCs at OASIS Supply Chain E-Business Web Services Security Public Policy Conformance XML Languages Industry specific
© OASIS 2003
oasis-open.orgoasis-open.orgNew OASIS PPS TC
Production Planning and Scheduling (PPS) TC
Convener: Prof. Yasuyuki NishiokaFirst meeting: 18 December, TokyoLanguage: JapanesePurpose: Develop common object
models and XML schema for production planning and scheduling in manufacturing
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Supply Chain TCs
Electronic Procurement Standardization
Materials Markup LanguageProduct Life Cycle SupportProduction Planning and
Scheduling
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS E-Business TCs
Business TransactionsBusiness-Centric MethodologyContent Assembly MechanismControlled Trade Markup LanguageDirectory Services Markup LanguageebXML Business ProcessebXML Collaboration Protocol Profile
and AgreementebXML Implementation, Interoperability
and Conformance
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS E-Business TCs (cont.)
ebXML Messaging ServicesebXML RegistryManagement Protocol (completed)UDDI SpecificationUniversal Business LanguageWeb Services Business Process
Execution Language
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Security TCs
Application Vulnerability Description Language
Digital Signature ServiceseXtensible Access Control Markup
LanguageProvisioning ServicesPublic Key InfrastructureRights Language
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Security TCs (cont.)
Security ServicesWeb Application SecurityWeb Services SecurityXML Common Biometric Format
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Web Services TCs
Asynchronous Service Access ProtocolFramework for Web Services
ImplementationWeb Services Business Process
Execution LanguageWeb Services Composite Application
FrameworkWeb Services Distributed Management
© OASIS 2003
oasis-open.orgoasis-open.org
OASIS Web Services TCs (cont.)
Web Services for Remote PortletsWeb Services Interactive
Applications (completed)Web Services Reliable MessagingWeb Services Security
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Public Policy TCs
Controlled Trade Markup LanguageEducatione-GovernmentElection and Voter ServicesEmergency ManagementLegalXML eContractsLegalXML Electronic Court FilingLegalXML eNotarizationLegalXML Integrated Justice
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Public Policy TCs (cont.)
LegalXML Integrated JusticeLegalXML Lawful InterceptLegalXML Legal TranscriptsLegalXML Legislative Documents,
Citations, and MessagingLegalXML Online Dispute ResolutionTax XML
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS Industry Focus TCs
Automotive Repair InformationCustomer Information QualityDocBookHumanMarkupOpen Office XML FormatTranslation Web ServicesUser Interface Markup LanguageXML Localisation Interchange File
Format
© OASIS 2003
oasis-open.orgoasis-open.orgOASIS XML Language TCs
Entity ResolutionExtensible Resource IdentifierRELAX NGTopic Maps Published Subjects for
Geography and LanguagesTopic Maps Published SubjectsTopic Maps Vocabulary for XML
Standards and Technologies
© OASIS 2003
oasis-open.orgoasis-open.orgApproved OASIS Standards
Directory Services Markup Language (DSML) v2.0, Apr 2002
DocBook v4.1, Jan 2001ebXML Collaborative Partner Profile
Agreement (CPPA) v2.0, Nov 2002ebXML Messaging Service Specification
v2.0, Aug 2002ebXML Registry Information Model
(RIM) v2.0, Apr 2002ebXML Registry Services Specification
(RS) v2.0, Apr 2002
© OASIS 2003
oasis-open.orgoasis-open.org
Approved OASIS Standards (cont.)
Extensible Access Control Markup Language (XACML) v1.0, Feb 2003
Security Assertion Markup Language (SAML) v1.0, Nov 2002
Security Assertion Markup Language (SAML) v1.1, Aug 2003
Service Provisioning Markup Language (SPML) v1.0, Oct 2003
UDDI v2.0, Apr 2003 Web Services for Remote Portlets (WSRP)
v1.0, Aug 2003 XML Common Biometric Format (XCBF) v1.1,
Aug 2003
www.xml.org www.xml.coverpages.org
www.oasis-open.org