date: $Date: 2008-07-23 09:43:30 $ author: Jos de Bruijn, Reto Krummenacher, Ioan Toma this document provides an XML Schema for the XML version of the WSML syntax The syntax presented in this document can be used for all WSML variants. The WSML variant is identified through the 'variant' attribute of the root element 'wsml'. A modular approach has been chosen when creating this schema. This schema contains the conceptual syntax. Separate schemas have been developed for the WSML identifiers and for the WSML logical expressions. These schemas are therefore included in this schema. The element 'wsml' is the preferred root element for any WSML specification. It allows the user to explicity specify, through the 'variant' attribute, which WSML variant is used. If the WSML variant has not been specified, the application has to "guess" the variant and in the worst case, WSML-Full will be assumed. This element is used for indicating which WSML, RDFS, and OWL DL ontologies to import. Importing ontologies is the most basic (and inflexible) modularization mechanism. The result of the import is merely the union of the axioms in the importing and the imported ontology. Mediators can be used to mediate between any top-level WSMO elements, i.e. ontologies, goals, and web services. The most frequent use of mediators is to resolve heterogeneity between ontologies. Thus, mediators provide a more flexible way for modularization of ontologies. A list of shared variables for the capability A pre-condition is an axiom describing the state of the information space before executing the web service. An assumption is an axiom describing the state of the world before executing the web service. A post-condition is an axiom describing the state of the information space after executing the web service. An effect is an axiom describing the state of the world after executing the web service. A reference to an orchestration description. A goal specification. Any element can be used inside the annotations. The recommended set of annotations is the set of elements offered by Dublin Core. WSML further defines one element, named 'version' and 'owner' A goal, web service, mediator, capability and interface are elements that can have one or many non-functional properties. A web service specification. A web service capability specification. A web service interface specification. A web service choreography specification. A web service statesignature specification. A web service mode specification. A web service transition rules specification. A web service transition rule specification. A rule keyword can be: if, then, endif, forall, with, do, endforall, choose or endchoose A condition which can appear in a if transition rule. A piped rule specification. Pipe | used in a piped rule specification A fact specification. The element ooMediator is used for both declaration of ooMediators and reference to existing ooMediators. In case no elements are nested inside the ooMediator, the element is interpreted as a reference to the ooMediator indicated with the attribute 'name'. If elements are nested inside the ooMediator, it is interpreted as a specification of a new ooMediator whose identifier is specified in the attribute 'name'. A ggMediator specification. A wgMediator specification. A wwMediator specification. An ontology specification. An axiom reference or specification. In case no elements are nested inside the axiom, it is merely a reference to an axiom definition. Otherwise, it is an axiom specification, consisting of a number of annotations and the actual logical expression, contained in the definedBy keyword. An logical definition specification consisting of a set of logical expressions previously followed by the definedBy keyword. A concept specification or reference. In case no elements are nested inside the concept, it is a reference to the concept identified by the name. Otherwise, it is a concept specification. A concept can have zero or more attributes. The type of the attribute can be inferring or constraining. A constraining attribute (corresponding to 'ofType') is used to check the type of parameter values; an inferring parameter (corresponding to 'impliesType') is used to derive the type of attribute values. By default an attribute is constraining. Furthermore, an attribute can be symmetric, transitive, reflexive or the inverse of another attribute. Finally, it is possible to specify the minimal and maximal cardinality of an attribute. By default the minimal cardinality is 0 and the maximal cardinality is n (i.e. not restricted). A relation specification or reference. In case no elements are nested inside the relation, it is a reference to the relation identified by the name. Otherwise, it is a relation specification. The ordered list of parameter types An instance can be member of zero or more concepts. Furthermore, zero or more attribute values can be associated with this particular instance. The value of an attribute is either the identifier of another WSML element or a literal. An instance of a relation corresponds with a tuple in the extension of the relation. The values of the parameters are explicitly specified. In case the relation does not have named parameters, the parameter values only have a value and not a name. The order of the XML elements then corresponds with the order of the arguments of the relation.