1 / 5

Ontological Implications of Service-Oriented Architecture

Ontological Implications of Service-Oriented Architecture. Michael Gruninger NIST / Institute for Systems Research University of Maryland. Tasks. Service discovery Find web services that achieve F, and where if B occurs then it occurs before A.

donoma
Download Presentation

Ontological Implications of Service-Oriented Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Ontological Implications of Service-Oriented Architecture Michael Gruninger NIST / Institute for Systems Research University of Maryland

  2. Tasks • Service discovery • Find web services that achieve F, and where if B occurs then it occurs before A. • e.g., my credit card is charged only after the book leaves the warehouse • Service composition

  3. Semantic Web Service Ontologies • Specify the semantics of the process model underlying services, together with a notion of messages and dataflow. • Axiomatize this semantics within some logical language (OWL, Common Logic) • Existing ontologies • OWL-S • SWSF (Semantc Web Services Framework) • WSMO (Web Service Modelling Ontology)

  4. SWSF • FLOWS-core • Service, AtomicProcess, composedOf, message, channel • Control Constraints • Split, Sequence, Unordered, Choice, IfThenElse, Iterate, RepeatUntil • Ordering Constraints • OrderedActivity • Occurrence Constraints • OccActivity • State Constraints • TriggeredActivity • Exception Constraints • Exception

  5. Ontologies for Semantic Web Services • The software applications within services will typically be using different ontologies, and any service-oriented architecture must support the semantic integration of these ontologies • Required Capabilities • Advertise/publish application ontologies • Automatically generate semantic mappings between ontologies used by different services. • Twenty Questions Semantic Mapping Tool and Process Information Exchange protocols

More Related