1. UDDI, ebXML, WSIL, XRI, WSDM (and the GRID) Matthew J. Dovey Technical Manager Oxford University e-Science Centre matthew.dovey@oucs.ox.ac.uk

2. UDDI Universal Description Discovery and Integration Provides data model for describing businesses and services Provides API for accessing registries UBR – Public Registry maintained by IBM, Microsoft, HP etc. But UDDI can be used for private/community registries But UDDI can be used for private/community registries

3. UDDI History Initial simple specification to encourage take-up and early implementations Fairly rapid turn-around of new versions: Version 1.0 late 2000 Version 1.0 late 2000 Version 2.0 mid 2001 Version 2.0 mid 2001 Version 3.0 mid 2002 Version 3.0 mid 2002 2000-2002: lead by UDDI Consortium 2002- moved to OASIS TC Present: Version 2.0 process of vote for OASIS Standard Version 2.0 process of vote for OASIS Standard Version 3.0 OASIS Committee specification Version 3.0 OASIS Committee specification

4. UDDI Data Structure V2

5. UDDI API Security get_AuthToken, discard_AuthToken get_AuthToken, discard_AuthTokenPublication save_ (create, update), delete_ save_ (create, update), delete_Inquiry find_, get_ find_, get_ template based queries template based queries No relevance/ranking No relevance/ranking Negotiation (QoS, price etc.) should happen outside of UDDI (but UDDI may contain endpoints to such negotiation services) Negotiation (QoS, price etc.) should happen outside of UDDI (but UDDI may contain endpoints to such negotiation services)

6. UDDI v3 Subscription Synchronous Synchronous Asynchronous (via callback webservice) Asynchronous (via callback webservice) Digital signature support for authenticating provenence Custody transfer Explicit node replication API V2 left to implementation V2 left to implementation Migration of data between registries UBR as registry of key generators UBR as registry of key generators UDDI Policy modeling All UDDI objects can be referenced by http gets Additional query modifiers, category groups, internationalization, etc.

7. UDDI Extensibility Prior to v3 getBusinessDetailExt getBusinessDetailExt V3 Appendix Extending data model via XML Schema substitutionGroups Extending data model via XML Schema substitutionGroups Extending API structures via XML Schema substitutionGroups Extending API structures via XML Schema substitutionGroups Use of XML Namespace to identify extension elements Use of XML Namespace to identify extension elements Policy for client/server behaviour Policy for client/server behaviour

8. Extensibility Example <uddi:add_publisherAssertions xmlns:egExt="http://tempuri.org/uddi_extension" xmlns:uddi="urn:uddi-org:api_v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> someAuthInfo some business key some other business key <uddi:keyedReference tModelKey="uddi:uddi.org:relationships" keyName="some peer to peer relationship" keyValue="peer-peer" /> http://www.example.com/contract/p2pcontract.pdf

9. UDDI v4 Compatibility changes for SAML, WS-A, WS-I, WS- Policy, BPEL, XRI, etc. Better external taxonomy support etc. More granular access control (by role, entity, action) Life of data (stale data) Trustworthiness (integration of trust and identity services) Federation (representing registries within registries) Different comparisons for category groups UDDI and GRID – best practice or new requirements? More best practice guides etc.

10. XRI – eXtensible Resource Identifier New OASIS Committee (began early this year) Chairs:Drummond Reed, OneName and Gabe Wachob, Visa International Aims: to define a URI scheme and a corresponding URN namespace that provide transport- and application-neutral identification schemes to support distributed directory services that enable the identification of resources (including people and organizations) to define a URI scheme and a corresponding URN namespace that provide transport- and application-neutral identification schemes to support distributed directory services that enable the identification of resources (including people and organizations) define basic mechanisms for resolving the identifiers in these schemes and for exchanging data associated with these identifiers. define basic mechanisms for resolving the identifiers in these schemes and for exchanging data associated with these identifiers. To enable the creation of Web-like collections of resources (including, but not limited to, data, systems, services, organizations, and people) that extend the WWW's current generalized addressing and linking capabilities To enable the creation of Web-like collections of resources (including, but not limited to, data, systems, services, organizations, and people) that extend the WWW's current generalized addressing and linking capabilities Define an XML schema to associate metadata with resources and a service to manipulate this metadata and data associated with the resources Define an XML schema to associate metadata with resources and a service to manipulate this metadata and data associated with the resources

11. XRI Strawman XRI-URI are Abstract - XRI-URIs are intended primarily to identify things that are not otherwise concretely identified on the network (such as HTTP endpoints, SMTP mailboxes, etc) Abstract - XRI-URIs are intended primarily to identify things that are not otherwise concretely identified on the network (such as HTTP endpoints, SMTP mailboxes, etc) Human-friendly - XRI-URIs are intended to supported names that are parseable, memorable, and semantically meaningful to humans. Human-friendly - XRI-URIs are intended to supported names that are parseable, memorable, and semantically meaningful to humans. Reassignable - XRI-URIs are intended to be "reassignable". This means that they can both resolve to different networked resources or representations as well as semantically refer to different resources themselves over time. Reassignable - XRI-URIs are intended to be "reassignable". This means that they can both resolve to different networked resources or representations as well as semantically refer to different resources themselves over time. Multiple paths of hierarchy - Each "segment" of an XRI-URI corresponds to a local key in a directory/namespace. No assumption is made about the segments used to "reach" a particular directory -- there can be multiple "paths" to get to a particular directory/namespace. Multiple paths of hierarchy - Each "segment" of an XRI-URI corresponds to a local key in a directory/namespace. No assumption is made about the segments used to "reach" a particular directory -- there can be multiple "paths" to get to a particular directory/namespace. XRI-URNs are: Abstract - XRI-URNs are intended primarily to identify things which are not otherwise concretely identified on the network (such as HTTP endpoints, SMTP mailboxes, etc) Abstract - XRI-URNs are intended primarily to identify things which are not otherwise concretely identified on the network (such as HTTP endpoints, SMTP mailboxes, etc) Efficiently Machine Resolvable - An important feature of XRI-URNs is that they are very efficiently resolvable. Efficient resolvability is favored over support for human readability. Efficiently Machine Resolvable - An important feature of XRI-URNs is that they are very efficiently resolvable. Efficient resolvability is favored over support for human readability. Permanent - XRI-URNs have the semantics of other URN schemes – an XRI-URN refers to the same logical resource from the time it is defined globally and forever. Permanent - XRI-URNs have the semantics of other URN schemes – an XRI-URN refers to the same logical resource from the time it is defined globally and forever.

12. XRI Examples XRI xri://’naming.authority’/local/part xri://’naming.authority’/local/part (abstract identifiers) (abstract identifiers) xri://naming.authority.com/local/part xri://naming.authority.com/local/part (leveraging DNS) (leveraging DNS) xri://(http://root.cross-reference.com).leaf/local/part xri://(http://root.cross-reference.com).leaf/local/part (cross referencing leveraging other URI scheme – abstract identifiers) (cross referencing leveraging other URI scheme – abstract identifiers) xri://=AlbertEinstein/theory/relativity xri://=AlbertEinstein/theory/relativity (shortcut mnemonics for convenience of humans) (shortcut mnemonics for convenience of humans)XRN urn:xri://.naming.authority/local/part urn:xri://.naming.authority/local/part (abstract identifiers) (abstract identifiers) urn:xri://.(urn:pin:999).leaf/local/part urn:xri://.(urn:pin:999).leaf/local/part (cross referencing leveraging other URN scheme – abstract identifiers) (cross referencing leveraging other URN scheme – abstract identifiers)

13. WSIL - Web Services Inspection Language IBM/Microsoft Note (2001) Dropped from OGSI/OGSA due to potential IPR issues XML document acting as intermediate pointer to service description Can reference UDDI services or WSDL (or other WSIL) Extensible to support other descriptions

14. WSIL Examples Referencing WSDL </description> Referencing UDDI 4FA28580-5C39-11D5-9FCF-B3200333F79 4FA28580-5C39-11D5-9FCF-B3200333F79 http://www.example.com/uddi?3C9CADD0-5C39-11D5-9FCF-BB3200333F79 </wsiluddi:discoveryURL></wsiluddi:serviceDescription></description>

15. Locating WSIL Add /inspection.wsil to URL Via HTML meta tags

16. WSIL Alternative? Use of html link element (proposed to UDDI list by Paul Denning) e.g. e.g. UDDI v3 all UDDI objects can be referenced by http gets. UDDI v3 all UDDI objects can be referenced by http gets.

17. Web Service Architecture – Discovery N.B. UDDI is registry designed for long life-cycle endpoints UDDI is registry designed for long life-cycle endpoints QoS, contract negotiation, management, etc. outside of UDDI (but endpoints can be stored in UDDI) QoS, contract negotiation, management, etc. outside of UDDI (but endpoints can be stored in UDDI)

18. ebXML XML for e-Business OASIS Standard (Currently at version 2) Defines: Data model for e-business objects (including services, policies etc.) Data model for e-business objects (including services, policies etc.) Messaging for e-business transactions Messaging for e-business transactions Registry for e-business objects Registry for e-business objects

19. ebXML Data Model Object Oriented Model (UML) Objects have methods and attributes Objects have methods and attributes

20. ebXML Registry API Life Cycle Management Query Management Filter (XML syntax) Filter (XML syntax) SQL SQL XQuery in future version? XQuery in future version? ebXML Registries must have policies Auditing

21. ebXML Filter Query XYZ select id from Organization where parent in (select id from Organization where name = ‘XYZ’);

22. ebXML and UDDI Fairly similar aims ebXML centred on e-business ebXML centred on e-business UDDI centred on WebServices UDDI centred on WebServices ebXML defined UML data model; UDDI defines XML Schema ebXML defined UML data model; UDDI defines XML Schema Cross OASIS TC Working Groups UDDI as basis for ebXML registries UDDI as basis for ebXML registries ebXML as basis for UDDI registries ebXML as basis for UDDI registries JAXR (Java Access to XML Registries) High level abstract interface to UDDI, ebXML, … High level abstract interface to UDDI, ebXML, …

23. WSDM New OASIS TC (started up last month) Based on previous floundered OASIS TC Defining management of distributed resources USING Web services Defining management OF Web services operations and WSDL. Collaborate with W3C, GGF, DMTF, OASIS Chairs: Heather Kreger (IBM, Chair of WSA MTF) & Winston Bumpus (Novell, DMTF President)

24. Web Service Architecture – MTF Defining the manageability characteristics of the architectural elements of the Web Services architecture, i.e.: Identification - data that uniquely identifies the element Identification - data that uniquely identifies the element Status - information about operational state of a element (up: busy/idle; down: stopped/saturated/crashed) Status - information about operational state of a element (up: busy/idle; down: stopped/saturated/crashed) Configuration - a collection of behavioural properties which may be changed (persistent over instances) Configuration - a collection of behavioural properties which may be changed (persistent over instances) Metrics - raw atomic, unambiguous information for managmement purposes e.g. response times Metrics - raw atomic, unambiguous information for managmement purposes e.g. response times Operations - methods that control or help manage the entity (instance specific) Operations - methods that control or help manage the entity (instance specific) Events - changes in the state of the entity e.g a lifecycle state change, or a state change. Events - changes in the state of the entity e.g a lifecycle state change, or a state change.

25. DTMF Models real world managed objects. Large existing model (not in web/grid format/granularity) Application Working Group Intends to model management of web services Intends to model management of web services Interoperability Working Group Defining a CIM/SOAP protocol in WSDL: CIM/Ops as WSDL operations and xmlCIM as the body of SOAP messages over HTTP Defining a CIM/SOAP protocol in WSDL: CIM/Ops as WSDL operations and xmlCIM as the body of SOAP messages over HTTP

26. GRID OGSA et al. But you know all about that!

27. Web Services stack

28. Links OASIS (ebXML, UDDI, XRI, WSDM) http://www.oasis-open.org/ http://www.oasis-open.org/ http://www.oasis-open.org/ Web Service Architecture http://www.w3.org/2002/ws/arch/ http://www.w3.org/2002/ws/arch/ http://www.w3.org/2002/ws/arch/ WSIL http://www-106.ibm.com/developerworks/webservices/library/ws- wsilspec.html http://www-106.ibm.com/developerworks/webservices/library/ws- wsilspec.html http://www-106.ibm.com/developerworks/webservices/library/ws- wsilspec.html http://www-106.ibm.com/developerworks/webservices/library/ws- wsilspec.html