Service-Oriented Architecture Ontology Version 2.0 – Class Relationship Matrix
This appendix contains a class relationship matrix that illustrates the class-to-class relationships intrinsic in the OWL definitions of the SOA ontology. The matrix is deterministically derived from the OWL ontology definitions. Each row X and each column Y corresponds to an OWL class. A relation appears in cell (X,Y) if and only if class X is part of the domain and class Y is part of the range of the corresponding OWL property. Note that this means that datatype properties (which do not have a range) are not included in the class relationship matrix.
As outlined in the body of the document there are four relationships in the table (plus their inverses and sub-classed derivatives) that are technically allowed according to the OWL definitions, but would not be expected to occur in a practical application of the ontology. Specifically, services are not expected to perform services, services are not expected to use elements (directly), services are not expected to represent elements, and services are not expected to orchestrate compositions – all due to the Service class being defined as a logical representation of a repeatable activity; see The performs and performedBy Properties, The uses and usedBy Properties Applied to Service, The represents and representedBy Properties Applied to Service and The orchestrates and orchestratedBy Properties for details.
|
Element |
System |
Service |
Human Actor |
Task |
Element |
uses |
uses |
uses |
uses |
uses |
System |
uses |
uses |
uses |
uses |
uses |
Service |
uses |
uses |
uses |
uses |
uses |
Human Actor |
uses |
uses |
uses |
uses |
uses |
Task |
uses |
uses |
uses |
uses |
uses |
Composition |
uses |
uses |
uses |
uses |
uses |
Process |
uses |
uses |
uses |
uses |
uses |
Service Composition |
uses |
uses |
uses |
uses |
uses |
Service Contract |
|
|
isContractFot |
involvesParty |
|
Effect |
|
|
|
|
|
Service Interface |
|
|
isInterfaceOf |
|
|
Information Type |
|
|
|
|
|
Event |
generatedBy |
generatedBy |
generatedBy |
generatedBy |
generatedBy |
Policy |
appliesTo |
appliesTo |
appliesTo |
isSetBy |
appliesTo |
Thing |
|
|
|
|
|
|
Composition |
Process |
Service Composition |
Service Contract |
Effect |
Element |
uses |
uses |
uses |
|
|
System |
uses |
uses |
uses |
|
|
Service |
uses |
uses |
uses |
hasContract |
|
Human Actor |
uses |
uses |
uses |
isPartyTo |
|
Task |
uses |
uses |
uses |
|
|
Composition |
uses |
uses |
uses |
|
|
Process |
uses |
uses |
uses |
|
|
Service Composition |
uses |
uses |
uses |
|
|
Service Contract |
|
|
|
|
specifies |
Effect |
|
|
|
isSpecifiedBy |
|
Service Interface |
|
|
|
|
|
Information Type |
|
|
|
|
|
Event |
generatedBy |
generatedBy |
generatedBy |
|
|
Policy |
appliesTo |
appliesTo |
appliesTo |
appliesTo |
appliesTo |
Thing |
|
|
|
|
|
|
Service Interface |
Information Type |
Event |
Policy |
Thing |
Element |
|
|
generates |
isSubjectTo |
|
System |
|
|
generates |
isSubjectTo |
|
Service |
hasInterface |
|
generates |
isSubjectTo |
|
Human Actor |
|
|
generates |
setsPolicy |
|
Task |
|
|
generates |
isSubjectTo |
|
Composition |
|
|
generates |
isSubjectTo |
|
Process |
|
|
generates |
isSubjectTo |
|
Service Composition |
|
|
generates |
isSubjectTo |
|
Service Contract |
|
|
|
isSubjectTo |
|
Effect |
|
|
|
isSubjectTo |
|
Service Interface |
|
hasInput |
|
isSubjectTo |
|
Information Type |
isInputAt |
|
|
isSubjectTo |
|
Event |
|
|
|
isSubjectTo |
|
Policy |
appliesTo |
appliesTo |
appliesTo |
appliesTo |
appliesTo |
Thing |
|
|
|
isSubjectTo |
|