Information Technology Reference
In-Depth Information
dc:source in whole or in part. Recommended best practice is to identify
the referenced element by means of a string or number conforming to a
formal identification system.
•
Subject.
A topic of the content of the element. Typically, dc:subject will be
expressed as keywords, key phrases, or classification codes that describe a
topic of the element. Recommended best practice is to select a value from
a controlled vocabulary or a formal classification scheme.
•
Title.
The name given to an element. Typically, dc:title will be a name by
which the element is formally known.
•
Transactional.
This represents the transactional properties of the Web
service.
•
Trust.
This represents the trustworthiness of a Web service or an ontology.
•
Type.
The nature or genre of the content of the element. The dc:type
includes terms describing general categories, functions, genres, or aggre-
gation levels of content.
•
Version.
As many properties of an element might change over time, an
identifier of the element at a certain moment in time is needed.
6.6 Summary
In this chapter we have exhaustively introduced all elements relevant to the
WSMO framework. We have done this in a semiformal fashion using the UML-
based Meta-Object Facility. By separating the model from the language used
to implement it, this provides significantly more freedom then other competing
approaches (see Chapter 8).
Among the guiding principles we have presented Web compliance, which
will be very prominent in the next chapter, which introduces the concrete
language for WSML. Aspects of the Semantic Web are represented mainly
by introducing an epistemological model for ontologies and by using elements
of this model for refining other aspects such as capabilities through logical
expressions.
We have not yet made the relationship between the WSMO model and
Web service technology in the sense of WSDL explicit. The reason is that (1)
WSMO, used as a conceptual model to describe services, is independent of
the concrete technology used to implement them, and (2) this relationship
(grounding) is, in our context, only relevant to actual Web service execution
and not essential for an overall understanding. Information about grounding
can be found in Section 9.5.
Search WWH ::
Custom Search