Semantic Web Fred: Goal and Service Description Language Michael Stollberg - 05 June 2004 -

Slides:



Advertisements
Similar presentations
Dr. Leo Obrst MITRE Information Semantics Information Discovery & Understanding Command & Control Center February 6, 2014February 6, 2014February 6, 2014.
Advertisements

Web Service Modelling Ontology (WSMO)
Outbrief of SWSI Architecture Committee F2F Sat, April 12, 2003 Miami, FL Mark H. Burstein BBN Technologies.
1 Intention of slide set Inform WSMOLX of what is planned for Choreography & Orhestration in DIP CONTENTS Terminology Clarification / what will be described.
OASIS Reference Model for Service Oriented Architecture 1.0
Reasoning Tasks and Mediation on Choreography and Orchestration in WSMO Michael Stollberg WIW 2005, June 6-7, Innsbruck, Austria.
Integrating Agents, Ontologies, and Semantic Web Services for Collaboration on the Semantic Web Michael Stollberg and Thomas Strang DERI – Digital Enterprise.
Introduction To System Analysis and Design
1 The Fourth Summer School on Ontological Engineering and the Semantic Web (SSSW'06) Semantic Web Services Hands-On Session with IRS-III and WSMO Studio.
Software Testing and Quality Assurance
1 Discovery and Mediation using Diane Service Descriptions Ulrich Küster and Birgitta König-Ries (also contains work by Michael Klein) University Jena.
Semantic Web Fred Framework and Demonstration or ‘my PhD-Thesis in 30 min’ Michael Stollberg, 14-Dec-2004.
The WSMO / L / X Approach Michael Stollberg DERI – Digital Enterprise Research Institute Alternative Frameworks for Semantics in Web Services: Possibilities.
The RDF meta model: a closer look Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations.
Kmi.open.ac.uk Semantic Execution Environments Service Engineering and Execution Barry Norton and Mick Kerrigan.
1 The Third Summer School on Ontological Engineering and the Semantic Web (SSSW'05) Semantic Web Services Hands-On Session with IRS-III John Domingue and.
SE 555 – Software Requirements & Specifications Introduction
1 Service Discovery using Diane Service Descriptions Ulrich Küster and Birgitta König-Ries University Jena Germany
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
© Copyright Mick Kerrigan and Barry Norton Semantic Execution Environments Service Engineering.
1 Adapting BPEL4WS for the Semantic Web The Bottom-Up Approach to Web Service Interoperation Daniel J. Mandell and Sheila McIlraith Presented by Axel Polleres.
Introduction To System Analysis and design
Špindlerův Mlýn, Czech Republic, SOFSEM Semantically-aided Data-aware Service Workflow Composition Ondrej Habala, Marek Paralič,
Demonstrating WSMX: Least Cost Supply Management.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
MFI-5: Metamodel for process model registration Chong Wang, Keqing He and Baba Piprani.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Towards Translating between XML and WSML based on mappings between.
Agent Model for Interaction with Semantic Web Services Ivo Mihailovic.
3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 12.
25./ Final DIP Review, Innsbruck, Austria1 D11.22 DIP Project Presentation V5 Oct 2006 Presented at Final Review Innsbruck, Oct, 2006.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Semantic-enabled Voice and Data Integration: Telecommunication.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Tomas Vitvar SemanticGov 4 rd Planetary.
1 MFI-5: Metamodel for Process models registration HE Keqing, WANG Chong State Key Lab. Of Software Engineering, Wuhan University
Introduction To System Analysis and Design
Semantic Web Fred: Project Objectives & SWF Framework Michael Stollberg Reinhold Herzog Peter Zugmann - 07 April
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Semantic Web Services and User Goal definition problems Andrej.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Tomas Vitvar, Sanaullah Nazir SemanticGov.
10/18/20151 Business Process Management and Semantic Technologies B. Ramamurthy.
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
Using WSMX to Bind Requester & Provider at Runtime when Executing Semantic Web Services Matthew Moran, Michal Zaremba, Adrian Mocan, Christoph Bussler.
The Dynamic Discovery of Web Services Using WSMX Presented by Robert Zaremba.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Semantic Web Services enabled B2B Integration Kotinurmi,Vitvar,
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
WSMO Discovery Realization in Semantic Web Fred Michael Stollberg - 03 November
Christoph Bussler, Laurentiu Vasiliu Digital Enterprise Research Institute (DERI) National University of Ireland, Galway, Ireland SDK meeting.
MFI-5: Metamodel for process model registration WANG Chong, HE Keqing, HE Yangfan, WANG Jian State Key Lab of Software Engineering (SKLSE) Wuhan University,
Introduction to Semantic Web Service Architecture ► The vision of the Semantic Web ► Ontologies as the basic building block ► Semantic Web Service Architecture.
The RDF meta model Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations of XML compared.
16/11/ Semantic Web Services Language Requirements Presenter: Emilia Cimpian
WSDL – Web Service Definition Language  WSDL is used to describe, locate and define Web services.  A web service is described by: message format simple.
A Mediated Approach towards Web Service Choreography Michael Stollberg, Dumitru Roman, Juan Miguel Gomez DERI – Digital Enterprise Research Institute
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Dynamic RosettaNet Integration on Semantic Web Services Tomas.
 Copyright 2006 Digital Enterprise Research Institute. All rights reserved. Dynamic B2B Integration on the Semantic Web Services: SWS Challenge.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Tomas Vitvar SemanticGov 4 rd Planetary.
Discussion about MFI-7: Metamodel for Service Registration Wang Jian, He Keqing, He Yangfan, Wang Chong SKLSE, Wuhan University, China
Universität Innsbruck Leopold Franzens  Copyright 2007 DERI Innsbruck Second TTF Technical Fair 12 December 2007 Mediation Component Second.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. SOA-RM Overview and relation with SEE Adrian Mocan
Semantic Web Fred Automated Goal Resolution on the Semantic Web Michael Stollberg 38th Hawaiian International Conference on System Science Hawaii Big Island,
Of 24 lecture 11: ontology – mediation, merging & aligning.
A Semi-Automated Digital Preservation System based on Semantic Web Services Jane Hunter Sharmin Choudhury DSTC PTY LTD, Brisbane, Australia Slides by Ananta.
WWW: WSMO, WSML, and WSMX in a Nutshell Dumitru Roman 1, Jos de Bruijn 1, Adrian Mocan 1, Holger Lausen 1,2, John Domingue 3, Christoph Bussler 2, and.
Tomas Vitvar, Maciej Zaremba, Mathew Moran
Web Service Modeling Ontology (WSMO)
Web Ontology Language for Service (OWL-S)
Semantic Web Towards a Web of Knowledge - Projects
Business Process Management and Semantic Technologies
MFI-5: Metamodel for process model registration
Presentation transcript:

Semantic Web Fred: Goal and Service Description Language Michael Stollberg - 05 June

Semantic Web Fred 11-Oct-15 2 Content 1.Recall: SWF Aims & Architecture 2.Description Language Goals SWF Services 3.Usage in SWF Mechanisms 4.Summary

Semantic Web Fred 11-Oct-15 3 – Recall: SWF Aims & Architecture – Cooperation Model Aim: Map real world Cooperation Model into Software => Symmetry of cooperating parties : –Why: Cooperative Goals can only be achieved by cooperation of several parties (e.g. the CEO needs salesman for increasing company’s success, salesman needs CEO for increase sale rate) Every party is requester and provider at the same time –Implication for System Architecture: all potential partners need to have Goals and Services

Semantic Web Fred 11-Oct-15 4 – Recall: SWF Aims & Architecture – SWF Architecture Fred A Service Execution Goal Repository Service Repository -Description Registry -Implementation Rep. (Plans, Processes, WS) Goal Instance Service GG Discovery GS Discovery WW Discovery Mediator Repository Ontology Repository Fred B Agent Repository Service Goal Instance Cooperation Environment Service Goal Solver

Semantic Web Fred 11-Oct-15 5 – Recall: SWF Aims & Architecture – WSMO - SWF Repository Alignment all SWF Goals / Web Services / Mediators, etc also in WSMO Repository & vice versa -Repository structure identical, see WSMO D10 -transformation between descriptions needed => create a nice repository of use case data WSMO Registry concurrent publishing Ontologies Goals Web Services Mediators Ontologies Goals SWF Services Mediators transform & publish Smart Objects SWF Goal Schemas only all SWF Services esp. re-use of WSMO Mediators

Semantic Web Fred 11-Oct-15 6 – SWF Goal and Service Description Language – Aims & Objectives We only need semantic descriptions for Goals & SWF Services –Ontologies are handled by SMO technology, also external ontologies (e.g. from WSMO) are transformed into SMOs => internal handling –Mediators: “connection facility” is transformed in SWF technology “mediation facility” is a normal Web Service / SWF Service –Agents (Freds) do not need semantic descriptions Aim: SWF as a WSMO implementation –General structure very aligned to WSMO => SWF Goal & Service Description Language is a specialization of WSMO Language: –For modeling we use WSML (as in WSMO Use Case deliverable) –Will be transformed in to technology-depend format

Semantic Web Fred 11-Oct-15 7 – SWF Goal and Service Description Language – Goals Understanding of Goals: –express a desire that user delegates to a Fred for automated resolution –currently modeled as the “counterpart” for SWF Service Capability expresses a desire is the entity that actively interacts with a SWF Service => holds additional infos Cooperative Goals –a Goal that can be achieved in cooperation only (e.g. “Purchase”) –specifies compatible “normal” Goals that Freds may have in a cooperation (e.g. “Buyer” and “Seller” Goals as compatible Goals of “Purchase”) –change to previous version: Goal in SWF = specialization of WSMO Goal Cooperative Goal = Goals only resolvable in a cooperation Goal Schema and Goal Instance –Goal Schema = ontological structure of Goals resolvable by the system –Goal Instance = concrete expression of desire “thrown” during runtime Under discussion: really the right way?

Semantic Web Fred 11-Oct-15 8 – SWF Goal and Service Description Language – Goal Description Goal Schema Description Elements nonFunctionalProperties: based on WSMO Core Properties. mandatory: title, creator, description, date, time, identifier, rights, version. Important is the title and description (used by users to identify and select Goal Schemas). usedMediators: OO Mediators (terminology) requirementSpec: the ontological schema that is handed over to a service as input to that service during invocation. Is “instantiated” by a corresponding Goal Instance. resultSpec: the ontological schema that is expected to solve the Goal. Is “instantiated” by a corresponding Goal Instance. The resolution of a Goal might require usage of several services / several cooperations. postCondition: conditions on the resultSpec, i.e. the constraints that define desired state of the information space. If this holds after Goal Resolution, the Goal is solved. The postcondition describes conditions of resultSpecs in relation to requirementSpecs. effects: arbitrary states of the world that are expected to hold after the Goal Resolution. Not tested yet

Semantic Web Fred 11-Oct-15 9 – SWF Goal and Service Description Language – Goal Description Goal Instance Description Elements instanceOf: link to the Goal Schema that the Goal Instance is derive from nonFunctionalProperties: based on WSMO Core Properties. mandatory: creator, date, time, identifier, rights, derived from Goal Schema: title, description, version. Additionally: –timeConstraints: timeframe in which the Goal shall be resolved –resourceConstraints: constraints on possible partners or services to be used –goalResolutionContraints: “user preferences” on the whole Goal Resolution process owner: the Fred that has created this Goal Instance requirements: instantiated ontological structure that is handed over to a service as input during service invocation. results: instantiated ontological structure that is expected as a result of service(s) usage to solve the Goal. status: information on the Goal Resolution process, handled by the Goal Solver; possible values: open, solved, not solved, processing, cancelled Not tested yet

Semantic Web Fred 11-Oct – SWF Goal and Service Description Language – Goal Description Cooperative Goal Description Elements cooperativeGoal:[ nonFunctionalProperties => nonFunctionalProperties compatibleGoals[ compatibleGoal =>> goalSchema compatibleGoalConstraints =>> axiomDefinition ] cooperativeGoalConstraints =>> axiomDefinition ] compatibleGoals: the set of Goal Schemas which in interaction support the solution of the Cooperative Goal. compatibleGoalConstraints: constraints defined for the Goal Schema, e.g.: cardinality: 0-n means that there can interact 0, 1, or up to n partners with this Goal. Defining the Cooperative Goal “Playing Football” might have the sub-Goal “Providing a Team” with cardinality 2, while “Providing a team” might have “Being a team member” with cardinality 11. cooperativeGoalConstraints: constraints defined across Goal Schemas. this is a Redcution => maybe a GG Mediator here

Semantic Web Fred 11-Oct – SWF Goal and Service Description Language – Services SWF Service Model – 3 Services types: 1. Plan = internal Java program (need: JVM) 2. Process = multi-step service, each activity can be resolved arbitrarily (needs: Process Engine) 3. external Web Services (execution via WSDLExecutorPlan) => Aim: 1 common Description Language for all SWF Services – for discovery we only need the descriptive information – the Service Type is only of interest for Execution (different grounding) SWF Service PlanProcessExternal Web Service

Semantic Web Fred 11-Oct – SWF Goal and Service Description Language – Service Description SWF Service Description Elements nonFunctionalProperties: based on WSMO Core Properties. mandatory: title, creator, description, date, time, identifier, rights, version. WSMO Web Service specific nFPs are needed for discovery heuristics, but not incorporated in current version usedMediators: OO Mediators (terminology) capability: functional description, i.e. WHAT the service does interface: behavioral description, i.e. HOW to USE the service grounding: access (point to physical location) and Service Type Not tested yet

Semantic Web Fred 11-Oct – SWF Goal and Service Description Language – Service Description SWF Capability Description Elements precondition: input required by the service & conditions over this assumption: arbitrary constraint of the state of the world that has to hold before the service can be executed postcondition: (computational) result of the service & conditions over this, in relation to the input effect: arbitrary constraint of the state of the world that results as a change after execution of the service => currently: 100 % WSMO compliant different proposal under discussion: 1)Input = ontological structure required 2)precondition = conditions over 1), i.e. integrity constraint 3)assumption = arbitrary constraints on state of the world 4)Result = ontological structure returned 5)postcondition = conditions over 4), i.e. integrity constraint 6)effects= arbitrary constraints on state of the world

Semantic Web Fred 11-Oct – SWF Goal and Service Description Language – Service Description SWF Service Interface Description Elements swfServiceInterface:[ invocationMessage => invocationMessage outputMessage => outputMessage choreography => choreographyDescription ] invocation: Goal send input - must be compliant to Goal requirements - must satisfy the Capability precondition outputMessage: always the last message of a service behavior is a outgoing message (content: result or failure) choreography: WSMO Choreography description (we only need the individual behavior description here – the “global interaction model” is located in WW Discovery) Orchestration: handled by FRED Processes, not needed / regarded in SWF (orchestration & service composition is objective in FRESCO) not specified in WSMO yet Choreography Message Activity Start/E nd external visible behaviour Output Message Invocation Message

Semantic Web Fred 11-Oct – Outlook: SWF Mechanisms – Automated Cooperation Workflow

Semantic Web Fred 11-Oct – Outlook: SWF Architecture: Mechanisms – GG Discovery Detection of potential cooperation partners Fred A Fred Y Fred X Goal Instance Goal Schema 1. Initialization 2. Matching & Mediation 3. Potential Coop. Partners GG Mediator Cooperative Goal is compatible Goal

Semantic Web Fred 11-Oct – Outlook: SWF Discovery Mechanisms – GG Discovery Workflow What to match –Object of Interest (to be the same) –Cooperation Role (to be compatible) Cooperative Goal specifies this compatibility completely –matching of Object of Interests by Cooperative Goal designer –Cooperation Roles Compatibility: specifying compatible Goal Schemas Owners of corresponding Goal Instances will have compatible Roles Functional aspects: –initiates Cooperation –can be performed at design time –different engines that initiate GG Discovery permanent event-driven during runtime „hardcoded“ in a way

Semantic Web Fred 11-Oct – Outlook: SWF Discovery Mechanisms – GS Discovery Detection of suitable SWF Services for each partner (equivalent to Service Discovery in WSMO)

Semantic Web Fred 11-Oct – Outlook: SWF Discovery Mechanisms – GS Discovery Workflow What to match: SWF Service Capability postcondition & effect have to “match” Goal Instance result and well as the corresponding Goal Schema postcondition and effects Algorithm = WSMO Discovery Functional aspects: – pre-GS-Discovery at design time possible (indexing) – result: a set of possible usable SWF Service for each partner Remark: there has to be at least 1 SWF Service that matches the Goals of each partner (Service Composition tackled in FRESCO, currently manual as processes)

Semantic Web Fred 11-Oct – Outlook: SWF Discovery Mechanisms – WW Discovery Determine compatibility of detected Services for the Cooperation Partners (pre-requisite for automated Service Execution)

Semantic Web Fred 11-Oct – Outlook: SWF Discovery Mechanisms – WW Discovery Workflow What to match: determine / establish behavioral compatibility, i.e. determine the global service interaction model Algorithm – ideas: –individual behaviors must be inverse (simplest case) –determine compatibility of MEPs –also: messaging technology has to be the same Functional aspects: determines the Cooperation Contract specifies all information on Freds, Goals, Services, Service Interaction is the “Service Execution Agenda”

Semantic Web Fred 11-Oct – Summary – Open Points Conceptual Decisions on Goal & Service Description Language –Goal “requirements” –Service Capability & Interface Description => Test & Refinement in Use Case modelling Basis Technology for SWF Mechanisms: –reasoner –vs- conventional technologies: reasoner not stable & performant conventional technologies need transformations everywhere, loss of flexibility (still preferred at this point in time) –important decision... Matchmaker Specification – how shall they really work? Usage of WSMO Mediators – translation of connection facility

Semantic Web Fred 11-Oct – Summary – Future Work detailed system design Use Case Implementation supported environments: 1)FRED environment (Meeting rooms, FIPA, Cooperation Contract) 2)Web environment (virtual meeting rooms, SOAP, virtual cooperation contract) but: the core will be the same and: Dissemination …