The Concepts of WSMO - Enabling Semantic Web Services: The Web Service Modeling Ontology - page 75

• Coverage. The extent or scope of the content of the element. Typically,

dc:coverage will a include spatial location (a place name or geographic
coordinates), a temporal period (a period label, date, or date range), or a
jurisdiction (such as a named administrative entity). 3

• Creator. The entity primarily responsible for creating the content of the

element. Examples of dc:creator include a person, an organization, and a
Web service. The Dublin Core specification recommends that, typically,
the name of a dc:creator should be used to indicate the entity.

• Date. The date of an event in the life cycle of the element. Typically,

dc:date will be associated with the creation or availability of the element. 4

• Description. An account of the content of the element. Examples of

dc:description include, but are not limited to, an abstract, a table of
contents, a reference to a graphical representation of the content and a
free-text account of the content.

• Financial. This represents the cost-related and charging-related properties

of a Web service [105]. This property is a complex property, which includes
charging styles (e.g. per request or delivery, per unit of measure, granular-
ity, etc.), aspects of settlement such as the settlement model (transactional
vs. rental) and a settlement contract, payment obligations, and payment
instruments.

• Format. The physical or digital manifestation of the element. Typically,

dc:format may include the media type or dimensions of the element. The
format may be used to identify the software, hardware, or other equipment
needed to display or operate the element. Examples of dimensions include
size and duration.

• Identifier. An unambiguous reference to the element within a given con-

text. Recommended best practice is to identify the element by means of a
string or number conforming to a formal identification system. In Dublin
Core, formal identification systems include, but are not limited to, the
Uniform Resource Identifier (URI) (including the Uniform Resource Lo-
cator (URL)), the Digital Object Identifier (DOI), and the International
Standard Book Number (ISBN).

• Language. The language of the intellectual content of the element. The

language tags are defined in ISO Standard 639 [43], for example “en-GB”.
In addition, the logical language used to express the content should be
mentioned; for example this could be OWL.

3 For more complex applications, consideration should be given to using an en-
coding scheme that supports an appropriate specification of information, such as
DCMI Period, DCMI Box, or DCMI Point.
4 We recommend using an encoding defined in ISO Standard 8601:2000 [44] for date
and time notation. A short introduction to the standard can be found at http:
//www.cl.cam.ac.uk/ ~ mgk25/iso-time.html . This standard is also used by the
XML Schema definition (YYYY-MM-DD) [16], and thus one is automatically
compliant with XML Schema too.