OWL-S is a OWL-based Web service ontology, which supplies Web service providers with a core set of markup language constructs for describing the properties and capabilities of their Web services in unambiguous, computer-intepretable form. OWL-S markup of Web services will facilitate the automation of Web service tasks, including automated Web service discovery, execution, composition and interoperation. Following the layered approach to markup language development, the current version of OWL-S builds on the Ontology Web Language (OWL) Candidate Recommendation produced by theWeb-Ontology Working Group at the World Wide Web Consortium.
This page contains a version of the OWL-S language developed by a group of Semantic Web researchers (listed below). We encourage feedback from interested parties through the [email protected] email list.
Previous releases of this language were known as DAML-S, and were built upon DAML+OIL (the predecessor of OWL).
Note also that the focus of this release is on a language for use in describing Web services. Related matters such as software components, tools, use cases, and architectural considerations are not covered here in detail. However, many requirements in these areas are being considered in developing this language, and as the scope of this working group expands, will be made more explicit. Some of these considerations are already described in related publications listed at http://www.daml.org/services/.
Original 1.0 (includes some OWL-Full elements) | Updated (OWL-DL-compliant) |
Service.owl | Service.owl |
Profile.owl | Profile.owl |
Process.owl | Process.owl |
Grounding.owl | Grounding.owl |
Here are several files related to Profile.daml/owl. They each contain declarations that previously were included within Profile.daml/owl. (Note: this minor reorganization of the Profile material was done after the release of 0.9 Beta. See the Status page for further details.
Included here are simple ontologies of time and of resources. The time ontology is used (currently in very limited ways) in process specification. The resources ontology is currently unused, but is planned for future use in specification of profiles and processes.