Profile.owl revision c4c2756a7ac6ba51ca2f35240bdb0cf99cf2092b
<?xml version='1.0' encoding='ISO-8859-1'?>
<!DOCTYPE uridef [
<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns">
]>
<!--
This document uses entity types as a shorthand for URIs.
For a version with unexpanded entities, try loading this source
into Internet Explorer.
-->
<rdf:RDF
xmlns:rdf= "&rdf;#"
xmlns:rdfs= "&rdfs;#"
xmlns:owl= "&owl;#"
xmlns:service="&service;#"
xmlns:process="&process;#"
xmlns= "&DEFAULT;#"
xml:base= "&DEFAULT;">
<owl:Ontology rdf:about="">
<owl:versionInfo>
$Id$
</owl:versionInfo>
<rdfs:comment>
OWL ontology for Advertisements (i.e. Profiles).
This file belongs to the OWL-S Release.
Initial version created by Terry Payne (trp@ecs.soton.ac.uk).
Modified by Massimo Paolucci (paolucci@cs.cmu.edu)
Modified by David Martin and other members of the OWL-S Coalition.
</rdfs:comment>
<rdfs:seeAlso rdf:resource="http://www.daml.org/services/owl-s/1.1/ProfileAdditionalParameters.owl" />
<rdfs:seeAlso rdf:resource="http://www.daml.org/services/owl-s/1.1/ProfileDeprecatedElements.owl" />
<!--
-->
<owl:imports>
<owl:Ontology rdf:about="&service;" />
</owl:imports>
<owl:imports>
<owl:Ontology rdf:about="&process;" />
</owl:imports>
</owl:Ontology>
<!-- ############ ########### ############ ############ ########### -->
<!--
Organization of this file:
1. Log of changes
2. Definition of Profile
It provides a definition of the Profile class
3. Non-Functional Properties
It provides a definition of properties such as name of the
service, contact information, quality of the service, and
additional information that may help to evaluate the service
4. Functional Properties
Input/Output/Precondition/Effects that help with the
specification of what the service provides
5. Additional Classes
These are classes that are needed to specify details of the
Profile
- Service Category
- Service Parameters
- Quality Rating
6. Deprecated
Classes and properties that were of relevance in the previous
versions of the profile, but they are no longer relevant as of
version 0.7. They are maintained here as deprecated, but will be
removed removed in following versions of the service profile
-->
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### -->
<!-- ############ LOG OF CHANGES from 0.7 to 0.9 ########### -->
<!-- ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
* Remove Deprecated functions and save them in a separate file for reference.
These were deprecated in version 0.7 (see below) and have now been removed
from this file
* Migration of example and useful service parameters to a separate file.
Version 0.7 introduced several useful classes that were derived from top
level profile classes such as serviceParameter. These have now been moved
to a supplementary file.
* Removal of Actor proterties
The Actor class and its properties have been moved to a separate file. It
represents actors within a service description. Alternative concepts
can be used to represent individuals. Examples include FOAF or vCard.
* Renaming of the ParameterDescription to FunctionalPropertyDescription
* Creation of the following FunctionalPropertyDescription classes:
InputDescription,
OutputDescription,
PreconditionDescription
EffectDescription
where each has an explicit range restriction. All of these classes are
now disjoint.
* Renaming parameterName to functionalPropertyName.
-->
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### -->
<!-- ############ LOG OF CHANGES from 0.6 to 0.7 ########### -->
<!-- ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
* Deprecations:
- OfferedService
- NeededService
- ServiceRequester
- ServiceProvider
- serviceType
- intendedPurpose
- role
- requestedBy
- providedBy
- domainResource
- geographicRadius
- degreeOfQuality
- qualityGuarantee
- communicationThru
- Location
* ParameterDescription
- parameterName turned from OWL:#Thing to XSD:string. The name
of a parameter is just a string
- restrictedTo: added maxCardinality restriction to 1
- refersTo: added maxCardinality restriction to 1
* Added ContactInformation to collect information about whom to
refer to when using the service
* Added title property to Actor
* Added examples of service categories
- Naics
- UNSPSC
* Added examples of Service Parameters
- MaxResponseTime
- AverageResponseTime
- GeographicRadius
* Added examples of QualityRating
- D&B
-->
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### -->
<!-- ############ PROFILE ########### -->
<!-- ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
Profile is a subclass of ServiceProfile. It is used to
acknowledge that there may be different ways to profile services
that are different from the way we expressed it so far.
-->
<owl:Class rdf:ID="Profile">
<rdfs:label>Profile</rdfs:label>
<rdfs:subClassOf rdf:resource="&service;#ServiceProfile" />
<rdfs:comment>
Definition of Profile
</rdfs:comment>
</owl:Class>
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### -->
<!-- ############ PROFILE ########### -->
<!-- ############ NON FUNCTIONAL PROPERTIES ########### -->
<!-- ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
The Service Name refers to the name of the service that is being
offered.
-->
<owl:DatatypeProperty rdf:ID="serviceName">
<rdfs:domain rdf:resource="#Profile"/>
</owl:DatatypeProperty>
<!-- there is only one name per profile -->
<owl:Class rdf:about="#Profile">
<rdfs:comment>
A profile can have only one name
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#serviceName"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!--
The TextDescription provides a brief description of the service.
It summarisese what the service offers, or to describe what
service is requested.
-->
<owl:DatatypeProperty rdf:ID="textDescription">
<rdfs:domain rdf:resource="#Profile"/>
</owl:DatatypeProperty>
<!-- there is only one text description per profile -->
<owl:Class rdf:about="#Profile">
<rdfs:comment>
A profile can have only one text description
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#textDescription"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!--
Contact information is used to record contact information
about the entity that issued the Profile. It once refered to Actor,
that records address and other info that allows a receiver of the
profile to contact directly the issuer. However, this class has migrated
to a separate ActorDefault.daml ontology.
Previous versions of the OWL-S profile defined the range as follows:
<rdfs:range rdf:resource="#Actor"/>
This definition has migrated to ActorDefault.daml
-->
<owl:ObjectProperty rdf:ID="contactInformation">
<rdfs:domain rdf:resource="#Profile"/>
</owl:ObjectProperty>
<!--
has_process is a pointer the process that is associated with the
service.
-->
<owl:ObjectProperty rdf:ID="has_process">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="&process;#Process"/>
</owl:ObjectProperty>
<owl:FunctionalProperty rdf:about="#has_process"/>
<!--
serviceCategory refers to an ontology of services that
may be on offer. High level services could include
classification on the bases of industry taxonomies such as
NAICS or UNSPCP or DandB or others that may be used.
Additionally, it can be used to specify other classification
systems such as
* Products
* Problem Solving Capabilities
* Commercial Services
* Information
etc
No range restrictions are placed on this property at present.
Specific service descriptions will specialise this by
restricting the range appropriately using subPropertyOf.
Examples of usage of serviceCategory are given in
QualityRating has been deprecated, as it can be constructed
from the ServiceParameter class.
-->
<owl:ObjectProperty rdf:ID="serviceCategory">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="#ServiceCategory"/>
</owl:ObjectProperty>
<!--
serviceParameters - An expandable list of properties that
may accompany a profile description.
The range of each property is unconstrained, i.e. no range restrictions
are placed on the service parameters at present. Specific service
parameters will specialise this property by restricting the range
appropriately and using subPropertyOf.
-->
<owl:ObjectProperty rdf:ID="serviceParameter">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="#ServiceParameter"/>
</owl:ObjectProperty>
<!-- ############ ########### ############ ############ ########### -->
<!-- ####### ###### -->
<!-- ####### SERVICE PROFILE FUNCTIONALITY DESCRIPTION ###### -->
<!-- ####### ###### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
This ontology has no classes for modelling IOPE's. Profile
instances will be able to define IOPE's using the schema
offered by the Process.owl ontology.
The hasParameter property relates Profile instances to
process:Parameter instances. In particular, there are subproperties
of hasParameter for process:Input and process:Output:
*hasInput
*hasOutput
In addition, the following properties relate Profile to
expr:Condition and process:Result:
*hasPrecondition
*hasResult.
-->
<owl:ObjectProperty rdf:ID="hasParameter">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="&process;#Parameter"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="hasInput">
<rdfs:subPropertyOf rdf:resource="#hasParameter"/>
<rdfs:range rdf:resource="&process;#Input"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="hasOutput">
<rdfs:subPropertyOf rdf:resource="#hasParameter"/>
<rdfs:range rdf:resource="&process;#Output"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="hasPrecondition">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="&expr;#Condition"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="hasResult">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="&process;#Result"/>
</owl:ObjectProperty>
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
ServiceCategory describes categories of services on the bases of
some classification that may be outside OWL-S and possibly
outside OWL. In the latter case, they may require some
specialized reasoner if any inference has to be done with it
-->
<owl:Class rdf:ID="ServiceCategory"/>
<!-- categoryName is the name of the actual category, which could be just a literal,
or perhaps the uri of the process parameter (a property)
-->
<owl:DatatypeProperty rdf:ID="categoryName">
<rdfs:domain rdf:resource="#ServiceCategory"/>
</owl:DatatypeProperty>
<!-- each serviceCategory can refer to only one categoryName -->
<owl:Class rdf:about="#ServiceCategory">
<rdfs:comment>
a ServiceCategory is restricted to refer to only onename
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#categoryName"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!-- taxonomy stores a reference to the taxonomy scheme. It can be
either the URL of the taxonomy, or the name of the taxonomy or
anything else. -->
<owl:DatatypeProperty rdf:ID="taxonomy">
<rdfs:domain rdf:resource="#ServiceCategory"/>
</owl:DatatypeProperty>
<!-- each serviceCategory can refer to only one taxonomy, to limit
the possibility of confusion. -->
<owl:Class rdf:about="#ServiceCategory">
<rdfs:comment>
a ServiceCategory is restricted to refer to only one taxonomy
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#taxonomy"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!-- value points to the value in a specific taxonomy
There may be more than one value for each taxonomy, so no
restriction is added here.
-->
<owl:DatatypeProperty rdf:ID="value">
<rdfs:domain rdf:resource="#ServiceCategory"/>
</owl:DatatypeProperty>
<!-- each serviceCategory can refer to only one value,
if more then one value applies, then they have to be added as a
string with space separators -->
<owl:Class rdf:about="#ServiceCategory">
<rdfs:comment>
a ServiceCategory is restricted to refer to only one taxonomy
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#value"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!-- Often taxonomies associate a code to each type of service.
The following property stores the code -->
<owl:DatatypeProperty rdf:ID="code">
<rdfs:domain rdf:resource="#ServiceCategory"/>
</owl:DatatypeProperty>
<!-- each serviceCategory can refer to only one code,
if more then one value applies, then they have to be added as a
string with space separators
There may be of course a problem of synchronization with the value -->
<owl:Class rdf:about="#ServiceCategory">
<rdfs:comment>
a ServiceCategory is restricted to refer to only one taxonomy
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#code"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!--
ServiceParameter describes service parameters.
In general we can think this class as the root of an ontology of
Service Parameters of different types. Other types of
ServiceParameters may expand this definition by adding other
properties.
-->
<owl:Class rdf:ID="ServiceParameter"/>
<!-- serviceParameterName is the name of the actual parameter, which could be just a literal,
or perhaps the uri of the process parameter (a property)
-->
<owl:DatatypeProperty rdf:ID="serviceParameterName">
<rdfs:domain rdf:resource="#ServiceParameter"/>
</owl:DatatypeProperty>
<owl:Class rdf:about="#ServiceParameter">
<rdfs:comment>
A ServiceParameter should have at most 1 name (more precisely only
one serviceParameterName)
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#serviceParameterName"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!-- sParameter points to the value of the parameter within some
OWL ontology -->
<owl:ObjectProperty rdf:ID="sParameter">
<rdfs:domain rdf:resource="#ServiceParameter"/>
<rdfs:range rdf:resource="&owl;#Thing"/>
</owl:ObjectProperty>
<owl:Class rdf:about="#ServiceParameter">
<rdfs:comment>
a Parameter is restricted to refer to only one concept in some
ontology
</rdfs:comment>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#sParameter"/>
<owl:cardinality rdf:datatype="&xsd;#nonNegativeInteger">1</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<!-- Taxononomies of businesses and products (such as NAICS and
UNSPSC) are already available and they may be translated in OWL in
the near future. Here we offer the possibility to specify the type
of service that is provided as well as the type of product. In
addition, we provide the bases for a retrieval of services on the
bases of these two features.
-->
<!-- Map the Profile to a Service Type -->
<owl:DatatypeProperty rdf:ID="serviceClassification">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="&xsd;#anyURI"/>
</owl:DatatypeProperty>
<!-- Map the Profile to a product Type -->
<owl:DatatypeProperty rdf:ID="serviceProduct">
<rdfs:domain rdf:resource="#Profile"/>
<rdfs:range rdf:resource="&xsd;#anyURI"/>
</owl:DatatypeProperty>
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### -->
<!-- ############ Actor ########### -->
<!-- ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!-- The Actor concept has now migrated to
rdf:resource="ActorDefault.owl"
-->
<!-- ############ ########### ############ ############ ########### -->
<!-- ############ ########### -->
<!-- ############ DEPRECATED ########### -->
<!-- ############ ########### -->
<!-- ############ ########### ############ ############ ########### -->
<!-- Deprecated concepts have now migrated to
rdf:resource="ProfileDeprecatedElements.owl"
-->
</rdf:RDF>