1. u se of UDDI to publish data of s emantic w eb Anton Naumenko, Sergiy Nikitin, Vagan Terziyan, Jari Veijalainen* Jyväskylä, Finland 27 August 2005, Industrial Ontologies Group, Department of Mathematical Information Technology, University of Jyväskylä, FINLAND * Information Technology Research Institute, Faculty of Information Technology, University of Jyvaskyla, FINLAND

2. ASG project asg-platform.org / info@asg-platform.org ”Combine the Services” Interlock the performance-oriented grid community and the application-services-oriented W3C-world using the advantages of - Open Grid Service Interface - Web Service Description Language and -Web Service Resource Framework to develop an Open Platform for adaptive services discovery, creation, composition, and enactment with business-oriented Quality of Service functionality = Adaptive Services Grid

3. ScenariosScenarios Three application areas:  Telecommunication  Car Problem Solving Service  Enterprise IT Common in these scenarios is the need to create advanced services, based on service components from different actors.

4. Milestone M12 Deliverables are research reports  requirements analysis results  evaluation of existing efforts  initial conceptual results

5. Milestone M18 The most important conceptual results have been prototypically implemented in tools integrated to build the core ASG platform. Deliverables of this milestone  research reports  prototypical tool implementations  scenarios

6. Work Packages: Project Management (C-0) ASG Interface (C-1) Service Discovery & Composition (C-2) Service Creation (C-3) Adaptive Process Management (C-4) Services Grid Infrastructure (C-5) ASG Development Methodology (C-6) Usability and Demonstration (C-7) Dissemination (C-D) “… to develop a proof-of-concept prototype of an open development platform for adaptive services discovery, creation, composition, and enactment.” Big picture

7. Place of the Registry

8. Role of the Registry in composed service invocation ASG project

9. Smart Resource 2005 Scenario “Expert” “Service” Labelled data Diagnostic model Querying diagnostic results Labelled data Watching and querying diagnostic data Labelled data History data “Device” Querying data for learning Learning sample and Querying diagnostic results “Knowledge Transfer from Expert to Service”

10. GUN Concept: All GUN resources “understand” each other…

11. ObjectiveObjective Use of UDDI registry to publish Semantic Web data  for semantic-based description,  discovery  integration of web resources in a context of needs of two research projects: “Adaptive Services Grid” (ASG) and “SmartResource”

12. ApproachApproach Mapping of RDFS upper concepts to UDDI data model using tModel structure, which makes possible to store semantically annotated resources internally in UDDI UDDI as an enabling specification for creation of a semantic registry for web resources in general

13. Semantic Annotation A description of entities using Semantic Web standards A prerequisite to allow semantic discovering and integration. In the context of UDDI, an entity of the semantic annotation would be a Web Service and businesses, business services and technical information that is a target of a binding. Consider each resource entity (not just a web service) as a subject of the semantic annotation, registering, discovering, composition, enactment, integration, etc.

14. Related work 1 Solution extends service descriptions using RDF and changes UDDI APIs for support of semantic search. L. Moreau, S. Miles, J. Papay, K. Decker, T. Payne, “Publishing Semantic Descriptions of Services”, Semantic Grid Workshop at GGF9, 2005

15. Related work 2 UDDI+ server introduces additional elements like  a matchmaker,  an ontology repository,  a proxy API to invoke UDDI APIs. Mapping of DAML-S to UDDI publish message Unchanged UDDI Publish and Inquiry interface S. Pokraev, J. Koolwaaij, M. Wibbels, “Extending UDDI with Context-Aware Features Based on Semantic Service Descriptions”, Proceedings of the International Conference on Web Services, ICWS '03, June 23 - 26, 2003, Las Vegas, Nevada, USA. CSREA Press 2003, ISBN 1-892512-49-1, pp. 184-190

16. Related work 3 A semantic search based on an externally created and operated matchmaker Semantic data are stored outside of UDDI  a link from tModel of a Web Service in UDDI to its Web Service Semantic Profile (WSSP). WSSP serves as the semantic annotation of a service and extends WSDL description of the service using RDF, RDFS, DAML+OIL or OWL, RDF-RuleML M. Paolucci, T. Kawamura, T.R. Payne, K. Sycara, “Importing the Semantic Web in UDDI”, Proceedings of E-Services Semantic Web Workshop (ESSW 2002), 2002

17. Related work 4 A mapping of an OWL-S profile to the UDDI data model for a matchmaker architecture based on the Paolucci’s results (previous slide) The difference from our approach:  OWL-S concepts to UDDI concepts  RDF triplet model to a data structure of tModel N. Srinivasan, M. Paolucci, K. Sycara, “An Efficient Algorithm for OWL-S Based Semantic Search in UDDI” Semantic Web Services and Web Process Composition, First International Workshop, SWSWPC 2004: 96-110

18. UDDIUDDI “…is the specification of services to provide publishing and discovery of “business, organizations and other Web Service providers”, their Web Services and technical interfaces to enact those services.“ (UDDI Specification)

19. tModel Structure Name Use tModelKeyrequired keyNameoptional keyValuerequired Name Use tModelKeyrequired Characteristics: provides a reference system based on abstraction provides the ability to describe compliance with specifications, concepts, or even shared design is a keyed entity in UDDI

20. Mapping SPO to UDDI SubjectObject Predicate Name Use tModelKeyrequired keyNameoptional keyValuerequired Name Use tModelKeyrequired

21. Mapping SPO to UDDI Name Use tModelKeyrequired keyNameoptional keyValuerequired Name Use tModelKeyrequired SubjectObject Predicate

22. Mapping SPO to UDDI(2) Name Use tModelKeyrequired keyNameoptional keyValuerequired Name Use tModelKeyrequired SubjectObject Predicate

23. Mapping SPO to UDDI(3) Name Use tModelKeyrequired keyNameoptional keyValuerequired Name Use tModelKeyrequired SubjectObject Predicate

24. XML view

25. Publishing of RDF-Schema concepts

26. New concepts

27. ConclusionsConclusions UDDI has enough support for the registration of semantically annotated resources SmartResource project can use UDDI to implement Notice Boards for registering semantically annotated resources Publishing ASG service and domain ontology to UDDI can be performed based on publishing of WSMO to UDDI Have to elaborate API to support semantic discovery of registered resources Navigable structure

28. Future Work Further research is needed to elaborate semantic discovery algorithms and UDDI APIs based on proposed way of storing semantics in UDDI

29. Thank you! Questions please