xml (e-business) standards state of the union norbert h. mikula chief technology strategist...
TRANSCRIPT
XML (e-business) StandardsState of the Union
Norbert H. MikulaNorbert H. MikulaChief Technology StrategistChief Technology StrategistDataChannelDataChannel
Agenda
State of the UnionState of the Union
About OASISAbout OASIS
E-business @ OASISE-business @ OASIS
Q&AQ&A
State of the union ?
It is a mess !
State of the union ?
State of the union ?
State of the union ?
We need a map !
B2B Conceptual Model
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
B2B Conceptual Model
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Agenda
State of the UnionState of the Union
About OASISAbout OASIS
E-business @ OASISE-business @ OASIS
Q&AQ&A
About OASIS
OASIS is a member consortium dedicated to OASIS is a member consortium dedicated to building systems interoperability specificationsbuilding systems interoperability specifications
We focus on industry applications of structured We focus on industry applications of structured information standards, such as XML, SGML, and information standards, such as XML, SGML, and CGM. CGM.
Members of OASIS are providers, users and Members of OASIS are providers, users and specialists of standards-based technologies and specialists of standards-based technologies and include organizations, individuals and industry include organizations, individuals and industry groups. groups. ~200 organizational members, ~200 individual members
International, Not-for-profit, Open, IndependentInternational, Not-for-profit, Open, Independent Successful through industry-wide collaborationSuccessful through industry-wide collaboration
OASIS standards process
Standards are created under an open, Standards are created under an open, democratic, vendor-neutral processdemocratic, 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 partiesOpen to all interested parties All discussion open to public commentAll discussion open to public comment One organization/One voteOne organization/One vote Resulting work is guaranteed to be Resulting work is guaranteed to be
representative of the industry as a whole, not representative of the industry as a whole, not just any one vendor’s viewjust any one vendor’s view
What OASIS Offers Industry
Time to Market: don’t waste your time and Time to Market: don’t waste your time and effort setting upeffort 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 Use your technical expertise on technical work, not on setting up administrative work, not on setting up administrative overheadoverhead
What OASIS Offers Members
Opportunity to pursue technical work in a Opportunity to pursue technical work in a neutral environmentneutral environment Buy-in and support from other developing and
implementing organizations
Opportunity to set the technical agenda of Opportunity to set the technical agenda of a recognized industry standards a recognized industry standards organizationorganization OASIS member-driven technical process
OASIS Process
Existing technical work submitted to OASIS TC; Existing technical work submitted to OASIS TC; or TC starts work at the beginningor TC starts work at the beginning
TC completes technical workTC completes technical work TC votes to approve work as an TC votes to approve work as an OASIS OASIS
Committee SpecificationCommittee Specification TC votes to submit the TC votes to submit the Committee SpecificationCommittee Specification
to OASIS membership for considerationto OASIS membership for consideration OASIS membership reviews, approves the OASIS membership reviews, approves the
Committee SpecificationCommittee Specification as an as an OASIS StandardOASIS Standard
Current Activities
Currently 20 OASIS Technical Committees Currently 20 OASIS Technical Committees and one Member Sectionand one Member Section
Increase of over a dozen new TCs since Increase of over a dozen new TCs since late 2000late 2000
Additional proposals in the works... Additional proposals in the works... Expect to have 6-8 TCs submitting Expect to have 6-8 TCs submitting
Committee Specifications to OASIS Committee Specifications to OASIS membership for review by the end of 2001membership for review by the end of 2001
Agenda
State of the UnionState of the Union
About OASISAbout OASIS
E-business @ OASISE-business @ OASIS
Q&AQ&A
Access Control (XACML)
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Access Control (XACML)
Started: May 2001Started: May 2001 Charter: Develop XACML, an XML Charter: Develop XACML, an XML
specification for expressing policies for specification for expressing policies for information access over the Internet.information access over the Internet.
Co-chairs: Co-chairs: Carlisle Adams, Entrust; Hal Carlisle Adams, Entrust; Hal Lockhart, EntegrityLockhart, Entegrity
Access Control - XACML
"Access control, which is often called 'rights "Access control, which is often called 'rights management' or 'entitlement management' or 'entitlement
management,' determines who can look at management,' determines who can look at something, what they can do with it, the something, what they can do with it, the
type of device they can look at it on, etc."type of device they can look at it on, etc."
Simon Y. Blackwell, Psoom, Chair (ret.)
Access Control - XACML
Ex. Use Case : Medical RecordsEx. Use Case : Medical Records Selectively disclose sensitive information
depending on requestor and situation. E.g. patient rights vs. patient protection.
Ex. Use Case : RegistriesEx. 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)
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Security Services (SAML)
What is the most annoying thing in What is the most annoying thing in working with ten different e-business working with ten different e-business sites?sites?
Security Services (SAML)
Started: March 2001Started: March 2001 Charter: combine AuthXML and S2ML Charter: combine AuthXML and S2ML
(and others) into a single XML (and others) into a single XML specification for the description of specification for the description of authentication and authorization of authentication and authorization of internet communicationsinternet communications
Co-chairs: Jeff Hodges, Oblix; Joe Pato, Co-chairs: Jeff Hodges, Oblix; Joe Pato, HPHP
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)
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Directory Services (DSML)
Started: 1999Started: 1999 Charter: develop DSML, an XML-Charter: develop DSML, an XML-
specification for marking up directory specification for marking up directory services informationservices information
Chair: James Tauber, BowstreetChair: James Tauber, Bowstreet Latest Version DSML 2.0 (adds directory Latest Version DSML 2.0 (adds directory
queries and updates)queries and updates)
Business Transaction Protocol
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Business Transaction Protocol
Started: March 2001Started: March 2001 Charter: develop the Business Charter: develop the Business
Transaction Protocol (BTP), an XML-Transaction Protocol (BTP), an XML-based protocol for managing complex, based protocol for managing complex, persistent B2B Internet transactionspersistent B2B Internet transactions
Chair: Pal Takacsi-Nagy, BEAChair: Pal Takacsi-Nagy, BEA
Business Transaction Protocol
ACIDACID
Two phased commitTwo phased commit
Internet scales distributed transactionsInternet scales distributed transactions E.g. : Semantics of roll-back?
Business Transaction Protocol
Ex. Use Case : A night outEx. 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-Ex. Use Case : Manufacturer-Supplier-ShipperShipper
ebXML Collaborative Partners
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
ebXML Collaborative Partners
Started: July 2001Started: July 2001 Charter: continued development of ebXML Charter: continued development of ebXML
CPP and CPA specificationsCPP and CPA specifications Chair: Dale Moberg, Cyclone CommerceChair: Dale Moberg, Cyclone Commerce
ebXML Collaborative Partners
A CPP defines one business partner's A CPP defines one business partner's technical capabilities to engage in technical capabilities to engage in electronic business collaborations with electronic business collaborations with other partners by exchanging electronic other partners by exchanging electronic messages.messages.
A CPA documents the technical A CPA documents the technical agreement between two (or more) agreement between two (or more) partners to engage in electronic business partners to engage in electronic business collaboration.collaboration.
ebXML Messaging
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
ebXML Messaging
Started: July 2001Started: July 2001 Charter: continue development of the Charter: continue development of the
ebXML Messaging specificationebXML Messaging specification Recommend technology for the transport, Recommend technology for the transport,
routing and packaging of business routing and packaging of business transactions using standard Internet transactions using standard Internet technologies.technologies.
Chair: Ian Jones, individual memberChair: Ian Jones, individual member
ebXML Registry
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
ebXML Registry
Started: 1999Started: 1999 Charter: continue development of ebXML Charter: continue development of ebXML
Registry & Repository specification, Registry & Repository specification, merge with OASIS Registry & Repository merge with OASIS Registry & Repository specification specification
Chair: Lisa Carnahan, NISTChair: Lisa Carnahan, NIST
ebXML Registry
The ebXML Registry provides a set of The ebXML Registry provides a set of services that enable sharing of services that enable sharing of information between interested parties for information between interested parties for the purpose of enabling business process the purpose of enabling business process integration between such parties based integration between such parties based on the ebXML specifications. The shared on the ebXML specifications. The shared information is maintained as objects in a information is maintained as objects in a repository and managed by the ebXML repository and managed by the ebXML Registry Services.Registry Services.
ebXML Registry (Use Case)
Schema Documents Are SubmittedSchema 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 Business Process Documents Are SubmittedSubmitted 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 Seller’s Collaboration Protocol Profile Is SubmittedSubmitted 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 SellerBuyer 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
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Universal Business Language
Started: October 2001Started: October 2001 Charter: develop a standard XML Charter: develop a standard XML
business library based on other pre-business library based on other pre-existing librariesexisting libraries
Chair: Jon Bosak, SunChair: Jon Bosak, Sun Current status: first meeting October 2001Current status: first meeting October 2001
Universal Business Language
Top down vs. bottom up?Top down vs. bottom up?
UBL: Bottom upUBL: Bottom up
Universal Business Language
Begin with xCBL 3.0 as the starting point and to Begin with xCBL 3.0 as the starting point and to develop the standard UBL library by mutually develop the standard UBL library by mutually agreed-upon changes to xCBL 3.0 based on agreed-upon changes to xCBL 3.0 based on industry experience with other XML business industry experience with other XML business libraries and with similar technologies such as libraries and with similar technologies such as Electronic Data Interchange. Electronic Data Interchange.
Develop UBL in light of Develop UBL in light of standards/specifications issued by standards/specifications issued by UN/CEFACT, ISO, IEC, ITU, W3C, IETF, OASIS, UN/CEFACT, ISO, IEC, ITU, W3C, IETF, OASIS, and such other standards bodies and and such other standards bodies and organizations as the UBL TC may deem organizations as the UBL TC may deem relevant. relevant.
RELAX NG
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
RELAX NG
Started: February 2001Started: February 2001 Charter: combine TREX and RELAX Charter: combine TREX and RELAX
proposals into a single light-weight XML proposals into a single light-weight XML schema specification schema specification
Chair: James Clark, individual memberChair: James Clark, individual member Current status: Committee Specification Current status: Committee Specification
approved; will submit to OASIS approved; will submit to OASIS membership soonmembership soon
Entity Resolution
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Entity Resolution
Started: November 2000Started: November 2000 Charter: further development of SGML Charter: further development of SGML
Open Catalog Specification (TR Open Catalog Specification (TR 9401:1997; “SOCat”) for XML compliance9401:1997; “SOCat”) for XML compliance
Chair: Lauren Wood, SoftQuadChair: Lauren Wood, SoftQuad Current status: Committee Specification Current status: Committee Specification
approved; will submit to OASIS approved; will submit to OASIS membership soonmembership soon
TM Published Subjects
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Topic Maps 101
Transcend Syntax !Transcend Syntax !Eliot Kimber, DataChannel/IsogenEliot Kimber, DataChannel/Isogen
Topic Maps 101
XYZ
A concept: XYZA concept: XYZ
Web
Topic Maps 101
First topic map concept : TopicFirst topic map concept : Topic Fundamental unit Meaningful description of an information object
<topic id=“XYZ”><topic id=“XYZ”>
<topname><topname>
<basename>XYZ</basename><basename>XYZ</basename>
</topname> </topname>
</topic></topic>
Topic Maps 101
A topic, in its most generic sense, can be A topic, in its most generic sense, can be any “thing” whatsoever – a person, an any “thing” whatsoever – a person, an
entity, a concept, really anything – entity, a concept, really anything – regardless of whether it exists or has any regardless of whether it exists or has any
other specific characteristics, about which other specific characteristics, about which anything whatsoever may be asserted by anything whatsoever may be asserted by
any means whatsoever.any means whatsoever.
Topic Maps 101
Extend the conceptExtend the concept
<topic id=“XYZ”><topic id=“XYZ”>
<topname><topname>
<basename>XYZ</basename><basename>XYZ</basename>
<dispname>XYZ Company</dispname><dispname>XYZ Company</dispname>
<sortname>XYZCompany</sortname><sortname>XYZCompany</sortname>
</topname> </topname>
</topic></topic>
Topic Maps 101
The topic occurs somewhere The topic occurs somewhere (on the Web)
XYZ
Web
Topic Maps 101
Second topic map concept : OccurrencesSecond topic map concept : Occurrences Path between a topic and an information object (in
this case a HTML page)
<occurs <occurs
href="http://xyz.com/serverdoc.htm">href="http://xyz.com/serverdoc.htm">
</occurs></occurs>
Topic Maps 101
Some information about an occurrenceSome information about an occurrence
Press ReleaseDocumentation
XYZ
Web
Topic Maps 101
Occurrences are typedOccurrences are typed
<occurs <occurs
type=“Documentation”type=“Documentation”
href="http://xyz.com/serverdoc.htm">href="http://xyz.com/serverdoc.htm">
</occurs></occurs>
<occurs <occurs
type=“Press Release”type=“Press Release”
href="http://xyz.com/news/ceo.htm">href="http://xyz.com/news/ceo.htm">
</occurs></occurs>
Topic Maps 101
Topic CharacteristicsTopic Characteristics Atomic Name Occurrence(s)
Must have at least one of themMust have at least one of them
Topic Maps 101
Web
There is more than one topicThere is more than one topicABC
NASDAQ
Press ReleaseDocumentation
XYZ
Topic Maps 101
And topics have typed relationshipsAnd topics have typed relationships
trading compete
Web
NASDAQ
Press ReleaseDocumentation
XYZABC
Topic Maps 101
Third topic map concept : AssociationsThird topic map concept : Associations Relationship between topics Association types are topics
<assoc type=“compete"><assoc type=“compete">
<assocrl>XYZ ABC</assocrl><assocrl>XYZ ABC</assocrl>
</assoc></assoc>
Topic Maps 101
Topics participating in an association Topics participating in an association have roles have roles role types are again … topics
<assoc type=“trading"><assoc type=“trading">
<assocrl type=“market">NASDAQ<assocrl type=“market">NASDAQ
</assocrl></assocrl>
<assocrl type=“stock">XYZ<assocrl type=“stock">XYZ
</assocrl></assocrl>
</assoc></assoc>
Topic Maps 101
Fourth topic map concept : Topic typeFourth topic map concept : Topic type Form a class-instance relationship
Topic types are again a topicTopic types are again a topic
ABC
CompanyMarket
NASDAQ XYZtrading compete
Topic Maps 101
Topic types can participate in Topic types can participate in associationsassociations
Which are again … (you get the picture)Which are again … (you get the picture)
listed
ABC
CompanyMarket
NASDAQ XYZtrading compete
Topic Maps 101
Fifth topic map concept : ScopeFifth topic map concept : Scope Compare to scope in programming languages
<topic id=“XYZ”><topic id=“XYZ”><topname scope=“English”><topname scope=“English”>
<basename>XYZ Inc.</basename><basename>XYZ Inc.</basename></topname></topname><topname scope=“German”><topname scope=“German”>
<basename>XYZ Ges.m.b.H.</basename><basename>XYZ Ges.m.b.H.</basename></topname> </topname> </topic></topic>
Topic Maps 101
There are more topic maps conceptsThere are more topic maps concepts Themes Facets Public Subjects Etc.
Exercise for the reader … Exercise for the reader …
Topic Maps 101
ISO 13250ISO 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 WebTopic Maps for the Web XTM, IdeAlliance initiative XTM 1.0 (March 2nd, 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-Widespread implementation of non-proprietary semantic navigation proprietary semantic navigation
networks is good for the Web. ISO networks is good for the Web. ISO 13250:2000 topic maps should be 13250:2000 topic maps should be
given full consideration by given full consideration by developers, content providers, developers, content providers,
builders of portals, and supporters builders of portals, and supporters of open standards and an open of open standards and an open
Web.”Web.” Liora Alschuler on XML.com
TM Published Subjects
Started: October 2001Started: October 2001 Charter: develop guidelines, Charter: develop guidelines,
recommendations, and applications to recommendations, and applications to promote adoption of Topic Maps promote adoption of Topic Maps Published Subjects (part of ISO 13250 and Published Subjects (part of ISO 13250 and XML Topic Maps (XTM) 1.0 Specification).XML Topic Maps (XTM) 1.0 Specification).
Chair: Bernard Vatant, MondecaChair: Bernard Vatant, Mondeca Current status: first meeting October 2001Current status: first meeting October 2001
WS Component Model
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
WS Component Model
Started: October 2001Started: October 2001 Charter: To create a Web Services Charter: To create a Web Services
standard for interactive application standard for interactive application access. WSCM will provide a coordinated access. WSCM will provide a coordinated set of XML vocabularies and Web services set of XML vocabularies and Web services interfaces that allow companies to deliver interfaces that allow companies to deliver Web applications to end users through a Web applications to end users through a variety of channels--directly to a browser, variety of channels--directly to a browser, indirectly through a portal or embedded indirectly through a portal or embedded into a third party Web application.into a third party Web application.
Chair: Charles Wiecha, IBMChair: Charles Wiecha, IBM
Customer Information Quality
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Customer Information Quality
Started: early 2000Started: early 2000 Charter: develop XML-based Charter: develop XML-based
specifications for customer profile and specifications for customer profile and addressing informationaddressing information
Chair: Ram Kumar, MastersoftChair: Ram Kumar, Mastersoft Current status: two Committee Current status: two Committee
Specifications approved; will submit to Specifications approved; will submit to OASIS membership soon; on-going work OASIS membership soon; on-going work with other specswith other specs
Provisioning Services
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
Provisioning Services
Started: November 2001Started: November 2001 Charter: combine the existing Active Charter: combine the existing Active
Digital Profile (ADPr), extensible Resource Digital Profile (ADPr), extensible Resource Provisioning Management (XRPM), and Provisioning Management (XRPM), and Information Technology Markup Information Technology Markup Language (ITML) specifications into a Language (ITML) specifications into a single specification describing single specification describing provisioning informationprovisioning information
Chair: Gavenraj Sodhi, Access360Chair: Gavenraj Sodhi, Access360 Current status: first meeting in NovemberCurrent status: first meeting in November
DocBook
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
DocBook
Started: 1992; moved to OASIS in 1998Started: 1992; moved to OASIS in 1998 Charter: develop the DocBook Charter: develop the DocBook
DTD/Schema for computer documentationDTD/Schema for computer documentation Chair: Norm Walsh, SunChair: Norm Walsh, Sun Current status: v4.1 accepted as an Current status: v4.1 accepted as an
OASIS Standard in January 2001; working OASIS Standard in January 2001; working towards v5.towards v5.
Conformance
Ma
na
ge
me
nt
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
Tra
din
g P
artn
er A
gre
em
en
t
XML Conformance
Started: 1999Started: 1999 Charter: develop test suites for testing Charter: develop test suites for testing
XML application conformance against the XML application conformance against the W3C XML RecommendationW3C XML Recommendation
Chair: Mary Brady, NISTChair: Mary Brady, NIST Current status: work completed summer Current status: work completed summer
2001; will be basis for future work in W3C 2001; will be basis for future work in W3C QA ActivityQA Activity
XSLT Conformance
Started: 1999Started: 1999 Charter: develop test suites for testing Charter: develop test suites for testing
XSLT application conformance against XSLT application conformance against the W3C XSLT Recommendationthe W3C XSLT Recommendation
Chair: Ken Holman, Crane SoftWrightsChair: Ken Holman, Crane SoftWrights
ebXML IIC
Started: August 2001Started: August 2001 IICIIC
Implementation, Interoperability, Conformance
Charter: develop guidelines and tools for Charter: develop guidelines and tools for interoperability, implementation, and interoperability, implementation, and conformance of the ebXML specs in order conformance of the ebXML specs in order to promote the adoption of the specs to promote the adoption of the specs
Chair: Philippe DeSmedt, Agentis Int’lChair: Philippe DeSmedt, Agentis Int’l Current status: work in progressCurrent status: work in progress
Conformance
Started: 1999Started: 1999 Charter: develop guidelines and Charter: develop guidelines and
resources for the creation of conformance resources for the creation of conformance test suitestest suites
Chair: Lynne Rosenthal, NISTChair: Lynne Rosenthal, NIST Current status: ongoing work in progress; Current status: ongoing work in progress;
a variety of white papers and test tools a variety of white papers and test tools releasedreleased
Agenda
State of the UnionState of the Union
About OASISAbout OASIS
E-business @ OASISE-business @ OASIS
Q&AQ&A
Announcement
OASIS public information meeting OASIS public information meeting on on Web ServicesWeb Services standards (the standards (the WSCM effortWSCM effort and related work at and related work at OASIS) OASIS)
OASIS will host the meeting at OASIS will host the meeting at 6:30 PM on Wednesday, 24 Oct, in 6:30 PM on Wednesday, 24 Oct, in Room 203Room 203 at the Santa Clara at the Santa Clara Convention Center. Convention Center.
Refreshments will be providedRefreshments will be provided and and everyone is welcome to attend.everyone is welcome to attend.
Q&A
Thanks !Thanks !