Another abandoned server code base... this is kind of an ancestor of taskrambler.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

618 lines
30 KiB

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:dc="http://purl.org/dc/terms/"
xmlns:rsa="http://www.w3.org/ns/auth/rsa#"
xmlns:cert="http://www.w3.org/ns/auth/cert#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
version="XHTML+RDFa 1.0" typeof="owl:Ontology" about="http://www.w3.org/ns/auth/cert#">
<head>
<title>The Cert Ontology Specification</title>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8" />
<style type="text/css">
@import url("http://www.w3.org/StyleSheets/TR/W3C-ED");
dl dt { margin-top: 0.5em; }
</style>
</head>
<body>
<h1><span property="dc:title" about="http://www.w3.org/ns/auth/cert#">The Cert Ontology</span> <span property="owl:versionInfo" about="http://www.w3.org/ns/auth/cert#">1.0</span></h1>
<h2>Namespace Document <span property="dc:created" about="http://www.w3.org/ns/auth/cert#" content="2008-11-13" datatype="xsd:date">13 November 2008</span></h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a> (<a href="http://www.w3.org/ns/auth/cert.n3">N3</a>, <a href="http://www.w3.org/ns/auth/cert.rdf">RDF/XML</a>)</dd>
<dt>Latest version:</dt>
<dd><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a> (<a href="http://www.w3.org/ns/auth/cert.n3">N3</a>, <a href="http://www.w3.org/ns/auth/cert.rdf">RDF/XML</a>)</dd>
<dt>Authors:</dt>
<dd><a href="http://bblfish.net/">Henry Story</a> </dd>
</dl>
<p class="copyright"><a rel="license" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010-2011 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a rel="foaf:homepage" property="foaf:name" content="World Wide Web Consotrium" href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup></span></span> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
<hr />
<h2 id="sec-status">Abstract</h2>
<p about="http://www.w3.org/ns/auth/cert#" property="rdfs:comment">Ontology for Certificates and crypto stuff.</p>
<div class="status">
<h2>Status of This Document</h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
This document is produced from work by the
<a href="http://www.w3.org/2005/Incubator/webid/">W3C WebID Incubator Group</a>.
This is an internal draft document and may not even end up being officially
published. It may also be updated, replaced or obsoleted by other documents
at any time. It is inappropriate to cite this document as other than
work in progress.
The source code for this document is available at the following
URI: <a href="https://dvcs.w3.org/hg/WebID">https://dvcs.w3.org/hg/WebID</a>
<p>This document was published by the <a about="http://www.w3.org/ns/auth/cert#" rel="rdfs:seeAlso" href="http://www.w3.org/2005/Incubator/webid/">WebID XG</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-xg-webid@w3.org">public-xg-webid@w3.org</a> (<a href="mailto:public-xg-webid-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-xg-webid/">archives</a>). All feedback is welcome.</p><p>Publication as a Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/44350/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.
</p>
<h2 id="sec-toc">Table of Contents</h2>
<ul>
<li><a href="#sec-glance">The Cert Ontology at a glance</a></li>
<li><a href="#sec-example">Examples</a></li>
<li><a href="#sec-crossref">Cross-reference for classes and properties</a></li>
<li><a href="#sec-ack">Acknowledgments</a></li>
</ul>
<a id="sec-glance"></a>
<h2 id="glance">The Cert Ontology at a glance</h2>
<p>An a-z index of <em>Cert Ontology</em> terms, by class (categories or types) and by property.</p>
<div class="azlist">
<p><span style="font-weight: bold;">Classes:</span> <a href="#Certificate">Certificate</a> | <a href="#PGPCertificate">PGPCertificate</a> | <a href="#PrivateKey">PrivateKey</a> | <a href="#PublicKey">PublicKey</a> | <a href="#RSAKey">RSAKey</a> | <a href="#RSAPublicKey">RSAPublicKey</a> | <a href="#Signature">Signature</a> | <a href="#X509Certificate">X509Certificate</a> </p>
<p><span style="font-weight: bold;">Properties:</span> <a href="#exponent">exponent</a> | <a href="#identity">identity</a> | <a href="#key">key</a> | <a href="#modulus">modulus</a> | <a href="#privateExponent">privateExponent</a> </p>
<p><span style="font-weight: bold;">Datatypes:</span> <a href="#hex">hex</a> </p>
</div>
<div style="clear: left;"></div>
<div style="clear: left;"></div>
<!-- ================================================================== -->
<p>
The evolution of the <em>Cert Ontology</em> is best considered in terms of the
stability of individual vocabulary terms, rather than the
specification as a whole. As terms stabilise in usage and
documentation, they progress through the categories
'<strong>unstable</strong>', '<strong>testing</strong>' and
'<strong>stable</strong>'. Older terms are marked '<strong>archaic</strong>' which allows the possibility of older forms to become modern again.</p><!--STATUSINFO-->
</div>
<h2 id="sec-example">Examples</h2>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
@prefix : &lt;http://www.w3.org/ns/auth/cert#&gt; .
@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
@prefix bob: &lt;https://bob.example/profile#&gt; .
@prefix rdfs: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
bob:me a foaf:Person;
foaf:name "Bob";
:key [ a :RSAPublicKey;
rdfs:label "made on 23 November 2011 on my laptop";
:modulus "00cb24ed85d64d794b69c701c186acc059501e856000f661c93204d8380e07191c5c8b368d2ac32a428acb970398664368dc2a867320220f755e99ca2eecdae62e8d15fb58e1b76ae59cb7ace8838394d59e7250b449176e51a494951a1c366c6217d8768d682dde78dd4d55e613f8839cf275d4c8403743e7862601f3c49a6366e12bb8f498262c3c77de19bce40b32f89ae62c3780f5b6275be337e2b3153ae2ba72a9975ae71ab724649497066b660fcf774b7543d980952d2e8586200eda4158b014e75465d91ecf93efc7ac170c11fc7246fc6ded79c37780000ac4e079f671fd4f207ad770809e0e2d7b0ef5493befe73544d8e1be3dddb52455c61391a1"^^xsd:hexBinary;
:exponent 65537 ;
] .
</pre>
<h2 id="sec-crossref">Cross-reference for Cert classes and properties</h2>
<p>The <em>Cert Ontology</em> introduces the following classes and properties. There is a link at the
top of this document to the RDF/XML and RDF/N3 versions.</p>
<!-- the following is the script-generated list of classes and properties -->
<!-- this is the a-z listing -->
<div class="azlist">
<p><span style="font-weight: bold;">Classes:</span> <a href="#Certificate">Certificate</a> | <a href="#PGPCertificate">PGPCertificate</a> | <a href="#PrivateKey">PrivateKey</a> | <a href="#PublicKey">PublicKey</a> | <a href="#RSAKey">RSAKey</a> | <a href="#RSAPublicKey">RSAPublicKey</a> | <a href="#Signature">Signature</a> | <a href="#X509Certificate">X509Certificate</a> </p>
<p><span style="font-weight: bold;">Properties:</span> <a href="#exponent">exponent</a> | <a href="#identity">identity</a> | <a href="#key">key</a> | <a href="#modulus">modulus</a> | <a href="#privateExponent">privateExponent</a> </p>
<p><span style="font-weight: bold;">Datatypes:</span> <a href="#hex">hex</a> </p>
</div>
<!-- and this is the bulk of the vocab descriptions -->
<div class="termlist">
<div class='termdetails'><br />
<h3>Classes</h3>
<div class="specterm" id="Certificate" about="http://www.w3.org/ns/auth/cert#Certificate" typeof="owl:Class">
<h4>Class: cert:Certificate</h4>
<em property="rdfs:label" >Certificate</em> - <span property="rdfs:comment" >A certificate is a Document that is signed.
As explained here http://www.pgpi.org/doc/pgpintro/#p16
'A digital certificate consists of three things:
* A public key.
* Certificate information. ('Identity' information about the
user, such as name, user ID, and so on.)
* One or more digital signatures.'
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://xmlns.com/foaf/0.1/Document"><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></span></dd> <dt>Has sub class</dt>
<dd><a href="#X509Certificate">cert:X509Certificate</a>
</dd>
<dd><a href="#PGPCertificate">cert:PGPCertificate</a>
</dd><dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#Certificate">#</a>] <!-- Certificate --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="PGPCertificate" about="http://www.w3.org/ns/auth/cert#PGPCertificate" typeof="owl:Class">
<h4>Class: cert:PGPCertificate</h4>
<em property="rdfs:label" >PGPCertificate</em> - <span property="rdfs:comment" >the class of PGP Certificates</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Certificate"><a href="#Certificate">cert:Certificate</a></span></dd><dt>Equivalent Class:</dt>
<dd><a href="#PubKey">wot:PubKey</a>
</dd> <dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#PGPCertificate">#</a>] <!-- PGPCertificate --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="PublicKey" about="http://www.w3.org/ns/auth/cert#PublicKey" typeof="owl:Class">
<h4>Class: cert:PublicKey</h4>
<em property="rdfs:label" >PublicKey</em> - <span property="rdfs:comment" >Public Key</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Properties include:</dt>
<dd><a href="#identity">cert:identity</a></dd>
<dt>Used with:</dt>
<dd><a href="#key">cert:key</a></dd> <dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Key"><a href="http://www.w3.org/ns/auth/cert#Key">cert:Key</a></span></dd> <dt>Has sub class</dt>
<dd><a href="#RSAPublicKey">cert:RSAPublicKey</a>
</dd><dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#PublicKey">#</a>] <!-- PublicKey --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="RSAKey" about="http://www.w3.org/ns/auth/cert#RSAKey" typeof="owl:Class">
<h4>Class: cert:RSAKey</h4>
<em property="rdfs:label" >RSA Key</em> - <span property="rdfs:comment" >
The union of the public and private components of an RSAKey.
Usually those pieces are not kept together
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Properties include:</dt>
<dd><a href="#modulus">cert:modulus</a></dd>
<dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Key"><a href="http://www.w3.org/ns/auth/cert#Key">cert:Key</a></span></dd> <dt>Has sub class</dt>
<dd><a href="#RSAPublicKey">cert:RSAPublicKey</a>
</dd><dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#RSAKey">#</a>] <!-- RSAKey --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="RSAPublicKey" about="http://www.w3.org/ns/auth/cert#RSAPublicKey" typeof="owl:Class">
<h4>Class: cert:RSAPublicKey</h4>
<em property="rdfs:label" >RSA Public Key</em> - <span property="rdfs:comment" >
The RSA public key. Padded message m are encrypted by applying the function
modulus(power(m,exponent),modulus)
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Properties include:</dt>
<dd><a href="#exponent">cert:exponent</a></dd>
<dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#RSAKey"><a href="#RSAKey">cert:RSAKey</a></span></dd>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#PublicKey"><a href="#PublicKey">cert:PublicKey</a></span></dd><dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#RSAPublicKey">#</a>] <!-- RSAPublicKey --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="Signature" about="http://www.w3.org/ns/auth/cert#Signature" typeof="owl:Class">
<h4>Class: cert:Signature</h4>
<em property="rdfs:label" >Signature</em> - <span property="rdfs:comment" >the class of signtatures</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#Signature">#</a>] <!-- Signature --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="X509Certificate" about="http://www.w3.org/ns/auth/cert#X509Certificate" typeof="owl:Class">
<h4>Class: cert:X509Certificate</h4>
<em property="rdfs:label" >X509Certificate</em> - <span property="rdfs:comment" >the class of X509 Certificates</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Certificate"><a href="#Certificate">cert:Certificate</a></span></dd><dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#X509Certificate">#</a>] <!-- X509Certificate --> [<a href="#glance">back to top</a>]</p>
<br/>
</div>
<div class="specterm" id="PrivateKey" about="http://www.w3.org/ns/auth/cert#PrivateKey" typeof="owl:Class">
<h4>Class: cert:PrivateKey</h4>
<em property="rdfs:label" >PrivateKey</em> - <span property="rdfs:comment" >Private Key</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unknown</dd>
<dt>Sub class of</dt>
<dd><span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Key"><a href="http://www.w3.org/ns/auth/cert#Key">cert:Key</a></span></dd> <dt>Is Defined By:</dt>
<dd rel="rdfs:isDefinedBy"><a href="http://www.w3.org/ns/auth/cert#">http://www.w3.org/ns/auth/cert#</a>
</dd><dt>OWL Class</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#PrivateKey">#</a>] <!-- PrivateKey --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><h3>Properties</h3>
<div class="specterm" id="exponent" about="http://www.w3.org/ns/auth/cert#exponent" typeof="owl:DatatypeProperty">
<h4>Property: cert:exponent</h4>
<em property="rdfs:label" >exponent</em> - <span property="rdfs:comment" >
The exponent used to encrypt the message. Number chosen between
1 and the totient(p*q). Often named 'e' .
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Domain:</dt>
<dd><span rel="rdfs:domain" href="http://www.w3.org/ns/auth/cert#RSAPublicKey"><a href="#RSAPublicKey">cert:RSAPublicKey</a></span>
</dd>
<dt>Range:</dt>
<dd><span rel="rdfs:range" href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"><a href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">xsd:nonNegativeInteger</a></span>
</dd><dt>Is Defined By:</dt> <dd> <span rel="rdfs:isDefinedBy" href="http://www.w3.org/ns/auth/cert#"></span>
</dd><dt>Datatype Property</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#exponent">#</a>] <!-- exponent --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="key" about="http://www.w3.org/ns/auth/cert#key" typeof="owl:InverseFunctionalProperty">
<h4>Property: cert:key</h4>
<em property="rdfs:label" >key</em> - <span property="rdfs:comment" >relates an agent to a key - most often the public key.</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Domain:</dt>
<dd><span rel="rdfs:domain" href="http://xmlns.com/foaf/0.1/Agent"><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></span>
</dd>
<dt>Range:</dt>
<dd><span rel="rdfs:range" href="http://www.w3.org/ns/auth/cert#PublicKey"><a href="#PublicKey">cert:PublicKey</a></span>
</dd><dt>Inverse property of</dt>
<dd><span rel="owl:inverseOf" href="http://www.w3.org/ns/auth/cert#identity"><a href="#identity">cert:identity</a></span></dd><dt>Has inverse property</dt>
<dd><a href="#identity">cert:identity</a>
</dd><dt>Is Defined By:</dt> <dd> <span rel="rdfs:isDefinedBy" href="http://www.w3.org/ns/auth/cert#"></span>
</dd><dt>RDF Property</dt>
<dd><span rel="rdf:type" href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"></span></dd> <dt>Object Property</dt>
<dd><span rel="rdf:type" href="http://www.w3.org/2002/07/owl#ObjectProperty"></span></dd><dt>Inverse Functional Property</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#key">#</a>] <!-- key --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="modulus" about="http://www.w3.org/ns/auth/cert#modulus" typeof="owl:DatatypeProperty">
<h4>Property: cert:modulus</h4>
<em property="rdfs:label" >modulus</em> - <span property="rdfs:comment" >
<p>The modulus of an RSA public and private key.
Or the modulus of a DSA Key.
The modulus is encoded as a hex binary. The binary is the same as the one encoded in the
<a href="http://www.w3.org/TR/xmldsig-core/#sec-CryptoBinary">XML DSIG CryptoBinary</a>
</p>
<blockquote>
This specification defines the ds:CryptoBinary simple type for representing arbitrary-length integers (e.g. "bignums") in XML as octet strings. The integer value is first converted to a "big endian" bitstring. The bitstring is then padded with leading zero bits so that the total number of bits == 0 mod 8 (so that there are an integral number of octets). If the bitstring contains entire leading octets that are zero, these are removed (so the high-order octet is always non-zero).
</blockquote>
<p>The only difference is that the octet string is then encoded using either xsd:base64Binary or xsd:hexBinary. Currently for all usages of this relation, the xsd:hexBinary datatype should be used until the SPARQL working group specifies specifies in its <a href="http://www.w3.org/TR/sparql11-entailment/#DEntRegime">D-Entailment</a> that those two types are equivalent.</p>
<p>It would have been better had there been a hexInteger datatype that was standard and supported by all tools.</p>
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Domain:</dt>
<dd><span rel="rdfs:domain" href="http://www.w3.org/ns/auth/cert#RSAKey"><a href="#RSAKey">cert:RSAKey</a></span>
</dd>
<dt>Range:</dt>
<dd><span rel="rdfs:range" href="http://www.w3.org/2001/XMLSchema#hexBinary"><a href="http://www.w3.org/2001/XMLSchema#hexBinary">xsd:hexBinary</a></span>
</dd> <dd><span rel="rdfs:range" href="http://www.w3.org/2001/XMLSchema#base64Binary"><a href="http://www.w3.org/2001/XMLSchema#base64Binary">xsd:base64Binary</a></span>
</dd><dt>Is Defined By:</dt> <dd> <span rel="rdfs:isDefinedBy" href="http://www.w3.org/ns/auth/cert#"></span>
</dd><dt>Datatype Property</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#modulus">#</a>] <!-- modulus --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><div class="specterm" id="privateExponent" about="http://www.w3.org/ns/auth/cert#privateExponent" typeof="owl:DatatypeProperty">
<h4>Property: cert:privateExponent</h4>
<em property="rdfs:label" >private</em> - <span property="rdfs:comment" >
The exponent used to decrypt the message
calculated as
public_exponent*private_exponent = 1 modulo totient(p*q)
The private exponent is often named 'd'
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >unstable</dd>
<dt>Domain:</dt>
<dd><span rel="rdfs:domain" href="http://www.w3.org/ns/auth/cert#RSAPrivateKey"><a href="http://www.w3.org/ns/auth/cert#RSAPrivateKey">cert:RSAPrivateKey</a></span>
</dd>
<dt>Range:</dt>
<dd><span rel="rdfs:range" href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"><a href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">xsd:nonNegativeInteger</a></span>
</dd><dt>Is Defined By:</dt> <dd> <span rel="rdfs:isDefinedBy" href="http://www.w3.org/ns/auth/cert#"></span>
</dd><dt>Datatype Property</dt>
</dl>
<p style="float: right; font-size: small;">[<a href="#privateExponent">#</a>] <!-- privateExponent --> [<a href="#glance">back to top</a>]</p>
<br/>
</div>
<div class="specterm" id="identity" about="http://www.w3.org/ns/auth/cert#identity" typeof="owl:ObjectProperty">
<h4>Property: cert:identity</h4>
<em property="rdfs:label" >identity</em> - <span property="rdfs:comment" >
the identity of the public key. This is the entity that knows the private key and
so can decrypt messages encrypted with the public key, or encrypt messages that can
be decrypted with the public key.
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >archaic</dd>
<dt>Domain:</dt>
<dd><span rel="rdfs:domain" href="http://www.w3.org/ns/auth/cert#PublicKey"><a href="#PublicKey">cert:PublicKey</a></span>
</dd>
<dt>Inverse property of</dt>
<dd><span rel="owl:inverseOf" href="http://www.w3.org/ns/auth/cert#key"><a href="#key">cert:key</a></span></dd><dt>Has inverse property</dt>
<dd><a href="#key">cert:key</a>
</dd><dt>Is Defined By:</dt> <dd> <span rel="rdfs:isDefinedBy" href="http://www.w3.org/ns/auth/cert#"></span>
</dd><dt>RDF Property</dt>
<dd><span rel="rdf:type" href="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"></span></dd> <dt>Object Property</dt>
<dt>Editorial Note</dt>
<dd property="skos:editorialNote">
It turns out that this relation is unintuitive to write out and to name.
One should instead use cert:key
</dd>
</dl>
<p style="float: right; font-size: small;">[<a href="#identity">#</a>] <!-- identity --> [<a href="#glance">back to top</a>]</p>
<br/>
</div><h3>Datatypes</h3>
<div class="specterm" id="hex" about="http://www.w3.org/ns/auth/cert#hex" typeof="http://www.w3.org/2000/01/rdf-schema#Datatype">
<h4>Datatype: cert:hex</h4>
<em property="rdfs:label" >hexadecimal</em> - <span property="rdfs:comment" ><span xmlns="http://www.w3.org/1999/xhtml"><p>
An encoding of a positive integer (from 0 to infinity) as a hexadecimal string that makes it easy to read and/or fun to present on the web.</p>
<p>The purpose of this way of representing hexadecimals is to enable users to copy and paste hexadecimal notations as shown by most browsers, keychains or tools such as opensso, into their rdf representation of choice. There are a wide variety of ways in which such strings can be presented. One finds the following:</p>
<pre>
e1 dc d5 e1 00 8f 21 5e d5 cc 7c 7e c4 9c ad 86
64 aa dc 29 f2 8d d9 56 7f 31 b6 bd 1b fd b8 ee
51 0d 3c 84 59 a2 45 d2 13 59 2a 14 82 1a 0f 6e
d3 d1 4a 2d a9 4c 7e db 90 07 fc f1 8d a3 8e 38
25 21 0a 32 c1 95 31 3c ba 56 cc 17 45 87 e1 eb
fd 9f 0f 82 16 67 9f 67 fa 91 e4 0d 55 4e 52 c0
66 64 2f fe 98 8f ae f8 96 21 5e ea 38 9e 5c 4f
27 e2 48 ca ca f2 90 23 ad 99 4b cc 38 32 6d bf
</pre>
<p>
Or the same as the above, with ':' instead of spaces. We can't guarantee that these are the only ways such tools will present hexadecimals, so we are very lax.</p>
<p>The letters can be uppercase or lowercase, or mixed. </p>
<p>Some strings may start with initial 00's, and can be stripped in this notation as they often are. Doing this could, in complement of 2 notation turn a positive number into a negative one, if the first hexadecimal character happens to be one of the set {'8', '9', 'a', 'A', 'b', 'B', 'c', 'C', 'd', 'D', 'e', 'E', 'f', 'F'} . As we interpret this string as a hexadecimal number leading 00s are not important (Complement of 2 notation and hexadecimal overlap for positive numbers)</p>
<p> In order to make this fun, we allow any unicode characters in the string. A parser should </p>
<ol>
<li>remove all non hexadecimal characters</li>
<li>treat the resulting as a hexadecimal representation of a number</li>
</ol>
<p>
This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.
</p>
<p>
Cert hex is also a datatype property because we used to write it out like this
</p>
<pre>
[] a rsa:RSAPublicKey;
rsa:public_exponent [ cert:hex "e1 dc d5 ..."]
</pre>
<p> The above notation is now deprecated. Now we prefer the literal format below.</p>
<pre>
[] a rsa:RSAPublicKey;
rsa:public_exponent "e1 dc d5 ..."^^cert:hex .
</pre>
</span>
</span> <br />
<dl>
<dt>Status:</dt>
<dd property="vs:term_status" >archaic</dd>
<dt> Equivalent Class: </dt>
<dd> <a href="#nonNegativeInteger">xsd:nonNegativeInteger</a> </dd><dt> Editorial Note: </dt>
<dd> <span xmlns="http://www.w3.org/1999/xhtml"><p>
This relation should slowly be transited to just being a datatype.</p>
<p>Being a datatype and a property is legal as explained here
<a href="http://lists.w3.org/Archives/Public/semantic-web/2010Mar/0037.html">on the semantic web mailing list in March 2010</a>.
But it may be somewhat confusing, especially if it goes against a pattern - still to be set - by the xsd datatypes as the follow up email makes clear. </p></span>
</dd>
</dl>
<p style="float: right; font-size: small;">[<a href="#hex">#</a>] <!-- hex --> [<a href="#glance">back to top</a>]</p>
<br/>
</div>
</div>
</div>
<!-- dirty hack for specgen -->
<div style="display: none"><span about="http://www.w3.org/ns/auth/cert#PGPCertificate" rel="owl:equivalentClass" href="http://xmlns.com/wot/0.1/PubKey"></span></div>
<div style="display: none"><span about="http://www.w3.org/ns/auth/cert#hex" rel="owl:equivalentClass" href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"></span></div>
<div style="display: none"><span about="http://www.w3.org/ns/auth/cert#int" rel="owl:equivalentClass" href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"></span></div>
<h2 id="sec-ack">Acknowledgments</h2>
<p>The following people have been instrumental in providing thoughts, feedback,
reviews, criticism and input in the creation of this specification:</p>
<ul>
<li>Tim Berners-Lee</li>
<li>Sarven Capadisli</li>
<li>Melvin Carvalho</li>
<li>Michael Hausenblas</li>
<li>Kingsley Idehen</li>
<li>Ian Jacobi</li>
<li>Nathan Rixham</li>
<li>Seth Russell</li>
<li>Jeff Sayre</li>
<li>Manu Sporny</li>
<li>Toby Inkster</li>
<li>Bruno Harbulot</li>
<li>Reto Bachmann-Gmür</li>
<li>Sergio Fernandez</li>
<li><a href="http://ii.uwb.edu.pl/~dtomaszuk/">Dominik Tomaszuk</a> (<a href="http://ii.uwb.edu.pl/">University of Bialystok</a>)</li>
</ul>
</body>
</html>