<?xml version="1.0"?>

<!DOCTYPE rdf:RDF [
   <!ENTITY rdf              "http://www.w3.org/1999/02/22-rdf-syntax-ns">
   <!ENTITY rdfs             "http://www.w3.org/2000/01/rdf-schema">
   <!ENTITY owl              "http://www.w3.org/2002/07/owl">
   <!ENTITY sten             "http://www.somewhere#">
   <!ENTITY D2.1             "http://www.somewhere">
   <!ENTITY meta             "http://www.somewhere#">
]>

<rdf:RDF
   xmlns:rdf              ="&rdf;#"
   xmlns:rdfs             ="&rdfs;#"
   xmlns:owl              ="&owl;#"
   xmlns:sten             ="&sten;"
   xmlns:meta             ="&meta;"
>

<!--
&lt;!DOCTYPE html PUBLIC
         "-//W3C//DTD XHTML 1.0 Transitional//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;

&lt;html&gt;

&lt;head&gt;
 &lt;meta http-equiv="content-type" content="text/html; charset=iso-8859-1"/&gt;
 &lt;title&gt;S-TEN D2.1: Information&lt;/title&gt;
 &lt;style type="text/css"&gt;
   .note { color: #808080; }
   .table { font-size: smaller }
   .title { font-size: xx-large }
   p { text-align: justify }
   pre { background: #FFFFE0; }
   p.caption { text-align: center }
 &lt;/style&gt;
&lt;/head&gt;

&lt;body&gt;

&lt;a name="information"/&gt;
&lt;h2&gt;6 Information&lt;/h2&gt;

&lt;a name="what_is_information"/&gt;
&lt;h3&gt;6.1 What is information&lt;/h3&gt;

&lt;a name="information_content_and_information_carrier"/&gt;
&lt;h3&gt;6.1.1 Information content and information carrier&lt;/h3&gt;

&lt;p&gt;A &lt;a href="physical_things.htm#physical_thing"&gt;&lt;b&gt;sten:physical_thing&lt;/b&gt;&lt;/a&gt; can bear a pattern which can be decoded by a
person, by a machine or by a person using a machine. Such a &lt;a href="physical_things.htm#physical_thing"&gt;&lt;b&gt;sten:physical_thing&lt;/b&gt;&lt;/a&gt;
is an &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE 1 An &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;
can be a computer file which is identified by a path on a computer system, or
by a URL on the Internet. A computer file is not usually thought of as "physical",
but:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it exists in time - a computer file is created and subsequently destroyed or deleted;&lt;/li&gt;
&lt;li&gt;it exists in space - a computer file held by a computer or network of computers, which
is located somewhere;&lt;/li&gt;
&lt;li&gt;it is made up of matter - a computer file is destroyed when a computer is destroyed,
in the same way that a book is destroyed when a library is destroyed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An object can be "physical" even if it is made up of matter which cannot be
precisely identified, or which changes from time to time. Consider a
&lt;a href="physical_things.htm#facility"&gt;&lt;b&gt;sten:facility&lt;/b&gt;&lt;/a&gt; which is a pump within a process plant. The pump is used by
the plant operators to move fluids, and is naturally regarded as physical. From
time to time, the installed pump &lt;a href="physical_things.htm#physical_asset"&gt;&lt;b&gt;sten:physical_asset&lt;/b&gt;&lt;/a&gt; will be removed for servicing and
will be replaced by a new pump &lt;a href="physical_things.htm#physical_asset"&gt;&lt;b&gt;sten:physical_asset&lt;/b&gt;&lt;/a&gt;, but the operators will regard
the &lt;a href="physical_things.htm#facility"&gt;&lt;b&gt;sten:facility&lt;/b&gt;&lt;/a&gt; as continuing to exist.&lt;/p&gt;

&lt;p&gt;The Grand Canyon in Arizona is "physical". The matter which forms
the Grand Canyon is uncertain, but clearly its existence depends upon matter. It
can be regarded as a "feature", like a slot in a manufacture part but on a larger
scale. An &lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; is also "physical".&lt;/p&gt;

&lt;p&gt;It can be debated whether a computer file is more like a facility, feature or
activity. The answer may even depend upon the nature of the computer hardware.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 1 The English language printed copy of the
UN "Universal declaration of human rights" possessed by Fred Bloggs is an
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;. This can be decoded by any sighted, literate,
English language speaking person.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 2 The file &lt;a href="http://www.un.org/Overview/rights.html"&gt;&lt;code&gt;http://www.un.org/Overview/rights.html&lt;/code&gt;&lt;/a&gt; is an
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;. This can be decoded by a Web Browser, where "decoding"
is defined as generating a human readable presentation.&lt;/p&gt;

&lt;p&gt;This can be decoded by an
English language speaking person using a Web Browser, where "decoding" is defined as
understanding the intention of UN resolution 217 A (III) of 1948-12-10.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;An &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; can be classified according to the
nature of the response made by a person, machine or person using a machine which
decodes it. A class which consists of all information carriers which produce the same
response is an &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE 2 The class &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; is a subclass of
&lt;b&gt;iso15926-2:class_of_information_representation&lt;/b&gt;.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 3 The class of all information carriers which can lead to
an understanding of the UN "Universal declaration of human rights" is an
&lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;. We can call this class
"UN Universal declaration of human rights document".&lt;/p&gt;

&lt;p&gt;The English language printed copy of the UN "Universal declaration of human rights"
possessed by Fred Bloggs is a menber if this class.&lt;/p&gt;

&lt;p&gt;The file &lt;a href="http://www.un.org/Overview/rights.html"&gt;&lt;code&gt;http://www.un.org/Overview/rights.html&lt;/code&gt;&lt;/a&gt; is a member of this
class. It can be decoded by any English language speaking person using a
web browser.&lt;/p&gt;

&lt;p&gt;The file &lt;a href="http://www.unhchr.ch/udhr/lang/wls.htm"&gt;&lt;code&gt;http://www.unhchr.ch/udhr/lang/wls.htm&lt;/code&gt;&lt;/a&gt; is a member of this
class. It can be decoded by any Welsh (Cymraeg) language speaking person using a
web browser.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 4 The class of all information carriers which can lead to
an understanding of the UN "Univeral declaration of human rights" by a person who only
speaks English is an
&lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;. We can call this class
"UN Universal declaration of human rights document in English".&lt;/p&gt;

&lt;p&gt;The English language printed copy of the UN "Universal declaration of human rights"
possessed by Fred Bloggs is a menber if this class.&lt;/p&gt;

&lt;p&gt;The file &lt;a href="http://www.un.org/Overview/rights.html"&gt;&lt;code&gt;http://www.un.org/Overview/rights.html&lt;/code&gt;&lt;/a&gt; is a member of this
class. It can be decoded by any English language speaking person using a
web browser.&lt;/p&gt;

&lt;p&gt;The file &lt;a href="http://www.unhchr.ch/udhr/lang/eng.htm"&gt;&lt;code&gt;http://www.unhchr.ch/udhr/lang/eng.htm&lt;/code&gt;&lt;/a&gt; is a member of this
class. It can be decoded by any English language speaking person using a
web browser.&lt;/p&gt;
&lt;/div&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 5 The class of all information carriers which reproduce the
UN "Universal declaration of human rights" with the same format as the official record of
the 1948-12-10 General Assembly session is an &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;.
We can call this class
"UN Universal declaration of human rights reproduction of official record".&lt;/p&gt;

&lt;p&gt;The printed copy of the 1948-12-10 UN General Assembly session possessed by the
UK Foreign Office is
a menber if this class. It can be decoded by any sighted person.&lt;/p&gt;

&lt;p&gt;The file &lt;a href="http://daccess-ods.un.org/access.nsf/Get?Open&amp;DS=A/RES/217(III)&amp;Lang=E"&gt;&lt;code&gt;http://daccess-ods.un.org/access.nsf/Get?Open&amp;DS=A/RES/217(III)&amp;Lang=E&lt;/code&gt;&lt;/a&gt; is a member of this
class. It can be decoded by any web browser which supports PDF.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;An &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; can be a class which consists of all copies of
a file.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 6 The class of all copies of
&lt;a href="http://www.un.org/Overview/rights.html"&gt;&lt;code&gt;http://www.un.org/Overview/rights.html&lt;/code&gt;&lt;/a&gt; is an &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;.
We can call this class "Copy of UN Universal declaration of human rights from UN website".&lt;/p&gt;

&lt;p&gt;The file &lt;code&gt;C:\useful_documents\UN_declaration_of_human_rights.html&lt;/code&gt;
on the computer possessed by Fred Bloggs is a member of this class.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;An &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; can be an RDF graph. An
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; which is a member of an RDF graph can be:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a GIF file which contains the graph as graphics;&lt;/li&gt;
&lt;li&gt;a text file which is an XML serialisation of the graph;&lt;/li&gt;
&lt;li&gt;a text file which is an N3 serialisation of the graph.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 7 The RDF graph "Janet loves John" is an &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;.
Three of the members of this class are &lt;a href="#janet_loves_john_fig"&gt;Figure 6&lt;/a&gt;;
the XML serialisation below; and the N3 serialisation below.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;GIF file&lt;/b&gt;:&lt;/p&gt;
&lt;div align="center"&gt;
&lt;a name="janet_loves_john_fig"/&gt;
&lt;img src="../images/janet_loves_john.gif"
     alt="Janet loves John RDF graph"/&gt;
&lt;p class="caption"&gt;&lt;b&gt;Figure 6: Janet loves John RDF graph&lt;/b&gt;&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;b&gt;XML serialisation&lt;/b&gt;:&lt;/p&gt;

&lt;pre&gt;
<rdf:RDF xmlns:my_ontology="urn:my_ontology">
 <owl:Thing rdf:about="urn:people:Janet">
  <my_ontology:loves rdf:about="urn:people:John"/>
 </owl:Thing>
</rdf:RDF>
&lt;/pre&gt;

&lt;p&gt;&lt;b&gt;N3 serialisation&lt;/b&gt;:&lt;/p&gt;

&lt;pre&gt;
urn:people:Janet  urn:my_ontology:loves  urn:people:John .
&lt;/pre&gt;

&lt;/div&gt;

&lt;a name="uri_url_and_urn"/&gt;
&lt;h3&gt;6.1.2 URI, URL and URN&lt;/h3&gt;
&lt;p&gt;A URI can be used to identify anything.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 1 The animal "Babar the elephant" can be given the URI "urn:animal_registry:Babar". This
does not mean that I can download "Babar the elephant" from the Internet. Animal, real or
ficticious cannot be stored in my computer.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;The use of URIs is explained in
&lt;a href="http://www.rfc-editor.org/rfc/rfc3986.txt"&gt;&lt;code&gt;http://www.rfc-editor.org/rfc/rfc3986.txt&lt;/code&gt;&lt;/a&gt;
"Uniform Resource Identifier (URI): Generic Syntax", January 2005. This document says:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;A URI can be further classified as a locator, a name, or both.  The term
"Uniform Resource Locator" (URL) refers to the subset of URIs
that, in addition to identifying a resource, provide a means of locating the resource
by describing its primary access mechanism (e.g., its network "location").&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Hence an &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; that is a resource on the Internet can be
identified by a URL. An object of any other type, including an
&lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;, is identified by
a URI, which is not a URL.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 2 Consider a sensor which is operated by Fred Bloggs and which has
the URN &lt;code&gt;urn:123:456&lt;/code&gt;. This is not useful on its own because
the URN does not tell you where to go to find out more information.&lt;/p&gt;

&lt;p&gt;However, Fred Bloggs can also run a server which provides information about the
sensor with the URL &lt;code&gt;http://www.fred.bloggs.eu/sensors#456&lt;/code&gt;. This is useful
provided that you know that &lt;code&gt;urn:123:456&lt;/code&gt; is operated by Fred Bloggs and
you know the algorithm by which Fred Bloggs has converted the URN into a URL.&lt;/p&gt;

&lt;p&gt;Life becomes easier if Fred Bloggs registers &lt;code&gt;urn:123:456&lt;/code&gt; with a
sensor registry. Information about the sensor in the registry has the URL:&lt;/p&gt;

&lt;p class="caption"&gt;http://www.sensor_registry.eu/sensors/urn:123:456&lt;/p&gt;

&lt;p&gt;The sensor registry can also manage aliases so that the information about the
sensor also has the URL:&lt;/p&gt;

&lt;p class="caption"&gt;http://www.sensor_registry.eu/sensors/http://www.fred.bloggs.eu/sensors#456&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;There is a tradition within RDF to regard a URL as a surrogate for a thing,
so that a reference to a URL is regarded as equivalent to a reference to a thing.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 3 The statement:&lt;/p&gt;

&lt;pre&gt;
http://www.myspace.com/Janet  urn:my_ontology:loves  http://www.myspace.com/John .
&lt;/pre&gt;

&lt;p&gt;is regarded as equivalent to:&lt;/p&gt;

&lt;pre&gt;
urn:people:Janet  urn:my_ontology:loves  urn:people:John .
&lt;/pre&gt;

&lt;p&gt;even though the URLs identify resources which can be accessed over the Internet
rather than people.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;If it is decided not to comply with this tradition, then the URN can be related
to the URL by a &lt;a href="#has_registry_data"&gt;&lt;b&gt;sten:has_registry_data&lt;/b&gt;&lt;/a&gt;
relationship.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 4:&lt;/p&gt;

&lt;pre&gt;
urn:people:Janet  urn:has_registry_data  http://www.myspace.com/Janet .
&lt;/pre&gt;
&lt;/div&gt;

&lt;p&gt;On the other hand, if it is decided to comply with this tradition, then
&lt;a href="#has_registry_data"&gt;&lt;b&gt;sten:has_registry_data&lt;/b&gt;&lt;/a&gt; is the same as
&lt;b&gt;owl:sameAs&lt;/b&gt;.&lt;/p&gt;

&lt;a name="creation_and_use_of_information"/&gt;
&lt;h3&gt;6.1.3 Creation and use of information&lt;/h3&gt;
&lt;p&gt;An &lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; can use and create information. This means that it has
an &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; as an input or output.&lt;/p&gt;

&lt;p&gt;The "provenance" of information is the activity which created it.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE Extracting from the
&lt;a href="observation_and_measurement.htm#human_observation_example"&gt;human observation example&lt;/a&gt; in the section
&lt;a href="observation_and_measurement.htm#observation_and_measurement"&gt;Observation and measurement&lt;/a&gt;, we have:&lt;/p&gt;

&lt;pre&gt;
[ a                sten:observing_activity  ] ;
  sten:gives_result_record
                   http://www.somewhere.com/observations/my_bearing_2007-03-15T16:00 .
&lt;/pre&gt;

&lt;p&gt;The property &lt;a href="observation_and_measurement.htm#gives_result_record"&gt;&lt;b&gt;sten:gives_result_record&lt;/b&gt;&lt;/a&gt; is a specialisation of
&lt;a href="#has_output_record"&gt;&lt;b&gt;sten:has_output_record&lt;/b&gt;&lt;/a&gt;, which is a specialisation of
&lt;a href="physical_things.htm#has_output"&gt;&lt;b&gt;sten:has_output&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is possible to record the output content as a named graph, as follows:&lt;/p&gt;

&lt;pre&gt;
[ a                sten:observing_activity  ] ;
  sten:gives_result_record
        { [ a                     sten:physical_object_at_instant ]
            sten:temporal_part_of :my_bearing ;
            sten:at_time          [ sten:utc_iso8601 "2007-03-15T16:00" ] ;
            a                     sten:hot
        } .
&lt;/pre&gt;
&lt;/div&gt;

&lt;a name="information_about_things"/&gt;
&lt;h3&gt;6.1.4 Information about things&lt;/h3&gt;
&lt;p&gt;A &lt;b&gt;owl:Thing&lt;/b&gt; can be associated with an
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; which describes it.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 1 The information that "Janet loves John" can be regarded as information
about either Janet or John. If this information is held in
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;
&lt;code&gt;http://www.somewhere.org/gossip/janet_and_john&lt;/code&gt;, then the association
between the information and the people can be recorded as follows:&lt;/p&gt;

&lt;pre&gt;
http://www.somewhere.org/gossip/janet_and_john
         sten:is_about urn:people:Janet ;
         sten:is_about urn:people:John .
&lt;/pre&gt;

&lt;p&gt;or looked at in the other direction:&lt;/p&gt;
&lt;pre&gt;
urn:people:Janet
  sten:is_described by http://www.somewhere.org/gossip/janet_and_john .

urn:people:John
  sten:is_described by http://www.somewhere.org/gossip/janet_and_john .
&lt;/pre&gt;
&lt;/div&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 2 The BioPathways Consortium provides a
&lt;a href="http://lsid.biopathways.org/resolver/"&gt;Life Science Identifier Service&lt;/a&gt;
which gives information about objects in the Life Sciences. The consortium says:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The World-Wide Web provides a globally distributed communication framework
that is essential for almost all scientific collaboration, including
bioinformatics. However, several limits and inadequacies have become
apparent, one of which is the inability to programmatically identify locally
named objects that may be widely distributed over the network. This
shortcoming limits our ability to integrate multiple knowledgebases, each of
which gives partial information of a shared domain, as is commonly seen in
bioinformatics. The Life Science Identifier (LSID) and LSID Resolution System
(LSRS) provide simple and elegant solutions to this problem, based on the
extension of existing internet technologies. LSID and LSRS are consistent
with next-generation semantic web and semantic grid approaches.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A Life Science Identifier is a URN, such as
&lt;code&gt;urn:lsid:gdb.org:GenomicSegment:GDB132938&lt;/code&gt;. Information about this object,
provided by the Life Science Identifier Service has the URL
&lt;a href="http://lsid.biopathways.org/resolver/urn:lsid:gdb.org:GenomicSegment:GDB132938"&gt;&lt;code&gt;http://lsid.biopathways.org/resolver/urn:lsid:gdb.org:GenomicSegment:GDB132938&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A user of the Life Science Identifier Service can either access this URL directly,
or enter the URN as data in a field of
&lt;a href="http://lsid.biopathways.org/resolver/"&gt;&lt;code&gt;http://lsid.biopathways.org/resolver/&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The functionality of the Life Science Identifier Service can be recorded by
statements of the form:&lt;/p&gt;

&lt;pre&gt;
urn:lsid:gdb.org:GenomicSegment:GDB132938
  sten:is_described_by
     http://lsid.biopathways.org/resolver/urn:lsid:gdb.org:GenomicSegment:GDB132938 .
&lt;/pre&gt;

&lt;p&gt;&lt;font size="-1"&gt;ACKNOWLEDGEMENT David Leal is indebted to David Price of Eurostep Limited
for drawing his attention to this example.&lt;/font&gt;&lt;/p&gt;
&lt;/div&gt;

&lt;a name="information_and_standard"/&gt;
&lt;h3&gt;6.1.5 Information and standard&lt;/h3&gt;
&lt;p&gt;There are related concepts as follows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;
that is an ISO standard. This object is assigned a URN by ISO in
accordance with
&lt;a href="http://www.ietf.org/internet-drafts/draft-goodwin-iso-urn-01.txt"&gt;J. Goodwin, "A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)"&lt;/a&gt;.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 1 The standard ISO 10303-214 edition 2 (2003) is assigned the URN:&lt;/p&gt;

&lt;p class="caption"&gt;&lt;code&gt;urn:iso:std:iso:10303:-214:ed-2&lt;/code&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;/li&gt;

&lt;li&gt;&lt;p&gt;An &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; that
complies with a standard.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 2 The &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;
"my_data" complies with ISO 10303-214:2003. This is recorded as follows:&lt;/p&gt;

&lt;pre&gt;
:my_data  sten:complies_with  urn:iso:std:iso:10303:-214:ed-2  .
&lt;/pre&gt;
&lt;/div&gt;
&lt;/li&gt;

&lt;li&gt;&lt;p&gt;An &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; which
holds &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; that
complies with a standard. As described in
&lt;a href="#information_content_and_information_carrier"&gt;Information content and information carrier&lt;/a&gt;,
the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; is a member of
the &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;div class="note"&gt;
&lt;p&gt;EXAMPLE 3 The &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;
with URL &lt;code&gt;http://www.fred.bloggs.eu/design/system_789.stp&lt;/code&gt;
complies with ISO 10303-214:2003. This is recorded as follows:&lt;/p&gt;

&lt;pre&gt;
http://www.fred.bloggs.eu/design/system_789.stp
                       a  [ sten:complies_with  urn:iso:std:iso:10303:-214:ed-2 ] .
&lt;/pre&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;a name="_example_information_about_a_sensor"/&gt;
&lt;h3&gt;6.1.6 Example information about a sensor&lt;/h3&gt;
&lt;p&gt;Consider a sensor with URN &lt;code&gt;urn:123:456&lt;/code&gt;.  A sensor registry can
provide the resource &lt;code&gt;http://www.sensor_registry.eu/sensors/urn:123:456&lt;/code&gt;
which is an HTML page as follows:&lt;/p&gt;

&lt;table border="1" width="100%"&gt;
 &lt;tr&gt;
  &lt;td width="100%"&gt;
   &lt;table border="1" width="100%"&gt;
    &lt;tr&gt;
     &lt;td rowspan="3" width="15%"&gt;sensor&lt;/td&gt;
     &lt;td width="15%"&gt;id&lt;/td&gt;
     &lt;td width="70%"&gt;urn:123:456&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
     &lt;td width="15%"&gt;registry data&lt;/td&gt;
     &lt;td width="70%" &gt;&lt;font color="blue"&gt;http://www.fred.bloggs.eu/sensors#456&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
     &lt;td width="15%"&gt;registry data&lt;/td&gt;
     &lt;td width="70%" &gt;&lt;font color="blue"&gt;http://www.sensor_registry.eu/sensors/urn:123:456&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
   &lt;/table&gt;
  &lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
  &lt;td width="100%"&gt;
   &lt;table border="1" width="100%"&gt;
    &lt;tr&gt;
     &lt;td width="15%"&gt;design data&lt;/td&gt;
     &lt;td width="15%"&gt;ISO 10303-214&lt;/td&gt;
     &lt;td width="70%"&gt;&lt;font color="blue"&gt;http://www.fred.bloggs.eu/design/system_789.stp&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
   &lt;/table&gt;
  &lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
  &lt;td width="100%"&gt;
   &lt;table border="1" width="100%"&gt;
    &lt;tr&gt;
     &lt;td rowspan="3" width="15%"&gt;measurements&lt;/td&gt;
     &lt;td width="15%"&gt;2007-01&lt;/td&gt;
     &lt;td width="70%"&gt;&lt;font color="blue"&gt;http://www.fred.bloggs.eu/measurements/2007-01&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
     &lt;td width="15%"&gt;2007-02&lt;/td&gt;
     &lt;td width="70%"&gt;&lt;font color="blue"&gt;http://www.fred.bloggs.eu/measurements/2007-02&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
     &lt;td width="15%"&gt;2007-03&lt;/td&gt;
     &lt;td width="70%"&gt;&lt;font color="blue"&gt;http://www.fred.bloggs.eu/measurements/2007-03&lt;/font&gt;&lt;/td&gt;
    &lt;/tr&gt;
   &lt;/table&gt;
  &lt;/td&gt;
 &lt;/tr&gt;
&lt;/table&gt;

&lt;p&gt;This is person readable information. The presentation could be neater, with
hypertext links which do not show the actual URLs.  For computer processing, an
OWL equivalent is required, which is as follows:&lt;/p&gt;

&lt;pre&gt;
urn:123;456  a                       sten:sensor ;
             sten:has_registry_data  http://www.fred.bloggs.eu/sensors#456 ;
             sten:has_registry_data  http://www.sensor_registry.eu/sensors/urn:123:456 .

urn:123;456  sten:has_design_data    http://www.fred.bloggs.eu/design/system_789.stp .

http://www.fred.bloggs.eu/design/system_789.stp
                       a  [ sten:complies_with  urn:iso:std:iso:10303:-214:ed-2 ] .

[ sten:temporal_part_of urn:123;456 ]
             sten:has_result_record  http://www.fred.bloggs.eu/measurements/2007-01 .

[ sten:temporal_part_of urn:123;456 ]
             sten:has_result_record  http://www.fred.bloggs.eu/measurements/2007-02 .

[ sten:temporal_part_of urn:123;456 ]
             sten:has_result_record  http://www.fred.bloggs.eu/measurements/2007-03 .
&lt;/pre&gt;

&lt;p&gt;This OWL is formally equivalent to the HTML, but a person would guess that
&lt;code&gt;http://www.fred.bloggs.eu/measurements/2007-01&lt;/code&gt; applies to month 2006-01.
So that software does not have to access the resource to discover this, the
information can be put in the OWL as follows:&lt;/p&gt;

&lt;pre&gt;
[ sten:temporal_part_of urn:123;456 ;
  sten:during [ iso8601:calendar_month "2007-01" ] ]
             sten:has_result_record  http://www.fred.bloggs.eu/measurements/2007-01 .

[ sten:temporal_part_of urn:123;456 ;
  sten:during [ iso8601:calendar_month "2007-02" ] ]
             sten:has_result_record  http://www.fred.bloggs.eu/measurements/2007-02 .

[ sten:temporal_part_of urn:123;456 ;
  sten:during [ iso8601:calendar_month "2007-03" ] ]
             sten:has_result_record  http://www.fred.bloggs.eu/measurements/2007-03 .
&lt;/pre&gt;

&lt;p&gt;The resources identified by the URLs can be HTML files with the corresponding
OWL file specified by a link in the <head> element as follows:&lt;/p&gt;

&lt;pre&gt;
<head>
 <title>Sensor 456</title>
 <link rel="meta" type="application/rdf+n3"
   href="http://http://www.sensor_registry.eu/sensors/urn:123:456/n3"/>
</head>
&lt;/pre&gt;

&lt;a name="information_ontology"/&gt;
&lt;h3&gt;6.2 Information ontology&lt;/h3&gt;

&lt;a name="information_carrier"/&gt;
&lt;h3&gt;6.2.1 information_carrier&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;a href="physical_things.htm#physical_thing"&gt;&lt;b&gt;sten:physical_thing&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;it bears a pattern which can be decoded by a person, by a machine, or by a person
using a machine.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE An object identified by a URL must be an &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:Class rdf:about="&sten;#information_carrier">
 <rdfs:subClassOf rdf:resource="&sten;#physical_object"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#information_carrier"/>
</owl:Class>
<!--
&lt;/pre&gt;

&lt;p&gt;An &lt;b&gt;rdfg:graph&lt;/b&gt; is an
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:Class rdf:about="&amp;rdfg;graph">
 <rdfs:subClassOf rdf:resource="&sten;information_carrier"/>
</owl:Class>
<!--
&lt;/pre&gt;

&lt;a name="information_content"/&gt;
&lt;h3&gt;6.2.2 information_content&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;owl:Class&lt;/b&gt;;&lt;/li&gt;
&lt;li&gt;it consists of each member of &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; which produces a
particlar class of response when decoded by a person, machine, or person using a machine.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:Class rdf:about="&sten;information_content">
 <rdfs:subClassOf rdf:resource="&amp;owl;Class"/>
 <rdfs:subClassOf>
  <owl:Restriction>
   <owl:onProperty rdf:resource="&amp;rdfs;subClassOf"/>
   <owl:someValuesFrom>
    <owl:Class>
     <owl:oneOf rdf:parseType="Collection">
      <owl:Class rdf:resource="&sten;information_carrier"/>
     </owl:oneOf>
    </owl:Class>
   </owl:someValuesFrom>
  </owl:Restriction>
 </rdfs:subClassOf>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#information_content"/>
</owl:Class>
<!--
&lt;/pre&gt;

&lt;a name="has_output_record"/&gt;
&lt;h3&gt;6.2.3 has_output_record&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#has_output_record"&gt;&lt;b&gt;sten:has_output_record&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:partial_function&lt;/b&gt; between
&lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; and &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; carries
the information produced by the activity.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE An &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; which
has an &lt;a href="#has_input_record"&gt;&lt;b&gt;sten:has_input_record&lt;/b&gt;&lt;/a&gt; relationship can
also have a &lt;a href="physical_things.htm#has_role_player"&gt;&lt;b&gt;sten:has_role_player&lt;/b&gt;&lt;/a&gt;
relationship.&lt;/p&gt;

&lt;p&gt;This will be the case if the
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; is an
ink on paper document or a computer file, because in either case the input is a
&lt;a href="physical_things.htm#persistent_object"&gt;&lt;b&gt;sten:persistent_object&lt;/b&gt;&lt;/a&gt;
which is present during the
&lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;has_output_record">
 <rdfs:domain rdf:resource="&sten;activity"/>
 <rdfs:range rdf:resource="&sten;information_carrier"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_output_record"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="record_produced_by"/&gt;
&lt;h3&gt;6.2.4 record_produced_by&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#record_produced_by"&gt;&lt;b&gt;sten:record_produced_by&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:function&lt;/b&gt; between
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; and &lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; produced the information.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:FunctionalProperty rdf:about="&sten;record_produced_by">
 <rdfs:domain rdf:resource="&sten;information_carrier"/>
 <rdfs:range rdf:resource="&sten;activity"/>
 <owl:inverseOf rdf:resource="&sten;has_output_record"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#record_produced_by"/>
</owl:FunctionalProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_input_record"/&gt;
&lt;h3&gt;6.2.5 has_input_record&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#has_input_record"&gt;&lt;b&gt;sten:has_input_record&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:partial_function&lt;/b&gt; between
&lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; and &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; carries
the information used by the activity.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE An &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; which
has an &lt;a href="#has_input_record"&gt;&lt;b&gt;sten:has_input_record&lt;/b&gt;&lt;/a&gt; relationship can
also have a &lt;a href="physical_things.htm#has_role_player"&gt;&lt;b&gt;sten:has_role_player&lt;/b&gt;&lt;/a&gt;
relationship.&lt;/p&gt;

&lt;p&gt;This will be the case if the
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; is an
ink on paper document or a computer file, because in either case the input is a
&lt;a href="physical_things.htm#persistent_object"&gt;&lt;b&gt;sten:persistent_object&lt;/b&gt;&lt;/a&gt;
which is present during the
&lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;has_input_record">
 <rdfs:domain rdf:resource="&sten;activity"/>
 <rdfs:range rdf:resource="&sten;information_carrier"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_input_record"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="record_used_by"/&gt;
&lt;h3&gt;6.2.6 record_used_by&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#record_used_by"&gt;&lt;b&gt;sten:record_used_by&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:mapping&lt;/b&gt; between
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; and &lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; used the information.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;record_used_by">
 <rdfs:domain rdf:resource="&sten;information_carrier"/>
 <rdfs:range rdf:resource="&sten;activity"/>
 <owl:inverseOf rdf:resource="&sten;has_input_record"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#record_used_by"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_content"/&gt;
&lt;h3&gt;6.2.7 has_content&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#has_content"&gt;&lt;b&gt;sten:has_content&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:multivalued_function&lt;/b&gt; between
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; and &lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; bears the
&lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;has_content">
 <rdfs:domain rdf:resource="&sten;information_carrier"/>
 <rdfs:range rdf:resource="&sten;information_content"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_content"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_content_literal"/&gt;
&lt;h3&gt;6.2.8 has_content_literal&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#has_content_literal"&gt;&lt;b&gt;sten:has_content_literal&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:multivalued_function&lt;/b&gt; between
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; and &lt;b&gt;rdfs:Literal&lt;/b&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; bears the
&lt;b&gt;rdfs:Literal&lt;/b&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:DatatypeProperty rdf:about="&sten;has_content">
 <rdfs:domain rdf:resource="&sten;information_carrier"/>
 <rdfs:range rdf:resource="&sten;information_content"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_content_literal"/>
</owl:DatatypeProperty>
<!--
&lt;/pre&gt;

&lt;a name="is_about"/&gt;
&lt;h3&gt;6.2.9 is_about&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#is_about"&gt;&lt;b&gt;sten:is_about&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:multivalued_function&lt;/b&gt; between
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; and &lt;b&gt;owl:Thing&lt;/b&gt;;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; bears information about the thing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;is_about">
 <rdfs:domain rdf:resource="&sten;information_carrier"/>
 <rdfs:range rdf:resource="&amp;owl;Thing"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#is_about"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="is_described_by"/&gt;
&lt;h3&gt;6.2.10 is_described_by&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#is_described_by"&gt;&lt;b&gt;sten:is_described_by&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:mapping&lt;/b&gt; between
&lt;b&gt;owl:Thing&lt;/b&gt; and &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the thing is described by the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;is_described_by">
 <rdfs:domain rdf:resource="&amp;owl;Thing"/>
 <rdfs:range rdf:resource="&sten;information_carrier"/>
 <owl:inverseOf rdf:resource="&sten;is_about"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#is_described_by"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="is_registry_data_for"/&gt;
&lt;h3&gt;6.2.11 is_registry_data_for&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#is_registry_data_for"&gt;&lt;b&gt;sten:is_registry_data_for&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is an &lt;a href="#is_about"&gt;&lt;b&gt;sten:is_about&lt;/b&gt;&lt;/a&gt; relationship;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; contains
registry data about the thing, and can be regarded as a surrogate for it.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE This relationship can associate a thing identified by a URN and a resource
with a location on the Internet identified by a URL.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;is_registry_data_for">
 <rdfs:subPropertyOf rdf:resource="&sten;is_about"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#is_registry_data_for"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_registry_data"/&gt;
&lt;h3&gt;6.2.12 has_registry_data&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#has_registry_data"&gt;&lt;b&gt;sten:has_registry_data&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is an &lt;a href="#is_described_by"&gt;&lt;b&gt;sten:is_described_by&lt;/b&gt;&lt;/a&gt; relationship;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; contains
registry data about the thing, and can be regarded as a surrogate for it.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE This relationship can associate a thing identified by a URN and a resource
with a location on the Internet identified by a URL.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;has_registry_data">
 <rdfs:subPropertyOf rdf:resource="&sten;is_described_by"/>
 <owl:inverseOf rdf:resource="&sten;is_registry_data_for"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_registry_data"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_design_data"/&gt;
&lt;h3&gt;6.2.13 has_design_data&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#has_design_data"&gt;&lt;b&gt;sten:has_design_data&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is an &lt;a href="#is_described_by"&gt;&lt;b&gt;sten:is_described_by&lt;/b&gt;&lt;/a&gt; relationship;&lt;/li&gt;
&lt;li&gt;the &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt; contains
design data about the thing.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="note"&gt;
&lt;p&gt;NOTE An &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;
can contain design information about more than one thing.&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;has_design_data">
 <rdfs:subPropertyOf rdf:resource="&sten;is_described_by"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_design_data"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="complies_with"/&gt;
&lt;h3&gt;6.2.14 complies_with&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#complies_with"&gt;&lt;b&gt;sten:complies_with&lt;/b&gt;&lt;/a&gt; relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is an &lt;b&gt;basics:mapping&lt;/b&gt; relationship from
&lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt; to
&lt;a href="#information_content"&gt;&lt;b&gt;sten:information_content&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;it specifies that a member of the domain complies with a standard.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:ObjectProperty rdf:about="&sten;complies_with">
 <rdfs:domain rdf:resource="&sten;information_content"/>
 <rdfs:range rdf:resource="&sten;information_content"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#complies_with"/>
</owl:ObjectProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_set_of_input_records"/&gt;
&lt;h3&gt;6.2.15 has_set_of_input_records&lt;/h3&gt;
&lt;p&gt;An object is an
&lt;a href="#has_set_of_input_records"&gt;&lt;b&gt;sten:has_set_of_input_records&lt;/b&gt;&lt;/a&gt;
relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:function&lt;/b&gt; between
&lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; and
&lt;a href="#set_of_information_carrier"&gt;&lt;b&gt;sten:set_of_information_carrier&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the
&lt;a href="#set_of_information_carrier"&gt;&lt;b&gt;sten:set_of_information_carrier&lt;/b&gt;&lt;/a&gt;
contains each &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;
with a &lt;a href="#has_input_record"&gt;&lt;b&gt;sten:has_input_record&lt;/b&gt;&lt;/a&gt;
relationship.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:FunctionalProperty rdf:about="&sten;has_set_of_input_records">
 <rdfs:domain rdf:resource="&sten;activity"/>
 <rdfs:range rdf:resource="&sten;set_of_information_carrier"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_set_of_input_records"/>
</owl:FunctionalProperty>
<!--
&lt;/pre&gt;

&lt;a name="has_set_of_output_records"/&gt;
&lt;h3&gt;6.2.16 has_set_of_output_records&lt;/h3&gt;
&lt;p&gt;An object is an
&lt;a href="#has_set_of_output_records"&gt;&lt;b&gt;sten:has_set_of_output_records&lt;/b&gt;&lt;/a&gt;
relationship if and only if:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it is a &lt;b&gt;basics:function&lt;/b&gt; between
&lt;a href="physical_things.htm#activity"&gt;&lt;b&gt;sten:activity&lt;/b&gt;&lt;/a&gt; and
&lt;a href="#set_of_information_carrier"&gt;&lt;b&gt;sten:set_of_information_carrier&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;the
&lt;a href="#set_of_information_carrier"&gt;&lt;b&gt;sten:set_of_information_carrier&lt;/b&gt;&lt;/a&gt;
contains each &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;
with a &lt;a href="#has_output_record"&gt;&lt;b&gt;sten:has_output_record&lt;/b&gt;&lt;/a&gt;
relationship.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:FunctionalProperty rdf:about="&sten;has_set_of_output_records">
 <rdfs:domain rdf:resource="&sten;activity"/>
 <rdfs:range rdf:resource="&sten;set_of_information_carrier"/>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#has_set_of_output_records"/>
</owl:FunctionalProperty>
<!--
&lt;/pre&gt;

&lt;a name="set_of_information_carrier"/&gt;
&lt;h3&gt;6.2.17 set_of_information_carrier&lt;/h3&gt;
&lt;p&gt;An object is an
&lt;a href="#set_of_information_carrier"&gt;&lt;b&gt;sten:set_of_information_carrier&lt;/b&gt;&lt;/a&gt;
it is the powerset of
&lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:Class rdf:about="&sten;set_of_information_carrier">
 <owl:equivalentClass>
  <owl:Restriction>
   <owl:onProperty rdf:resource="&amp;rdfs:subClassOf"/>
   <owl:someValuesFrom>
    <Class>
     <owl:oneOf rdf:parseType="Collection">
      <owl:Class rdf:about="&sten;information_carrier"/>
     </owl:oneOf>
    </Class>
   </owl:someValuesFrom>
  </owl:Restriction>
 </owl:equivalentClass>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#set_of_information_carriers"/>
</owl:Class>
<!--
&lt;/pre&gt;

&lt;a name="signal"/&gt;
&lt;h3&gt;6.2.18 signal&lt;/h3&gt;
&lt;p&gt;An object is a &lt;a href="#signal"&gt;&lt;b&gt;sten:signal&lt;/b&gt;&lt;/a&gt; if and only if:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;it is an &lt;a href="#information_carrier"&gt;&lt;b&gt;sten:information_carrier&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;it is not a &lt;a href="physical_things.htm#persistent_object"&gt;&lt;b&gt;sten:persistent_object&lt;/b&gt;&lt;/a&gt;;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;OWL specification:&lt;/u&gt;&lt;/p&gt;
&lt;pre&gt;
-->
<owl:Class rdf:about="&sten;signal">
 <owl:equivalentClass>
  <owl:Class>
   <owl:intersectionOf rdf:parseType="Collection">
    <owl:Class rdf:about="&sten;information_carrier"/>
    <owl:Class>
     <owl:complementOf rdf:about="&sten;persistent_object"/>
    </owl:Class>
   </owl:intersectionOf>
  </owl:Class>
 </owl:equivalentClass>
 <meta:defined_by rdf:resource="&D2.1;/information.htm#signal"/>
</owl:Class>
<!--
&lt;/pre&gt;

&lt;/body&gt;
&lt;/html&gt;
-->

</rdf:RDF>
