XML (e-business) Standards State of the Union Norbert H. Mikula Chief Technology Strategist DataChannel.

XML (e-business) Standards State of the Union Norbert H. Mikula Chief Technology Strategist DataChannel

Agenda State of the Union State of the Union About OASIS About OASIS E-business @ OASIS E-business @ OASIS Q&A Q&A

State of the union ? It is a mess !

State of the union ?

We need a map !

B2B Conceptual Model Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

About OASIS OASIS is a member consortium dedicated to building systems interoperability specifications OASIS is a member consortium dedicated to building systems interoperability specifications We focus on industry applications of structured information standards, such as XML, SGML, and CGM. We focus on industry applications of structured information standards, such as XML, SGML, and CGM. Members of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals and industry groups. Members of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals and industry groups.  ~200 organizational members, ~200 individual members International, Not-for-profit, Open, Independent International, Not-for-profit, Open, Independent Successful through industry-wide collaboration Successful through industry-wide collaboration

OASIS standards process Standards are created under an open, democratic, vendor-neutral process Standards are created under an open, democratic, vendor-neutral process  Any interested parties may participate, comment  No one organization can dictate the standard  Ensures that standards meet everyone’s needs, not just largest players’ Open to all interested parties Open to all interested parties All discussion open to public comment All discussion open to public comment One organization/One vote One organization/One vote Resulting work is guaranteed to be representative of the industry as a whole, not just any one vendor’s view Resulting work is guaranteed to be representative of the industry as a whole, not just any one vendor’s view

What OASIS Offers Industry Time to Market: don’t waste your time and effort setting up Time to Market: don’t waste your time and effort setting up  Committee process  Infrastructure (web site, mail lists)  IPR policy  Copyright protection  Program Management  Marketing/Promotion  Anti-trust Use your technical expertise on technical work, not on setting up administrative overhead Use your technical expertise on technical work, not on setting up administrative overhead

What OASIS Offers Members Opportunity to pursue technical work in a neutral environment Opportunity to pursue technical work in a neutral environment  Buy-in and support from other developing and implementing organizations Opportunity to set the technical agenda of a recognized industry standards organization Opportunity to set the technical agenda of a recognized industry standards organization  OASIS member-driven technical process

OASIS Process Existing technical work submitted to OASIS TC; or TC starts work at the beginning Existing technical work submitted to OASIS TC; or TC starts work at the beginning TC completes technical work TC completes technical work TC votes to approve work as an OASIS Committee Specification TC votes to approve work as an OASIS Committee Specification TC votes to submit the Committee Specification to OASIS membership for consideration TC votes to submit the Committee Specification to OASIS membership for consideration OASIS membership reviews, approves the Committee Specification as an OASIS Standard OASIS membership reviews, approves the Committee Specification as an OASIS Standard

Current Activities Currently 20 OASIS Technical Committees and one Member Section Currently 20 OASIS Technical Committees and one Member Section Increase of over a dozen new TCs since late 2000 Increase of over a dozen new TCs since late 2000 Additional proposals in the works... Additional proposals in the works... Expect to have 6-8 TCs submitting Committee Specifications to OASIS membership for review by the end of 2001 Expect to have 6-8 TCs submitting Committee Specifications to OASIS membership for review by the end of 2001

Access Control (XACML) Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Access Control (XACML) Started: May 2001 Started: May 2001 Charter: Develop XACML, an XML specification for expressing policies for information access over the Internet. Charter: Develop XACML, an XML specification for expressing policies for information access over the Internet. Co-chairs: Carlisle Adams, Entrust; Hal Lockhart, Entegrity Co-chairs: Carlisle Adams, Entrust; Hal Lockhart, Entegrity

Access Control - XACML "Access control, which is often called 'rights management' or 'entitlement management,' determines who can look at something, what they can do with it, the type of device they can look at it on, etc." Simon Y. Blackwell, Psoom, Chair (ret.)

Access Control - XACML Ex. Use Case : Medical Records Ex. Use Case : Medical Records  Selectively disclose sensitive information depending on requestor and situation. E.g. patient rights vs. patient protection. Ex. Use Case : Registries Ex. Use Case : Registries  Selectively grant access of registry content to specific customers, suppliers and business partners.  Business Objects, CPP, Business Processes contain proprietary information.

Security Services (SAML) Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Security Services (SAML) What is the most annoying thing in working with ten different e-business sites? What is the most annoying thing in working with ten different e-business sites?

Security Services (SAML) Started: March 2001 Started: March 2001 Charter: combine AuthXML and S2ML (and others) into a single XML specification for the description of authentication and authorization of internet communications Charter: combine AuthXML and S2ML (and others) into a single XML specification for the description of authentication and authorization of internet communications Co-chairs: Jeff Hodges, Oblix; Joe Pato, HP Co-chairs: Jeff Hodges, Oblix; Joe Pato, HP

Security Services Ex. Use Case : Single Sign-On Ex. Use Case : Single Sign-On  A Web user authenticates with a Web site. The Web user then uses a secured resource at another Web site, without directly authenticating to that Web site. Ex. User Case : Authorization Service Ex. User Case : Authorization Service  A user attempts to access a resource or service. The security controller for that resource -- a policy enforcement point or PEP -- checks the user's authorization to access the resource with a policy decision point or PDP.

Directory Services (DSML) Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Directory Services (DSML) Started: 1999 Started: 1999 Charter: develop DSML, an XML- specification for marking up directory services information Charter: develop DSML, an XML- specification for marking up directory services information Chair: James Tauber, Bowstreet Chair: James Tauber, Bowstreet Latest Version DSML 2.0 (adds directory queries and updates) Latest Version DSML 2.0 (adds directory queries and updates)

Business Transaction Protocol Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Business Transaction Protocol Started: March 2001 Started: March 2001 Charter: develop the Business Transaction Protocol (BTP), an XML- based protocol for managing complex, persistent B2B Internet transactions Charter: develop the Business Transaction Protocol (BTP), an XML- based protocol for managing complex, persistent B2B Internet transactions Chair: Pal Takacsi-Nagy, BEA Chair: Pal Takacsi-Nagy, BEA

Business Transaction Protocol ACID ACID Two phased commit Two phased commit Internet scales distributed transactions Internet scales distributed transactions  E.g. : Semantics of roll-back?

Business Transaction Protocol Ex. Use Case : A night out Ex. Use Case : A night out  The individual concerned uses a Personal Digital Organizer (PDA) to control the activities required for making the necessary arrangements with different service providers (e.g., “Taxi,” “Theatre,” “Restaurant,” and “Hotel”). The different activities are to be enclosed within the borders of a single long-running business transaction to achieve an all-or-nothing result and to accommodate for failures. Ex. Use Case : Manufacturer-Supplier- Shipper Ex. Use Case : Manufacturer-Supplier- Shipper

ebXML Collaborative Partners Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

ebXML Collaborative Partners Started: July 2001 Started: July 2001 Charter: continued development of ebXML CPP and CPA specifications Charter: continued development of ebXML CPP and CPA specifications Chair: Dale Moberg, Cyclone Commerce Chair: Dale Moberg, Cyclone Commerce

ebXML Collaborative Partners A CPP defines one business partner's technical capabilities to engage in electronic business collaborations with other partners by exchanging electronic messages. A CPP defines one business partner's technical capabilities to engage in electronic business collaborations with other partners by exchanging electronic messages. A CPA documents the technical agreement between two (or more) partners to engage in electronic business collaboration. A CPA documents the technical agreement between two (or more) partners to engage in electronic business collaboration.

ebXML Messaging Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

ebXML Messaging Started: July 2001 Started: July 2001 Charter: continue development of the ebXML Messaging specification Charter: continue development of the ebXML Messaging specification Recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies. Recommend technology for the transport, routing and packaging of business transactions using standard Internet technologies. Chair: Ian Jones, individual member Chair: Ian Jones, individual member

ebXML Registry Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

ebXML Registry Started: 1999 Started: 1999 Charter: continue development of ebXML Registry & Repository specification, merge with OASIS Registry & Repository specification Charter: continue development of ebXML Registry & Repository specification, merge with OASIS Registry & Repository specification Chair: Lisa Carnahan, NIST Chair: Lisa Carnahan, NIST

ebXML Registry The ebXML Registry provides a set of services that enable sharing of information between interested parties for the purpose of enabling business process integration between such parties based on the ebXML specifications. The shared information is maintained as objects in a repository and managed by the ebXML Registry Services. The ebXML Registry provides a set of services that enable sharing of information between interested parties for the purpose of enabling business process integration between such parties based on the ebXML specifications. The shared information is maintained as objects in a repository and managed by the ebXML Registry Services.

ebXML Registry (Use Case) Schema Documents Are Submitted Schema Documents Are Submitted  A third party such as an industry consortium or standards group submits the necessary schema documents required by the RosettaNet PIP3A4 Purchase Order business protocol with the Registry using the ObjectManager service of the Registry. Business Process Documents Are Submitted Business Process Documents Are Submitted  A third party, such as an industry consortium or standards group, submits the necessary business process documents required by the RosettaNet PIP3A4 Purchase Order business protocol with the Registry using the ObjectManager service of the Registry.

ebXML Registry (Use Case) Seller’s Collaboration Protocol Profile Is Submitted Seller’s Collaboration Protocol Profile Is Submitted  The seller publishes its Collaboration Protocol Profile or CPP to the Registry. The CPP describes the seller, the role it plays, the services it offers and the technical details on how those services may be accessed. The seller classifies their Collaboration Protocol Profile using the Registry’s flexible Classification capabilities. Buyer Discovers The Seller Buyer Discovers The Seller  The buyer browses the Registry using Classification schemes defined within the Registry using a Registry Browser GUI tool to discover a suitable seller. For example the buyer may look for all parties that are in the Automotive Industry, play a seller role, support the RosettaNet PIP3A4 process and sell Car Stereos. The buyer discovers the seller’s CPP and decides to engage in a partnership with the seller.

Universal Business Library Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Universal Business Language Started: October 2001 Started: October 2001 Charter: develop a standard XML business library based on other pre- existing libraries Charter: develop a standard XML business library based on other pre- existing libraries Chair: Jon Bosak, Sun Chair: Jon Bosak, Sun Current status: first meeting October 2001 Current status: first meeting October 2001

Universal Business Language Top down vs. bottom up? Top down vs. bottom up? UBL: Bottom up UBL: Bottom up

Universal Business Language Begin with xCBL 3.0 as the starting point and to develop the standard UBL library by mutually agreed-upon changes to xCBL 3.0 based on industry experience with other XML business libraries and with similar technologies such as Electronic Data Interchange. Begin with xCBL 3.0 as the starting point and to develop the standard UBL library by mutually agreed-upon changes to xCBL 3.0 based on industry experience with other XML business libraries and with similar technologies such as Electronic Data Interchange. Develop UBL in light of standards/specifications issued by UN/CEFACT, ISO, IEC, ITU, W3C, IETF, OASIS, and such other standards bodies and organizations as the UBL TC may deem relevant. Develop UBL in light of standards/specifications issued by UN/CEFACT, ISO, IEC, ITU, W3C, IETF, OASIS, and such other standards bodies and organizations as the UBL TC may deem relevant.

RELAX NG Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

RELAX NG Started: February 2001 Started: February 2001 Charter: combine TREX and RELAX proposals into a single light-weight XML schema specification Charter: combine TREX and RELAX proposals into a single light-weight XML schema specification Chair: James Clark, individual member Chair: James Clark, individual member Current status: Committee Specification approved; will submit to OASIS membership soon Current status: Committee Specification approved; will submit to OASIS membership soon

Entity Resolution Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Entity Resolution Started: November 2000 Started: November 2000 Charter: further development of SGML Open Catalog Specification (TR 9401:1997; “SOCat”) for XML compliance Charter: further development of SGML Open Catalog Specification (TR 9401:1997; “SOCat”) for XML compliance Chair: Lauren Wood, SoftQuad Chair: Lauren Wood, SoftQuad Current status: Committee Specification approved; will submit to OASIS membership soon Current status: Committee Specification approved; will submit to OASIS membership soon

TM Published Subjects Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Topic Maps 101 Transcend Syntax ! Eliot Kimber, DataChannel/Isogen

Topic Maps 101 XYZ A concept: XYZ A concept: XYZ Web

Topic Maps 101 First topic map concept : Topic First topic map concept : Topic  Fundamental unit  Meaningful description of an information object <topname><basename>XYZ</basename></topname></topic>

Topic Maps 101 A topic, in its most generic sense, can be any “thing” whatsoever – a person, an entity, a concept, really anything – regardless of whether it exists or has any other specific characteristics, about which anything whatsoever may be asserted by any means whatsoever.

Topic Maps 101 Extend the concept Extend the concept <topname><basename>XYZ</basename> XYZ Company XYZ Company <sortname>XYZCompany</sortname></topname></topic>

Topic Maps 101 The topic occurs somewhere The topic occurs somewhere  (on the Web) XYZ Web

Topic Maps 101 Second topic map concept : Occurrences Second topic map concept : Occurrences  Path between a topic and an information object (in this case a HTML page)<occurshref="http://xyz.com/serverdoc.htm"></occurs>

Topic Maps 101 Some information about an occurrence Some information about an occurrence Press Release Documentation XYZ Web

Topic Maps 101 Occurrences are typed Occurrences are typed<occurstype=“Documentation”href="http://xyz.com/serverdoc.htm"></occurs><occurs type=“Press Release” href="http://xyz.com/news/ceo.htm"></occurs>

Topic Maps 101 Topic Characteristics Topic Characteristics  Atomic Name  Occurrence(s) Must have at least one of them Must have at least one of them

Topic Maps 101 Web There is more than one topic There is more than one topic ABC NASDAQ Press Release Documentation XYZ

Topic Maps 101 And topics have typed relationships And topics have typed relationships trading compete Web NASDAQ Press Release Documentation XYZ ABC

Topic Maps 101 Third topic map concept : Associations Third topic map concept : Associations  Relationship between topics  Association types are topics XYZ ABC XYZ ABC

Topic Maps 101 Topics participating in an association have roles Topics participating in an association have roles  role types are again … topics NASDAQ NASDAQ</assocrl> XYZ XYZ</assocrl>

Topic Maps 101 Fourth topic map concept : Topic type Fourth topic map concept : Topic type  Form a class-instance relationship Topic types are again a topic Topic types are again a topic ABC Company Market NASDAQ XYZ trading compete

Topic Maps 101 Topic types can participate in associations Topic types can participate in associations Which are again … (you get the picture) Which are again … (you get the picture) listed ABC Company Market NASDAQ XYZ trading compete

Topic Maps 101 Fifth topic map concept : Scope Fifth topic map concept : Scope  Compare to scope in programming languages XYZ Inc. XYZ Inc. </topname> XYZ Ges.m.b.H. XYZ Ges.m.b.H. </topname></topic>

Topic Maps 101 There are more topic maps concepts There are more topic maps concepts  Themes  Facets  Public Subjects  Etc. Exercise for the reader … Exercise for the reader …

Topic Maps 101 ISO 13250 ISO 13250  Editors : Michel Biezunski, Martin Bryan, Steve Newcomb  Uses HyTime  ISO 10744  Editors : Charles Goldfarb, Steven Newcomb, Eliot Kimber, Peter Newcomb Topic Maps for the Web Topic Maps for the Web  XTM, IdeAlliance initiative  XTM 1.0 (March 2 nd, 2001)

Topic Maps 101 Topic Maps Definitions (from ISO 13250) Topic Maps Definitions (from ISO 13250)  “… enable multiple, concurrent views of sets of information objects”  “… link topics together in such a way as to enable navigation between them.”  “… filter an information set to create views adapted to specific users or purposes.”  “… facilitate the creation of topic-oriented user interfaces that provide the effect of merging unstructured information bases with structured ones.”

Topic Maps 101 “ Widespread implementation of non- proprietary semantic navigation networks is good for the Web. ISO 13250:2000 topic maps should be given full consideration by developers, content providers, builders of portals, and supporters of open standards and an open Web.”  Liora Alschuler on XML.com

TM Published Subjects Started: October 2001 Started: October 2001 Charter: develop guidelines, recommendations, and applications to promote adoption of Topic Maps Published Subjects (part of ISO 13250 and XML Topic Maps (XTM) 1.0 Specification). Charter: develop guidelines, recommendations, and applications to promote adoption of Topic Maps Published Subjects (part of ISO 13250 and XML Topic Maps (XTM) 1.0 Specification). Chair: Bernard Vatant, Mondeca Chair: Bernard Vatant, Mondeca Current status: first meeting October 2001 Current status: first meeting October 2001

WS Component Model Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

WS Component Model Started: October 2001 Started: October 2001 Charter: To create a Web Services standard for interactive application access. WSCM will provide a coordinated set of XML vocabularies and Web services interfaces that allow companies to deliver Web applications to end users through a variety of channels--directly to a browser, indirectly through a portal or embedded into a third party Web application. Charter: To create a Web Services standard for interactive application access. WSCM will provide a coordinated set of XML vocabularies and Web services interfaces that allow companies to deliver Web applications to end users through a variety of channels--directly to a browser, indirectly through a portal or embedded into a third party Web application. Chair: Charles Wiecha, IBM Chair: Charles Wiecha, IBM

Customer Information Quality Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Customer Information Quality Started: early 2000 Started: early 2000 Charter: develop XML-based specifications for customer profile and addressing information Charter: develop XML-based specifications for customer profile and addressing information Chair: Ram Kumar, Mastersoft Chair: Ram Kumar, Mastersoft Current status: two Committee Specifications approved; will submit to OASIS membership soon; on-going work with other specs Current status: two Committee Specifications approved; will submit to OASIS membership soon; on-going work with other specs

Provisioning Services Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

Provisioning Services Started: November 2001 Started: November 2001 Charter: combine the existing Active Digital Profile (ADPr), extensible Resource Provisioning Management (XRPM), and Information Technology Markup Language (ITML) specifications into a single specification describing provisioning information Charter: combine the existing Active Digital Profile (ADPr), extensible Resource Provisioning Management (XRPM), and Information Technology Markup Language (ITML) specifications into a single specification describing provisioning information Chair: Gavenraj Sodhi, Access360 Chair: Gavenraj Sodhi, Access360 Current status: first meeting in November Current status: first meeting in November

DocBook Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

DocBook Started: 1992; moved to OASIS in 1998 Started: 1992; moved to OASIS in 1998 Charter: develop the DocBook DTD/Schema for computer documentation Charter: develop the DocBook DTD/Schema for computer documentation Chair: Norm Walsh, Sun Chair: Norm Walsh, Sun Current status: v4.1 accepted as an OASIS Standard in January 2001; working towards v5. Current status: v4.1 accepted as an OASIS Standard in January 2001; working towards v5.

Conformance Management S e c u r i t y Core XML Standards Backend Integration Service Oriented Architectures Network Transport Business Conceptual Model (Definitions, format, structure, and choreography) Technical Conceptual Model (Standards, protocols and tools) Universal Business Processes Specialized Business Processes Business Process Instance Universal Business Content Specialized Business Content Business Content Instance Messaging Service Description Language Repository Directory / Registry Business Content Format Definition Process Description Language Trading Partner Agreement

XML Conformance Started: 1999 Started: 1999 Charter: develop test suites for testing XML application conformance against the W3C XML Recommendation Charter: develop test suites for testing XML application conformance against the W3C XML Recommendation Chair: Mary Brady, NIST Chair: Mary Brady, NIST Current status: work completed summer 2001; will be basis for future work in W3C QA Activity Current status: work completed summer 2001; will be basis for future work in W3C QA Activity

XSLT Conformance Started: 1999 Started: 1999 Charter: develop test suites for testing XSLT application conformance against the W3C XSLT Recommendation Charter: develop test suites for testing XSLT application conformance against the W3C XSLT Recommendation Chair: Ken Holman, Crane SoftWrights Chair: Ken Holman, Crane SoftWrights

ebXML IIC Started: August 2001 Started: August 2001 IIC IIC  Implementation, Interoperability, Conformance Charter: develop guidelines and tools for interoperability, implementation, and conformance of the ebXML specs in order to promote the adoption of the specs Charter: develop guidelines and tools for interoperability, implementation, and conformance of the ebXML specs in order to promote the adoption of the specs Chair: Philippe DeSmedt, Agentis Int’l Chair: Philippe DeSmedt, Agentis Int’l Current status: work in progress Current status: work in progress

Conformance Started: 1999 Started: 1999 Charter: develop guidelines and resources for the creation of conformance test suites Charter: develop guidelines and resources for the creation of conformance test suites Chair: Lynne Rosenthal, NIST Chair: Lynne Rosenthal, NIST Current status: ongoing work in progress; a variety of white papers and test tools released Current status: ongoing work in progress; a variety of white papers and test tools released

Announcement OASIS public information meeting on Web Services standards (the WSCM effort and related work at OASIS) OASIS public information meeting on Web Services standards (the WSCM effort and related work at OASIS) OASIS will host the meeting at 6:30 PM on Wednesday, 24 Oct, in Room 203 at the Santa Clara Convention Center. OASIS will host the meeting at 6:30 PM on Wednesday, 24 Oct, in Room 203 at the Santa Clara Convention Center. Refreshments will be provided and everyone is welcome to attend. Refreshments will be provided and everyone is welcome to attend.

Q&A Thanks !

XML (e-business) Standards State of the Union Norbert H. Mikula Chief Technology Strategist DataChannel.

Similar presentations

Presentation on theme: "XML (e-business) Standards State of the Union Norbert H. Mikula Chief Technology Strategist DataChannel."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

XML (e-business) Standards State of the Union Norbert H. Mikula Chief Technology Strategist DataChannel.

Similar presentations

Presentation on theme: "XML (e-business) Standards State of the Union Norbert H. Mikula Chief Technology Strategist DataChannel."— Presentation transcript:

Similar presentations

About project

Feedback