UDDI, ebxml,, WSIL, XRI, WSDM (and the GRID) Matthew J. Dovey Technical Manager Oxford University e-science e

Transcription

1 UDDI, ebxml,, WSIL, XRI, WSDM (and the GRID) Matthew J. Dovey Technical Manager Oxford University e-science e 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

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 2.0 mid 2001 Version 3.0 mid : 2002: lead by UDDI Consortium moved to OASIS TC Present: Version 2.0 process of vote for OASIS Standard Version 3.0 OASIS Committee specification

4 UDDI Data Structure V2

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

6 UDDI v3 Subscription Synchronous Asynchronous (via callback webservice) Digital signature support for authenticating provenence Custody transfer Explicit node replication API V2 left to implementation Migration of data between registries 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 V3 Appendix Extending data model via XML Schema substitutiongroups Extending API structures via XML Schema substitutiongroups Use of XML Namespace to identify extension elements Policy for client/server behaviour

8 Extensibility Example <uddi:add_publisherassertions xmlns:egext=" xmlns:uddi="urn:uddi-org:api_v3" xmlns:xsi=" <uddi:authinfo>someauthinfo</uddi:authinfo> <egext:publisherassertionext> <uddi:fromkey>some business key</uddi:fromkey> <uddi:tokey>some other business key</uddi:tokey> <uddi:keyedreference tmodelkey="uddi:uddi.org:relationships" keyname="some peer to peer relationship" keyvalue="peer-peer" /> <uddi:discoveryurls> <uddi:discoveryurl usetype="contract"> </uddi:discoveryurl> </uddi:discoveryurls> </egext:publisherassertionext> </uddi:add_publisherassertions>

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 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. To enable the creation of Web-like collections of resources (including, but not limited to, data, systems, services, organizations, ations, 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

11 XRI Strawman XRI-URI are Abstract - XRI-URIs are intended primarily to identify things that are not otherwise e 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. Reassignable - XRI-URIs are intended to be "reassignable" reassignable". This means that they can both resolve to different networked resources or representations as well w 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. 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) 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 a forever.

12 XRI Examples XRI xri:// naming.authority naming.authority /local/part (abstract identifiers) xri://naming.authority.com/local/part (leveraging DNS) xri://( reference.com).leaf/local/part (cross referencing leveraging other URI scheme abstract identifiers) xri://= ://=AlbertEinstein/theory/relativity (shortcut mnemonics for convenience of humans) XRN urn:xri://.naming.authority/local/part (abstract identifiers) urn:xri://.(urn:pin:999).leaf/local/part (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 referencednamespace=" =" /" location=" example.com/stockquote/main.wsdl"> </description> Referencing UDDI <description referencednamespace=" ="urn:uddi-org:api"> <wsiluddi:servicedescription location=" <wsiluddi:servicekey>4fa c39-11d5-9fcf-b f79</ B F79</wsiluddi:serviceKey> <wsiluddi:discoveryurl usetype=" ="businessentity"> 5C39-11D5-9FCF-BB F79 </wsiluddi:discoveryurl wsiluddi:discoveryurl> </wsiluddi:servicedescription wsiluddi:servicedescription> </description>

15 Locating WSIL Add /inspection.wsil/ to URL Via HTML meta tags <HTML> <HEAD> <META name="serviceinspection serviceinspection" content="localservices.wsil localservices.wsil"> <META name="serviceinspection serviceinspection" content=" <META name="serviceinspection serviceinspection" content="ftp:// sil"> </HEAD> <BODY>

16 WSIL Alternative? Use of html link element (proposed to UDDI list by Paul Denning) e.g. <link rel="alternate" type="application/uddi application/uddi-inq+xml" title="biznamehere biznamehere" href="url/to/soap/uddiv2/inquiryapi" /> 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 QoS,, contract negotiation, management, etc. outside of UDDI (but endpoints can be stored in UDDI)

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

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

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

21 ebxml Filter Query <AdhocQueryRequest> <ResponseOption returntype = "LeafClass"/> <FilterQuery> <OrganizationQuery> <OrganizationParentBranch> <NameBranch> <LocalizedStringFilter> <Clause> <SimpleClause leftargument = "value"> <StringClause stringpredicate = "Equal">XYZ</StringClause> </SimpleClause> </Clause> </LocalizedStringFilter> </NameBranch> </OrganizationParentBranch> </OrganizationQuery> </FilterQuery> </AdhocQueryRequest> 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-businesse UDDI centred on WebServices ebxml defined UML data model; UDDI defines XML Schema Cross OASIS TC Working Groups UDDI as basis for ebxml registries ebxml as basis for UDDI registries JAXR (Java Access to XML Registries) 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 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) Metrics - raw atomic, unambiguous information for managmement purposes e.g. response times 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.

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 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

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

27 Web Services stack Management requirements for a Manageable Web Services Archicture W3C WS Arch WG, Management TF Security/Trust/Privacy Management Quality of Service Mangeability of Web Services OASIS WSDM Web service based access to management data - OASIS WSDM, GGF CMM Manageability porttypes - OASIS WSDM, GGF CMM, DMTF

28 Links OASIS (ebxml( ebxml,, UDDI, XRI, WSDM) open.org/ Web Service Architecture WSIL ibm.com/developerworks/webservices/library/ws- wsilspec.html