<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>Draft: Identity Schema Element Metadata: Using Existing Specifications</title>
<meta http-equiv="Expires" content="Fri, 07 Sep 2007 00:51:09 +0000">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="Identity Schema Element Metadata: Using Existing Specifications">
<meta name="keywords" content="schema, identity, OpenID, InfoCard, SAML, schema, LDAP">
<meta name="generator" content="xml2rfc v1.32 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Draft</td><td class="header">M. Wahl</td></tr>
<tr><td class="header"> </td><td class="header">Informed Control Inc.</td></tr>
<tr><td class="header"> </td><td class="header">September 6, 2007</td></tr>
</table></td></tr></table>
<h1><br />Identity Schema Element Metadata: Using Existing Specifications</h1>
<h3>Abstract</h3>
<p>
This document specifies how existing RDF predicate definitions can be used for describing schema elements such as claim types and attribute types in an identity metasystem.
</p><a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Introduction<br />
<a href="#anchor2">2.</a>
Recommended predicates<br />
<a href="#anchor3">2.1.</a>
Predicates for describing attribute and claim types<br />
<a href="#anchor4">2.2.</a>
Predicates for describing schemas<br />
<a href="#anchor5">3.</a>
Guidance on use of other specifications<br />
<a href="#anchor6">4.</a>
Examples<br />
<a href="#anchor7">4.1.</a>
RDFa<br />
<a href="#anchor8">5.</a>
Security Considerations<br />
<a href="#anchor9">6.</a>
IANA Considerations<br />
<a href="#rfc.references1">7.</a>
References<br />
<a href="#rfc.references1">7.1.</a>
Normative References<br />
<a href="#rfc.references2">7.2.</a>
Informative References<br />
<a href="#anchor12">Appendix A.</a>
Copyright<br />
<a href="#rfc.authors">§</a>
Author's Address<br />
</p>
<br clear="all" />
<a name="anchor1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Introduction</h3>
<p>
</p>
<p>
This document specifies how <a class='info' href='#RDF.Concepts'>RDF<span> (</span><span class='info'>Klyne, G. and J. Carroll, “Resource Description Framework (RDF): Concepts and Abstract Syntax,” February 2004.</span><span>)</span></a> [RDF.Concepts] predicates in existing ontologies can be used in metadata describing schema elements. This document is to be read in combination with the document <a class='info' href='#Schema.New'>Identity Schema Element Metadata: New Specifications<span> (</span><span class='info'>Wahl, M., “Identity Schema Element Metadata: New Specifications,” September 2007.</span><span>)</span></a> [Schema.New].
</p>
<p>The following namespace prefixes are used in this document:
</p>
<blockquote class="text">
<p><tt>rdf</tt>: <tt>http://www.w3.org/1999/02/22-rdf-syntax-ns#</tt>
</p>
<p><tt>rdfs</tt>: <tt>http://www.w3.org/2000/01/rdf-schema#</tt>
</p>
<p><tt>owl</tt>: <tt>http://www.w3.org/2002/07/owl#</tt>
</p>
<p><tt>dc</tt>: <tt>http://purl.org/dc/elements/1.1/</tt>
</p>
<p><tt>higgins</tt>: <tt>http://www.eclipse.org/higgins/ontologies/2006/higgins.owl#</tt>
</p>
</blockquote>
<p>
The key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in
<a class='info' href='#RFC2119'>RFC 2119<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a> [RFC2119].
</p>
<p>
Please send comments to the identity schemas WG mailing list at idschemas@idcommons.net.
</p>
<a name="anchor2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Recommended predicates</h3>
<p>This section lists the predicates which are defined in existing ontologies and RECOMMENDED to be used for describing schema elements and schemas.
</p>
<a name="anchor3"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.1"></a><h3>2.1.
Predicates for describing attribute and claim types</h3>
<p>An application which generates an RDF description of an attribute type or claim type SHOULD use the following predicates in triples describing that schema element.
</p>
<ul class="text">
<li>One or more triples with predicate <tt>rdfs:label</tt> SHOULD be generated, each with a value that contains a human-readable short text label for the attribute type or claim type. Each label SHOULD be limited to approximately 80 characters.
</li>
<li>One or more triples with predicate <tt>rdfs:comment</tt> SHOULD be generated, each with a value that contains a human-readable text description for the attribute type or claim type. Each comment SHOULD be limited to 65536 characters.
</li>
<li>If this attribute type or claim type is similar to another attribute type or claim type (but not identical), then one or more triples with predicate <tt>rdfs:seeAlso</tt> SHOULD be generated, each with a value that is a URI of the definition of the atribute type or claim type that is similar to this one.
</li>
</ul>
<p>An application which generates an RDF description of an attribute type or claim type for which there is no existing RDF definition MAY use the following predicates in triples describing that schema element. The choice of predicates is determined by the schema designer, who determines whether the attribute type or claim type is to be modeled as an OWL datatype property, an OWL object property, or an OWL class.
</p>
<p>If the schema designer has decided the attribute type or claim type is to be modeled as an OWL datatype property, then
</p>
<ul class="text">
<li>One triple with predicate <tt>rdf:type</tt> SHOULD be generated, with the object URI "<tt>http://www.w3.org/2002/07/owl#DatatypeProperty</tt>".
</li>
<li>If this attribute type or claim type is identical to another attribute type or claim type that has been defined with a different URI, then one triple with predicate <tt>owl:equivalentProperty</tt> SHOULD be generated, with the object of the triple the URI of that other definition.
</li>
</ul>
<p>If the schema designer has decided the attribute type or claim type is to be modeled as an OWL object property, then
</p>
<ul class="text">
<li>One triple with predicate <tt>rdf:type</tt> SHOULD be generated, with the object URI "<tt>http://www.w3.org/2002/07/owl#ObjectProperty</tt>".
</li>
<li>One triple with predicate <tt>rdfs:subPropertyOf</tt> SHOULD be generated, with the object URI "<tt>http://www.eclipse.org/higgins/ontologies/2006/higgins.owl#attribute</tt>".
</li>
<li>If this attribute type or claim type has been determined to be identical to another attribute type or claim type that has been defined with a different URI, then one triple with predicate <tt>owl:equivalentProperty</tt> SHOULD be generated, with the object of the triple the URI of that other definition.
</li>
</ul>
<p>If schema designer has decided that the attribute type or claim type is to be modeled as an OWL class, then
</p>
<ul class="text">
<li>One triple with predicate <tt>rdf:type</tt> SHOULD be generated, with the object URI "<tt>http://www.w3.org/2002/07/owl#Class</tt>".
</li>
<li>One triple with predicate <tt>rdfs:subClassOf</tt> SHOULD be generated, with the object URI "<tt>http://www.eclipse.org/higgins/ontologies/2006/higgins.owl#Attribute</tt>".
</li>
<li>If this attribute type or claim type has been determined to be identical to another attribute type or claim type that has been defined with a different URI, then one triple with predicate <tt>owl:equivalentClass</tt> SHOULD be generated, with the object of the triple the URI of that other definition.
</li>
</ul>
<p>Triples with other predicates MAY be present in the description. In particular,
see <a class='info' href='#Schema.New'>Identity Schema Element Metadata: New Specification<span> (</span><span class='info'>Wahl, M., “Identity Schema Element Metadata: New Specifications,” September 2007.</span><span>)</span></a> [Schema.New] for a list of additional predicates that are useful for describing attribute types and claim types.
</p>
<p>As there is currently no industry consensus on whether an attribute type is to be modeled as an OWL datatype property, as an OWL object property, as an OWL class, or as none of these, an application which receives an RDF description of an attribute type or claim type is to be 'liberal in what it accepts' and MUST NOT require that a triple with predicate <tt>rdf:type</tt>, <tt>rdfs:subClassOf</tt> or <tt>rdfs:subPropertyOf</tt> be provided. If triples with those predicates are provided to an application, the application that receives them MUST allow the triples to have as their object any valid URI, except as noted in section 3 below.
</p>
<a name="anchor4"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.2"></a><h3>2.2.
Predicates for describing schemas</h3>
<p>An application which generates an RDF description of a schema (a collection of attribute type or claim type definitions) SHOULD use the following predicates in triples describing that schema.
</p>
<ul class="text">
<li>One or more triples with predicate <tt>rdfs:label</tt> SHOULD be generated, each with a value that contains a human-readable short text label for the schema. Each label SHOULD be limited to approximately 80 characters.
</li>
<li>One or more triples with predicate <tt>rdfs:comment</tt> SHOULD be generated, each with a value that contains a human-readable text description for the schema. Each comment SHOULD be limited to 65536 characters.
</li>
<li>The <a class='info' href='#DC.es'>Dublin Core Metadata Element Set<span> (</span><span class='info'>, “Dublin Core Metadata Element Set, Version 1.1,” December 2006.</span><span>)</span></a> [DC.es] contains 15 properties that have been standardized by ISO for resource description. One or more triples with the predicates <tt>dc:contributor</tt>, <tt>dc:coverage</tt>, <tt>dc:creator</tt>, <tt>dc:date</tt>, <tt>dc:description</tt>, <tt>dc:format</tt>, <tt>dc:identifier</tt>, <tt>dc:language</tt>, <tt>dc:publisher</tt>, <tt>dc:relation</tt>, <tt>dc:rights</tt>, <tt>dc:source</tt>, <tt>dc:subject</tt>, <tt>dc:title</tt>, <tt>dc:type</tt> SHOULD be generated when there are appropriate values for those predicates available to describe the schema. As specified in <a class='info' href='#DC.xml'>Expressing Simple Dublin Core in RDF/XML<span> (</span><span class='info'>Beckett, D., Miller, E., and D. Brickley, “Expressing Simple Dublin Core in RDF/XML,” July 2002.</span><span>)</span></a> [DC.xml], "if the value of the Dublin Core element is a resource which has a URI rather than plain text, it should be recorded in the value of the rdf:resource attribute on the tag, with empty tag content".
</li>
<li>One triple with predicate <tt>rdf:type</tt> SHOULD be generated, with the object URI "<tt>http://www.w3.org/2002/07/owl#Ontology</tt>".
</li>
<li>One triple with predicate <tt>owl:versionInfo</tt> SHOULD be generated, with a value that contains a human-readable text string encoding a version number or date of the schema. This value SHOULD be limited to approximately 80 characters, and is typically a string generated by a revision control system such as CVS.
</li>
<li>One triple with predicate <tt>owl:imports</tt> SHOULD be generated, with the object URI "<tt>http://www.eclipse.org/higgins/ontologies/2006/higgins.owl</tt>".
</li>
<li>If the schema being described has dependencies on other schemas, then one or more triples with predicate <tt>owl:imports</tt> SHOULD be generated, in which the object URI of a triple is the URI of another schema on which this schema is dependent.
</li>
</ul>
<p>The properties listed in the <a class='info' href='#DC.terms'>DCMI Metadata terms<span> (</span><span class='info'>, “DCMI Metadata Terms,” December 2006.</span><span>)</span></a> [DC.terms] document, <tt>abstract</tt>, <tt>accessRights</tt>, <tt>accuralMethod</tt>, <tt>accrualPeriodicity</tt>, <tt>accrualPolicy</tt>, <tt>alternative</tt>, <tt>audience</tt>, <tt>available</tt>, <tt>bibliographicCitation</tt>, <tt>conformsTo</tt>, <tt>created</tt>, <tt>dateAccepted</tt>, <tt>dateCopyrighted</tt>, <tt>dateSubmitted</tt>, <tt>educationLevel</tt>, <tt>extent</tt>, <tt>hasFormat</tt>, <tt>hasPart</tt>, <tt>hasVersion</tt>, <tt>instructionalMethod</tt>, <tt>isFormatOf</tt>, <tt>isPartOf</tt>, <tt>isReferencedBy</tt>, <tt>isReplacedBy</tt>, <tt>isRequiredBy</tt>, <tt>issued</tt>, <tt>isVersionOf</tt>, <tt>license</tt>, <tt>mediator</tt>, <tt>medium</tt>, <tt>modified</tt>, <tt>provenance</tt>, <tt>references</tt>, <tt>replaces</tt>, <tt>requires</tt>, <tt>rightsHolder</tt>, <tt>spatial</tt>, <tt>tableOfContents</tt>, <tt>temporal</tt> and <tt>valid</tt>, MAY be used to provide additional description of a schema.
</p>
<p>Triples with other predicates MAY be present in the description.
</p>
<p>As there is currently no industry consensus on whether an identity schema is to be modeled as an OWL ontology, an application which receives an RDF description of a schema MUST NOT require that a triple with predicate <tt>rdf:type</tt> be provided. If triples with this predicates is provided to an application, the application that receives them MUST allow the triples to have as their object any valid URI, except as noted in section 3 below.
</p>
<a name="anchor5"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
Guidance on use of other specifications</h3>
<p>
</p>
<ul class="text">
<li>The XML attribute <tt>xml:lang</tt> SHOULD NOT be used on <tt>rdf:Description</tt> nodes representing schema elements. It MAY be used on individual triples, e.g. for setting a language of a particular <tt>rdfs:label</tt>.
</li>
<li>The <tt>rdf:type</tt> predicate MAY be used to describe a schema element. However, the values <tt>rdf:Seq</tt>, <tt>rdf:Bag</tt>, <tt>rdf:Alt</tt>, <tt>rdf:List</tt> SHOULD NOT be used as the object of this predicate when describing an attribute type or claim type.
</li>
</ul>
<p>ISSUE: this document does not currently specify how
<tt>rdfs:subClassOf</tt>, <tt>rdfs:subPropertyOf</tt>, <tt>rdfs:range</tt> and <tt>rdfs:domain</tt> are to be used.
</p>
<p>ISSUE: should <tt>owl:DeprecatedClass</tt> and <tt>owl:DeprecatedProperty</tt> be mentioned?
</p>
<a name="anchor6"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4"></a><h3>4.
Examples</h3>
<a name="anchor7"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4.1"></a><h3>4.1.
RDFa</h3>
<p>An RDFa representation in a file with Content-Type <tt>application/xhtml+xml</tt>. This example only uses predicate definitions from existing specifications.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
<?xml version="1.0"?>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:higgins="http://www.eclipse.org/higgins/ontologies/2006/higgins.owl#">
<head about="">
<title property="rdfs:label">Example schema containing two attribute types.</title>
<meta property="rdfs:comment" xml:lang="en" content="This schema has two attribute type definitions: patronymic and age." />
<meta property="owl:versionInfo" xml:lang="en" content="$1.1$" />
<link rel="rdf:type" href="http://www.w3.org/2002/07/owl#Ontology" />
<link rel="owl:imports" href="http://www.eclipse.org/higgins/ontologies/2006/higgins.owl" />
</head>
<body>
<ul about="#patronymic">
<li><span property="rdfs:label">Patryonymic</span></li>
<li>This is an <a rel="rdf:type" href="http://www.w3.org/2002/07/owl#ObjectProperty">OWL ObjectProperty</a>.</li>
<li>This is a sub-property of a
<a rel="rdfs:subPropertyOf" href="http://www.eclipse.org/higgins/ontologies/2006/higgins.owl#attribute">Higgins attribute</a>.</li>
</ul>
<ul about="#age">
<li><span property="rdfs:label">Age</span></li>
<li><span property="rdfs:label" lang="de">Alter</span> (German)</li>
<li><span property="rdfs:label" lang="fr">&#xC2;ge</span> (French)</li>
<li>Comment: <span property="rdfs:comment">How old a person is (in years)</span></li>
<li>This is an <a rel="rdf:type" href="http://www.w3.org/2002/07/owl#ObjectProperty">OWL ObjectProperty</a>.</li>
<li>This is a sub-property of a
<a rel="rdfs:subPropertyOf" href="http://www.eclipse.org/higgins/ontologies/2006/higgins.owl#attribute">Higgins attribute</a>.</li>
</ul>
</body>
</html>
</pre></div>
<a name="anchor8"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5"></a><h3>5.
Security Considerations</h3>
<p>
Security issues are not yet discussed in this memo.
</p>
<a name="anchor9"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6"></a><h3>6.
IANA Considerations</h3>
<p>
There are no IANA considerations in this memo.
</p>
<a name="rfc.references"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.7"></a><h3>7.
References</h3>
<a name="rfc.references1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>7.1. Normative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="DC.es">[DC.es]</a></td>
<td class="author-text">“<a href="http://dublincore.org/documents/dces/">Dublin Core Metadata Element Set, Version 1.1</a>,” December 2006.</td></tr>
<tr><td class="author-text" valign="top"><a name="DC.terms">[DC.terms]</a></td>
<td class="author-text">“<a href="http://dublincore.org/documents/dcmi-terms/">DCMI Metadata Terms</a>,” December 2006.</td></tr>
<tr><td class="author-text" valign="top"><a name="DC.xml">[DC.xml]</a></td>
<td class="author-text">Beckett, D., Miller, E., and D. Brickley, “<a href="http://dublincore.org/documents/dcmes-xml/">Expressing Simple Dublin Core in RDF/XML</a>,” July 2002.</td></tr>
<tr><td class="author-text" valign="top"><a name="Higgins.Ontology">[Higgins.Ontology]</a></td>
<td class="author-text">“Higgins Ontology” (<a href="http://wiki.eclipse.org/Higgins_Ontology">HTML</a>, <a href="http://www.eclipse.org/higgins/ontologies/2006/higgins.owl">OWL</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="OPENID.ax">[OPENID.ax]</a></td>
<td class="author-text">Hardt, D. and J. Bufu, “<a href="http://openid.net/specs/openid-attribute-exchange-1_0-04.html">OpenID Attribute Exchange 1.0 - Draft 4</a>,” January 2007.</td></tr>
<tr><td class="author-text" valign="top"><a name="OWL.reference">[OWL.reference]</a></td>
<td class="author-text">“<a href="http://www.w3.org/TR/owl-ref/">OWL Web Ontology Language Reference</a>,” February 2004.</td></tr>
<tr><td class="author-text" valign="top"><a name="RDF.Concepts">[RDF.Concepts]</a></td>
<td class="author-text">Klyne, G. and J. Carroll, “<a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">Resource Description Framework (RDF): Concepts and Abstract Syntax</a>,” February 2004.</td></tr>
<tr><td class="author-text" valign="top"><a name="RDF.Schema">[RDF.Schema]</a></td>
<td class="author-text">Brickley, D. and R. Guha, “<a href="http://www.w3.org/TR/rdf-schema/">RDF Vocabulary Description Language 1.0: RDF Schema</a>,” February 2004.</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
<td class="author-text">Bradner, S., “<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,” RFC 2119, BCP 14, March 1997.</td></tr>
<tr><td class="author-text" valign="top"><a name="Schema.New">[Schema.New]</a></td>
<td class="author-text">Wahl, M., “Identity Schema Element Metadata: New Specifications,” September 2007.</td></tr>
</table>
<a name="rfc.references2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>7.2. Informative References</h3>
<table width="99%" border="0">
</table>
<a name="anchor12"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.A"></a><h3>Appendix A.
Copyright</h3>
<p>
Copyright (C) Informed Control Inc. (2007).
</p>
<p>
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, AND THE ORGANIZATION HE/SHE REPRESENTS
DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR
A PARTICULAR PURPOSE.
</p>
<a name="rfc.authors"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>Author's Address</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text"> </td>
<td class="author-text">Mark Wahl</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Informed Control Inc.</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">PO Box 90626</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Austin, TX 78709</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">US</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:mark.wahl@informed-control.com">mark.wahl@informed-control.com</a></td></tr>
</table>
</body></html>