Background
The W3C Web Ontology Language (OWL) is playing an important role in an increasing number and range of applications, and is the focus of research into tools, reasoning techniques, formal foundations and language extensions. This level of experience with OWL means that the community is now in a good position to discuss how OWL be applied, adapted and extended to fulfil current and future application demands. In particular, the initial design of OWL was conservative in several ways: it excluded constructs that did not have considerable
The Web Ontology Language (OWL) is a language for defining and instantiating Web ontologies.[1] An OWL ontology may include descriptions of classes, along with their related properties and instances. OWL is designed for use by applications that need to process the content of information instead of just presenting information to humans. It facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL is based on earlier languages
The Web Ontology Language (OWL) is a language for defining and instantiating Web ontologies.[1] An OWL ontology may include descriptions of classes, along with their related properties and instances. OWL is designed for use by applications that need to process the content of information instead of just presenting information to humans. It facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL is based on earlier languages
As the set of available Web Services expands, it becomes increasingly important to have automated tools to help identify services that match a requester's requirements. Finding suitable Web services depends on the facilities available for service providers to describe the capabilities of their services and for service requesters to describe their requirements in an unambiguous and ideally, machine-interpretable form. Adding semantics to represent the requirements and capabilities of Web services is essential for achieving this unambiguity and
RSS/XML