Semantic Web Services Language

Semantic Web Services Language (SWSL)Paradigm| Multi-paradigm: generic, object-oriented (class-based), imperative, reflective

|

First appeared| 1994; 32 years ago (1994)
Filename extensions| .swsl
Website| www.w3.org/Submission/SWSF-SWSL/
Influenced
Semantic Web Services, Semantic Web, Semantic computing
Abraham Bernstein(left), One of the authors of Semantic Web Services Language (SWSL) Michael Gruninger, One of the authors of Semantic Web Services Language (SWSL)

The Semantic Web Services Language (SWSL) is a general-purpose logical language for specifying Semantic Web Services Ontologies (SWSOs), as well as individual Web services.[1][2] The Semantic Web Services Language (SWSL) describes the syntax elements of SWSL and its semantic and semantic foundations.[3] It can be used with the underlying language and network structure of Semantic Web Services. Syntactically, first-order logic (including all connections used in first-order logic) is a subset of the Semantic Web Services Language (SWSL).[1][3]

The Semantic Web Services Language consists of two different basic languages: Declarative Logic Programs (SWSL Rule) and First Order Classical Logic (SWSL-FOL).[4] Semantically, the two sub-language of SWSL are incompatible, but the two sub-language can cooperate.[1]

SWSL-Rules is a non-monotonic semantic and rule-based language. SWSL-FOL is a complete first word logic language.

SWSL-FOL and SWSL-Rules follow the semantics of the Semantic Web Services Language (SWSL).

## Contents

* 1 Background
* 2 Uses of SWSL
* 2.1 The cases of Semantic Web Services Language (SWSL)
* 3 SWSL-FOL
* 3.1 Definition
* 3.2 The Syntax And Semantic Extension Of SWSL-FOL
* 3.3 Uses
* 4 SWSL-Rules
* 4.1 Definition
* 4.2 The Syntax And Semantic Extension Of SWSL-Rules
* 4.3 Uses
* 5 Language
* 5.1 The Layered Structure
* 5.2 Main layers
* 5.2.1 The Monotonic Lloyd-Topor Layer:[1]
* 5.2.2 The NAF Layer
* 5.2.3 The Nonmonotonic Lloyd-Topor Layer
* 5.2.4 The Courteous Rules Layer
* 5.2.5 The HiLog Layer
* 5.2.6 The Equality Layer
* 5.2.7 The Frames Layer
* 6 References
* 7 External links

## Background

Twelve authors from the National Institute of Standards and Technology (NIST), National Research Council of Canada, SRI International, Stanford University, Toshiba and Southampton University submitted four documents:

* Semantic Web Services Language (SWSL)
* Semantic Web Services Framework (SWSF) Overview
* Semantic Web Services Ontology (SWSO)
* SWSF Application Scenarios[5]

The four documents defined the Semantic Web Services Framework (SWSF). The Semantic Web Services Framework (SWSF) includes Ontology Semantic Web Services Ontology (SWSO) and Descriptive Language Semantic Web Services Language (SWSL) . The Semantic Web Service Ontology (SWSO) and Semantic Web Services Language (SWSL) semantics can work together to accomplish tasks.

The Semantic Web Services Ontology (SWSO) is expressed in both FLOWS and ROWS.[6] FLOWS is the First-order Logic Ontology for Web Services; ROWS is the Rules Ontology for Web Services.[6]

Semantic Web Services Ontology (SWSO) develops a first-order logic language along with its sister general-purpose logic language Semantic Web Services Language (SWSL).[6] The expected semantics of the concepts in FLOWS in the Semantic Web Services Ontology (SWSO) can be used in SWSL-FOL; partial semantics of ROWS can also be used in SWSL-Rules.[6]

## Uses of SWSL

The Semantic Web Services Language (SWSL) features include URIs, integration of XML built-in types, and XML-compatible namespaces and import mechanisms.[4] Semantic Web Services Language (SWSL) works with the basic language of the Web to meet the requirements of a single Semantic Web Service and Semantic Web Service Ontology (SWSO).[7][2][8]

The use of The Semantic Web Services Language (SWSL) also includes helping SWSL-Rules work with SWSL-FOL.[4]

Developed with Semantic Web Services Language (SWSL) is FLOWS, which provides a framework for description and reasoning services.[2]

### The cases of Semantic Web Services Language (SWSL)

Negotiation and contracting

When shopping online, buyers and sellers represent “a financing service”[9] and “a delivery service” [9] respectively. When there is a natural conflict of interest between the parties: the seller wants to sell the goods, the buyer wants to benefit from the loss of the goods.[9]

Process Modeling

Process Modeling can be easily divided into three steps: Generic Planning Services; Single or Multiagent Plan Coordination Service and e-Service Composition in a Behavior based Framework.

1\. Generic Planning Services: "This is an example of a service to support the selection or generation of plans and their reliable execution."[10]

2.Single or Multiagent Plan Coordination Service: Single or Multiagent Plan The nature of the Coordination Service is a service, which is designed to coordinate multiple or one plan, handle conflicts and take advantage of collaboration opportunities.[11]

3.e-Service Composition in a Behavior based Framework: e-Service is an operation of outputting and inputting parameters. Under the conditions and effects of both message-based and activity-based, the interactive e-Service can have different combinations.[12] The result of composition can be divided into one-time and reusable. One-time means that the combined results can only be used once and cannot be used for requests from other users.[12] Reusable means that the combined result can be used multiple times and can be used for requests from other users.[12]

Process Enactment

This section shows an example of SWSL using DAML-S, and the services of federated resource coordination operations are constrained by heterogeneous distributed policy sets.[13]

## SWSL-FOL

### Definition

SWSL-FOL, which is SWSL-First-order Logic,[3][4] is a complete first word logic language that extends HiLog's functionality and F-Logic's frame syntax. SWSL-FOL has a Layers structure.

SWSL-FOL and SWSL-Rules are sub-language of the Semantic Web Services Language.[1][2] There is a grammatical overlap between the two. Although each connection used by SWSL-FOL can be used for SWSL-Rules, this does not mean that SWSL-FOL is a subset of the SWSL rules.[1]

### The Syntax And Semantic Extension Of SWSL-FOL

The most basic syntax and semantics of SWSL-FOL's syntax and semantics is SWSL-FOL. Three other enhancements based on SWSL-FOL include: SWSL-FOL + Equality, SWSL-FOL + HiLog and SWSL-FOL + Frames. This helps the SWSL-FOL language to have more powerful features.

The SWSL-FOL + Equality formula adds an equality operator based on SWSL-FOL:=:.[1]

> In this situation, the end of the SWSL-FOL formula uses the (".") symbol.

The SWSL-FOL + HiLog formula extends the object-oriented syntax of the Frames layer of SWSL-Rules.[1]

> This formula extends the semantics and syntax usage rules of the HiLog and HiLog atomic formulas to extend SWSL-FOL. The combination of SWSL-FOL + Equality and SWSL-FOL + HiLog can also extend the syntax and semantics of SWSL-FOL + HiLog, but this does not help SWSL-FOL + Equality upgrade syntax and semantics.

The SWSL-FOL + Frames formula extends the object-oriented syntax of the HiLog layer of SWSL-Rules.[1]

> The combination of SWSL-FOL + Equality and SWSL-FOL + Frame can extend the semantics and syntax of both formulas simultaneously.

### Uses

SWSL-FOL is mainly used to express the formal characteristics of Web services concepts and Semantic Web services, especially the process model:[2]

The composition of the service and the process model;[1]

Verification and verification services after analysis of the process model;[1]

SWSL-FOL is in the form of first-order classical logic.[1]

SWSL-FOL applies the ability to oppose reasoning and/or presence to many use case scenarios and can be used to formally specify service features.

## SWSL-Rules

### Definition

SWSL-Rules, which is Declarative Logic Programs,[3][4] is a non-monotonic semantic and rule-based language. SWSL-Rules is not first-order.[1] SWSL-Rules has a Layers structure.[4]

Among them, the pure Horn subset in SWSL-Rules constitutes the core of the SWSL-Rules.

### The Syntax And Semantic Extension Of SWSL-Rules

SWSL-Rules is a Declarative Logic Programs that combines different layers of SWSL-Rules syntax and semantics into a knowledge representation language. The structure of SWSL-Rules can be easily divided into NAF, Courteous, HiLog, Frames and Reification layers. In the SWSL-Rules different branches are orthogonal and can be combined.[4][1]

NAF indicates the negation and failure of SWSL-Rules in the semantic sense. The Courteous extension features SWSL-Rules, adding syntax to limit classic negation and priority rules. Nonmon LT extends the semantics and syntax of SWSL-Rules by extending the meaning of quantifiers and rule bodies. HiLog belongs to the first order, enabling highly metaprogramming by allowing variables to transcend predicate symbols, function symbols, and formulas.

Frames layer introduces the most common object-oriented features. Both the HiLog and Frames layers extend the syntax and semantics of SWSL-Rules at different levels in different ways. The Reification layer is used to create objects with WSL-Rules formulas. The Lloyd-Topor extension and the Courteous rule extension provide all normal first-order connections for SWSL rules.[1]

Therefore, the syntax SWSL rule contains all the connections of the complete first-order logic, which provides a bridge for SWSL-FOL.

### Uses

SWSL-Rules is mainly used to express the formal characteristics of Web services concepts and Semantic Web services, especially the process model:[2][1]

* rust in security, privacy and confidentiality authorization policies;
* Contracts and advertising;
* Supervise certain procedures for identifying and resolving anomalies;
* Semantic mediation of translation between different ontology or context;

Use an object-oriented ontology with default inheritance with priority and/or cancellation (for example, in the Program Manual. The logically non-monotonic nature of SWSL rules is widely used for negative failures and/or polite priority conflict handling and similar events.

SWSL-FOL applies the ability to oppose reasoning and/or presence to many use-case scenarios that can be used to formalize service features, while SWSL rules are used to infer these features and perform service.

## Language

### The Layered Structure

The semantics and syntax within the layer enhance the language modeling capabilities of SWSL. It makes it easier for learners and administrators to learn and manipulate the language and understand the relationships between different functions within the layer.

In addition, the semantics and syntax of the sub-language SWSL-Rules or SWSL-FOL inside SWSL is usually extended by updating most of the layers that are the core of the language. The layers are independent of each other, but can be combined with each other, and the specific combination is different in the two sub-language. This can provide some guidance for vendors who may only be interested in a particular subset of features.[1]

### Main layers

#### The Monotonic Lloyd-Topor Layer:[1]

The Monotonic Lloyd-Topor Layer extends the Horn layer by using Disjunction in the rule body; Conjunction in the rule head; and allowing new symbols of classical implication to be used in the rule head.

* The forms of classical implication: formula1 ==> formula2; formula1 <== formula2
* The new symbols of classical implication in Monotonic Lloyd-Topor Layer: formula1 <==> formula2

#### The NAF Layer

The NAF layer add the negation-as-failure symbol, naf.

The form of NAF layer: p(?X,?Y) :- q(?X,?Z) and naf r(?Z,?Y)

The NAF layer extends the semantics of SWSL-Rules by adding a negative failure symbol naf. The main advantage of this semantic is that it is easy to calculate, and the definition of its model is unique.

* The form before the NAF layer extends naf syntax: ... :- ... and naf r(?X) and ...
* The form after the NAF layer extends naf syntax: ... :- ... and ∃ X (naf r(?X)) and ... or ... :- ... and ∀ X (naf r(?X)) and ...[1]

#### The Nonmonotonic Lloyd-Topor Layer

The Nonmonotonic Lloyd-Topor Layer introduces explicit bounded quantifiers: <==, ==> and the bi-implication symbol <==> in the rule body.

For example, classical implication A <== B is interpreted in a non-classical way: as (A or naf B) rather than (A or neg B).[1]

#### The Courteous Rules Layer

The Courteous Rules Layer is upgraded for conflict handling, and syntax and semantics extend four new features:

* Rule labels: The name that prioritizes between rules. The form of rule labels in Courteous Rules Layer :{label} head :- body.
* Classical negation of atoms; prioritization predicate: rules can be sorted by priority[1]

#### The HiLog Layer

The HiLog Layer extends the first-order syntax of Semantic Web Services Language (SWSL) by allowing variables to be used beyond the function notation, predicate symbol, and atomic formula range. The expanded functionality of The HiLog Layer supports materialization and plays a key role in exploring unknown knowledge structures.

"HiLog term (abbr., H-term): A HiLog term is either a first-order term or an expression of the following form: t(t1,...,tn), where t, t1, ..., tn are HiLog terms."[1]

#### The Equality Layer

The Equality Layer adds a complete equality predicate to the Semantic Web Services Language (SWSL) that obeys the equal congruence axioms of equality, :=: .[1]

* The equality predicates in The Equality Layer are transitive and symmetrical.
* The logical implication relationship is constant when it is equal to or equal to or equal to.

#### The Frames Layer

The Frames Layer mimics F-logic's addition of Frame syntax to extend semantics. The Frames are called molecules in the Frames Layer, which introduces object-oriented syntax.[1]

* The Frame syntax.
* Path expressions.
* Class membership and class subclasses.
* The signature molecules will give a representation of the type specification.

## References

1. ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 Battle, Steve; Bernstein, Abraham; Boley, Harold; Grosof, Benjamin; Gruninger, Michael; Hull, Richard; Kifer, Michael; Martin, David et al.. "Semantic Web Services Language (SWSL)". https://www.w3.org/Submission/SWSF-SWSL/. Retrieved 1 May 2019.
2. ↑ 2.0 2.1 2.2 2.3 2.4 2.5 Battle, Steve; Bernstein, Abraham; Boley, Harold; Grosof, Benjamin; Gruninger, Michael; Hull, Richard; Kifer, Michael; Martin, David et al.. Semantic Web Services Framework (SWSF) Overview. https://www.w3.org/Submission/SWSF/. Retrieved 1 May 2019.
3. ↑ 3.0 3.1 3.2 3.3 Fensel, Dieter; Facca, Federico; Toma, Ioan; Simperl, Elena (2011). Semantic Web Services. STI Innsbruck, ICT-Technologiepark University of Innsbruck ，Institute AIFB, Building 11.40 Karlsruhe Institute of Technology. doi:10.1007/978-3-642-19193-0. ISBN 978-3-642-19192-3. https://semanticscholar.org/paper/a928d87cb00834ac1267bebe82b5ce25d145c9ad.
4. ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 Grosof, Benjamin; Kifer, Michael; Martin, David. "Rules in the Semantic Web Services Language (SWSL): An Overview for Standardization Directions". https://pdfs.semanticscholar.org/7d55/3960c42f361cab0fd0c6fa8cb0ff734824fe.pdf. Retrieved 12 April 2019.
5. ↑ Battle, Steve; Bernstein, Abraham; Boley, Harold; Grosof, Benjamin; Gruninger, Michael; Hull, Richard; Kifer, Michael; Martin, David et al.. "Semantic Web Services Framework (SWSF)". https://www.w3.org/Submission/2005/07/.
6. ↑ 6.0 6.1 6.2 6.3 Battle, Steve; Bernstein, Abraham; Boley, Harold; Grosof, Benjamin; Gruninger, Michael; Hull, Richard; Kifer, Michael; Martin, David et al.. "Semantic Web Services Ontology (SWSO)". https://www.w3.org/Submission/2005/SUBM-SWSF-SWSO-20050909/. Retrieved 20 May 2019.
7. ↑ Sheu, Phillip; Yu, Heather; Ramamoorthy; Joshi, Arvind; Zadeh, Lotfi (2010). Semantic Computing. IEEE Press Editorial Board. doi:10.1002/9780470588222. ISBN 9780470464953.
8. ↑ Shin, Kang; Kiskis (1994). "SWSL: a synthetic workload specification language for real-time systems". IEEE Transactions on Software Engineering (IEEE) 20 (10): 798–811. doi:10.1109/32.328992.
9. ↑ 9.0 9.1 9.2 Kifer, Michael. "A Buying Contract that Utilizes Escrow". http://www.daml.org/services/use-cases/language/BuyWithEscrow.html.
10. ↑ Tate, Austin. "Usage Scenario: Generic Planning Services". University of Edinburgh. http://www.daml.org/services/use-cases/language/SWSL-Planning-Service.html.
11. ↑ Cox, Jeffrey; Durfee, Edmund. "Usage Scenario: Single or Multiagent Plan Coordination Service". University of Michigan. http://www.daml.org/services/use-cases/language/PlanCoordination.html.
12. ↑ 12.0 12.1 12.2 Hull, Rick; Berardi, Daniela. "Usage Scenario:e-Service Composition in a Behavior based Framework". http://www.daml.org/services/use-cases/language/swsl-usecase/Composition.htm.
13. ↑ Bradshaw, Jeff; Uszok, Andrzej. "Usage Scenario: Coalition Search & Rescue Policy Service". Institute for Human and Machine Cognition, Pensacola, FL; Austin Tate, Artificial Intelligence Applications Institute, University of Edinburgh. http://www.daml.org/services/use-cases/language/Coalition-SAR-Policy-Service.html.

## External links

* v
* t
* e

World Wide Web Consortium (W3C)

Products and
standards|

| Recommendations|

* ActivityPub
* ARIA
* Canonical XML
* CDF
* CSS
* DOM
* Geolocation API
* HTML (HTML5)
* ITS
* JSON-LD
* Linked Data Notifications
* MathML
* Micropub
* OWL
* PLS
* RDF
* RDF Schema
* SISR
* SKOS
* SMIL
* SOAP
* SRGS
* SRI
* SSML
* SVG
* SCXML
* SHACL
* SPARQL
* Timed text
* VoiceXML
* Web storage
* WSDL
* Webmention
* WebSub
* XForms
* XHTML
* XHTML+RDFa
* XInclude
* XLink
* XML
* XML Base
* XML Encryption
* XML Events
* XML Information Set
* XML namespace
* XML Schema
* XML Signature
* XOP
* XPath
* XPath 2.0
* XPointer
* XProc
* XQuery
* XSL
* XSL-FO
* XSLT (elements)

|

Notes|

* IndieAuth
* JF2
* Post Type Discovery
* XAdES
* XHTML+SMIL
* XUP

Working drafts|

* CCXML
* CURIE
* EME
* InkML
* MSE
* RIF
* SMIL Timesheets
* sXBL
* XFDL
* XFrames
* XBL
* XMLHttpRequest

Guidelines|

* Web Content Accessibility Guidelines

Initiative|

* Multimodal Interaction Activity (MMI)
* Markup Validation Service
* Web Accessibility Initiative
* WebPlatform

Deprecated|

* C-HTML
* HDML
* JSSS
* PGML
* VML
* XHTML+MathML+SVG

Obsoleted|

* P3P

Organizations|

* Advisory Committee (AC)
* World Wide Web Foundation

Elected groups|

* Advisory Board (AB)

Working groups|

* CSS
* Geolocation
* Social Web
* SVG
* Web Hypertext Application Technology (WHATWG)
* Web Platform

Community groups|

* Web Incubator Community Group (WICG)

Closed groups|

* Device Description (DDWG)
* HTML

Software|

* CERN httpd
* Libwww

Browsers|

* Line Mode (1990–)
* Arena (1993–98)
* Agora (1994–97)
* Argo (1994–97)
* Amaya (browser/editor, 1996–2012)

Conferences|

* International World Wide Web Conference (IW3C)
* Steering Committee (IW3C2)
* First conference ("WWW1", 1994)

* v
* t
* e

Semantic Web

Background|

* Databases
* Hypertext
* Internet
* Ontologies
* Semantics
* Semantic networks
* World Wide Web

Sub-topics|

* Dataspaces
* Hyperdata
* Linked data
* Rule-based systems

Applications|

* Semantic analytics
* Semantic broker
* Semantic computing
* Semantic mapper
* Semantic matching
* Semantic publishing
* Semantic reasoner
* Semantic search
* Semantic service-oriented architecture
* Semantic wiki

Related topics|

* Collective intelligence
* Description logic
* Folksonomy
* Geotagging
* Information architecture
* Knowledge extraction
* Knowledge management
* Knowledge representation and reasoning
* Library 2.0
* Digital library
* Digital humanities
* Metadata
* References
* Topic map
* Web 2.0
* Web engineering
* Web Science Trust

Standards|

| Syntax and supporting technologies|

* HTTP
* IRI
* URI
* RDF
* triples
* RDF/XML
* JSON-LD
* Turtle
* TriG
* Notation3
* N-Triples
* TriX (no W3C standard)
* RRID
* SPARQL
* XML
* Semantic HTML

|

Schemas, ontologies and rules|

* Common Logic
* OWL
* RDFS
* Rule Interchange Format
* Semantic Web Rule Language
* ALPS
* SHACL

Semantic annotation|

* eRDF
* GRDDL
* Microdata
* Microformats
* RDFa
* SAWSDL
* Facebook Platform

Common vocabularies|

* DOAP
* Dublin Core
* FOAF
* Schema.org
* SIOC
* SKOS

Microformat vocabularies|

* hAtom
* hCalendar
* hCard
* hProduct
* hRecipe
* hResume
* hReview

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Semantic Web Services Language. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Semantic_Web_Services_Language&oldid=238385"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template