language en

Service Interaction Context Ontology (SICO)

This version:
http://ontologies/interactioncontext
Latest version:
http://ontologies/interactioncontext
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://insertlicenseURIhere.example.org
Visualization:
Visualize with WebVowl
Cite as:
Retrieved from: http://ontologies/interactioncontext
Ontology Specification Draft

Abstract

The Service Interaction Context Ontology, (SICO) is an ontology designed for modeling and representing interactions within a service-oriented or S-PSS environment. This ontology is expressed in RDF/XML format and follows the OWL (Web Ontology Language) standard. SICO defines a set of classes and properties to represent various entities, including interactions, users, services, subservices, context, and more. It also incorporates data properties to capture information such as location, name, and value, as well as object properties to establish relationships between entities. Notably, SICO includes rules, utilizing the SWRL (Semantic Web Rule Language) to infer relationships and dependencies among entities. The ontology aims to provide a comprehensive framework for describing and understanding the context of interactions within a service-oriented environment, facilitating the modeling and analysis of complex systems involving users, services, and their interactions in several contexts.

Introduction back to ToC

The resulting ontology, Service Interaction Context Ontology (SICO) was created in Protégé. To represent the components of the ontology, we divided the entities into three groups: S-PSS, Context, and Interaction.
  • S-PSS: In an S-PSS, a static model is necessary to represent the services of smart devices. In accordance with Maleki et al. (2018a), each service is modeled into a pattern that relates the service with the product and required information. Services may be grouped into related sub-services. A sub-service represents a specific function of the e-service platform or smart device, requiring information in the form of rules, measures, and parameters. The product itself is closely related to the physical components that need to integrate sensors in the solution.
  • CONTEXT: The second group further extends the framework ontology model to incor- porate context-specific entities and relationships. The ontology encompasses four major sources of contextual information: device, user/identity, environment, and time (Iqbal et al., 2021). Device context will refer to information relevant to the status and particular properties of the SCP. The user identity context can encompass demographic details such as age-group, location, education level, reflecting the type of an individual or a user group. The environmental and time context will refer to the surrounding conditions and temporal aspects influencing the SCP or user interaction. This includes factors such as ambient conditions, time of day, and other situational variables that contribute to an understanding of the overall context in which the device or user operates. Because contextual data is dynamic, it needs to be created as instances or individuals derived from these types for each particular implementation of the framework.
  • INTERACTION: In the last group, following a bottom-up approach, we analyzed a dataset from collected user interactions (Carrera-Rivera et al., 2023), to define the entities and their relationships with the services and contextual data within the ontology. Interaction sequences represent an ordered set of individual interactions performed by users within the system and are linked to a specific service or sub-service. Interactions can take various forms (i.e. click, scroll, hover) and have the ability to trigger events. To enhance the understanding and analysis of these events, it was crucial to name them appropriately. Once these elements were incorporated into the ontology, a comprehensive representation of user interactions and their connections to the system behavior and functionality was achieved.

Namespace declarations

Table 1: Namespaces used in the document
owl<http://www.w3.org/2002/07/owl#>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
rdfs<http://www.w3.org/2000/01/rdf-schema#>
sico<http://ontologies/interactioncontext#>
swrl<http://www.w3.org/2003/11/swrl#>
swrla<http://swrl.stanford.edu/ontologies/3.3/swrla.owl#>
swrlb<http://www.w3.org/2003/11/swrlb#>
xml<http://www.w3.org/XML/1998/namespace>
xsd<http://www.w3.org/2001/XMLSchema#>

Service Interaction Context Ontology (SICO): Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Service Interaction Context Ontology (SICO): Description back to ToC

The Service Interaction Context Ontology, (SICO) is an ontology designed for modeling and representing interactions within a service-oriented or S-PSS environment. This ontology is expressed in RDF/XML format and follows the OWL (Web Ontology Language) standard. SICO defines a set of classes and properties to represent various entities, including interactions, users, services, subservices, context, and more. It also incorporates data properties to capture information such as location, name, and value, as well as object properties to establish relationships between entities. Notably, SICO includes rules, utilizing the SWRL (Semantic Web Rule Language) to infer relationships and dependencies among entities. The ontology aims to provide a comprehensive framework for describing and understanding the context of interactions within a service-oriented environment, facilitating the modeling and analysis of complex systems involving users, services, and their interactions in several contexts.

Cross-reference for Service Interaction Context Ontology (SICO) classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Service Interaction Context Ontology (SICO).

Classes

contextc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Context

The top-level class representing a contextual element, which can include devices, environments, identities, and time.
has sub-classes
device c, environment c, identity c, time c
is in range of
occurs in op

devicec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Device

has super-classes
context c

environmentc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Environment

has super-classes
context c

identityc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Identity

has super-classes
context c

informationc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Information

A class representing general information entities. Subclasses might include measures, rules, and other information-related concepts.
has sub-classes
measure c, rule c

interactionc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Interaction

A class representing interactions between various entities in the context, capturing the dynamics of user-device, device-device, or user-environment interactions.
is in domain of
belongs to op, element dp, order dp
is in range of
has interactions op

interaction sequencec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#InteractionSequence

A class representing a sequence or series of interactions
is in domain of
executes op, has interactions op, is made by op, occurs in op
is in range of
belongs to op, is executed with op, makes op

measurec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Measure

has super-classes
information c
is in range of
detects op

productc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Product

A class representing products or objects that may be associated with sensors, services, or user interactions.
is in domain of
has sensors op, has services op
is in range of
is service of op

ratingc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Rating

A class representing ratings or evaluations provided by users or other entities to interactions, products, or services.
is in domain of
is for a op, is from a op

rulec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Rule

has super-classes
information c

sensorc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Sensor

Description: A class representing sensors or sensor devices used to collect data within the interaction context.
is in domain of
detects op
is in range of
has sensors op

servicec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Service

A class representing services or functionalities provided by products or devices within.
has sub-classes
subservice c
is in domain of
has subservices op, is service of op
is in range of
has services op, is subservice of op

subservicec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Subservice

A subclass of Service that represents subcomponents or subfunctionalities of larger services, allowing for hierarchical service modeling.
has super-classes
service c
is in domain of
is executed with op, is subservice of op, is used by op
is in range of
executes op, has subservices op, is for a op, uses op

timec back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#Time

has super-classes
context c

userc back to ToC or Class ToC

IRI: http://ontologies/interactioncontext#User

User
is in domain of
has role op, makes op, uses op
is in range of
is from a op, is made by op, is role of op, is used by op

Object Properties

belongs toop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#belongs_to

has characteristics: functional

has domain
interaction c
has range
interaction sequence c
is inverse of
has interactions op

detectsop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#detects

has domain
sensor c
has range
measure c

executesop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#executes

has characteristics: functional, asymmetric

has domain
interaction sequence c
has range
subservice c
is inverse of
is executed with op

has interactionsop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#has_interactions

has characteristics: inverse functional

has domain
interaction sequence c
has range
interaction c
is inverse of
belongs to op

has roleop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#has_role

has characteristics: functional

has super-properties
top object property
has domain
user c
is inverse of
is role of op

has sensorsop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#has_sensors

has domain
product c
has range
sensor c

has servicesop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#has_services

has characteristics: inverse functional

has domain
product c
has range
service c
is inverse of
is service of op

has subservicesop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#has_subservices

has domain
service c
has range
subservice c
is inverse of
is subservice of op

has tagsop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#has_tags

has characteristics: transitive

has domain
service c or subservice c
is inverse of
is tag of op

is executed withop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_executed_with

has characteristics: inverse functional

has domain
subservice c
has range
interaction sequence c
is inverse of
executes op

is for aop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_for_a

has characteristics: functional

has domain
rating c
has range
subservice c

is from aop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_from_a

has characteristics: functional

has domain
rating c
has range
user c

is made byop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_made_by

has characteristics: functional

has domain
interaction sequence c
has range
user c
is inverse of
makes op

is role ofop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_role_of

has range
user c
is inverse of
has role op

is service ofop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_service_of

has characteristics: functional

has domain
service c
has range
product c
is inverse of
has services op

is subservice ofop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_subservice_of

has characteristics: functional

has domain
subservice c
has range
service c
is inverse of
has subservices op

is tag ofop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_tag_of

has range
service c or subservice c
is inverse of
has tags op

is used byop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#is_used_by

has super-properties
top object property
has domain
subservice c
has range
user c
is inverse of
uses op

makesop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#makes

has characteristics: inverse functional

has domain
user c
has range
interaction sequence c
is inverse of
is made by op

occurs inop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#occurs_in

has characteristics: inverse functional

has domain
interaction sequence c
has range
context c

usesop back to ToC or Object Property ToC

IRI: http://ontologies/interactioncontext#uses

has characteristics: inverse functional, asymmetric

has domain
user c
has range
subservice c
is inverse of
is used by op

Data Properties

elementdp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#element

has domain
interaction c
has range
string

end datedp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#endDate

has domain
interaction c or interaction sequence c
has range
date time

iddp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#id

has range
int

namedp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#name

has characteristics: functional

has super-properties
top data property
has range
string

orderdp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#order

has domain
interaction c
has range
integer

start datedp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#startDate

has domain
interaction c or interaction sequence c
has range
date time

tagdp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#tag

has characteristics: functional

has range
string

value interactiondp back to ToC or Data Property ToC

IRI: http://ontologies/interactioncontext#valueInteraction

has domain
interaction c or interaction sequence c
has range
double

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

References back to ToC

Add your references here. It is recommended to have them as a list.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.