--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/cert.owl Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,107 @@
+<rdf:RDF xmlns="http://www.w3.org/2000/01/rdf-schema#"
+xmlns:dc="http://purl.org/dc/terms/"
+xmlns:foaf="http://xmlns.com/foaf/0.1/"
+xmlns:owl="http://www.w3.org/2002/07/owl#"
+xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+xmlns:skos="http://www.w3.org/2004/02/skos/core#"
+xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+
+<owl:Ontology rdf:about="http://www.w3.org/ns/auth/cert#">
+<owl:versionInfo>1.0</owl:versionInfo>
+<rdfs:seeAlso rdf:resource="http://www.w3.org/2005/Incubator/webid/"/>
+<rdfs:comment>Ontology for Certificates and crypto stuff.</rdfs:comment>
+<dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+<dc:title>The Cert Ontology</dc:title>
+</owl:Ontology>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#Certificate">
+<rdfs:label>Certificate</rdfs:label>
+<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: (1) A public key. (2) Certificate information. 'Identity' information about the user, such as name, user ID, and so on. (3) One or more digital signatures.'</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://xmlns.com/foaf/0.1/Document"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#Key">
+<rdfs:label>Key</rdfs:label>
+<rdfs:comment>the class of keys</rdfs:comment>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PGPCertificate">
+<rdfs:label>PGP Certificate</rdfs:label>
+<rdfs:comment>the class of PGP Certificates</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Certificate"/>
+<owl:equivalentClass rdf:resource="http://xmlns.com/wot/0.1/PubKey"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PrivateKey">
+<rdfs:label>Private Key</rdfs:label>
+<rdfs:comment>Private Key</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Key"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PublicKey">
+<rdfs:label>Public Key</rdfs:label>
+<rdfs:comment>Public Key</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Key"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#Signature">
+<rdfs:label>Signature</rdfs:label>
+<rdfs:comment>the class of signtatures</rdfs:comment>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#X509Certificate">
+<rdfs:label>Certificate</rdfs:label>
+<rdfs:comment>the class of X509 Certificates</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Certificate"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:DatatypeProperty rdf:about="http://www.w3.org/ns/auth/cert#decimal">
+<rdfs:label>decimal</rdfs:label>
+<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+<rdfs:comment>An encoding of an integer in base 10 notation. Use cert:int instead.</rdfs:comment>
+<rdfs:domain rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
+<vs:term_status>archaic</vs:term_status>
+</owl:DatatypeProperty>
+
+<owl:DatatypeProperty rdf:about="http://www.w3.org/ns/auth/cert#hex">
+<rdfs:label>hex</rdfs:label>
+<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+<rdfs:comment>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.
+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 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 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. The letters can be uppercase or lowercase, or mixed.
+ 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 ofthe 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) In order to make this fun, we allow any unicode characters in the string. A parser should 1. remove all non hexadecimal characters
+2. treat the resulting as a hexadecimal representation of a number This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.</rdfs:comment>
+<vs:term_status>unstable</vs:term_status>
+</owl:DatatypeProperty>
+
+<owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/cert#identity">
+<rdfs:label>identity</rdfs:label>
+<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. It can be an Agent, or an idirect identifier of an agent such as a foaf:OnlineAccount .
+Should one specify the range as being the union of those two classes, or should one leave this open?</rdfs:comment>
+<rdfs:domain rdf:resource="http://www.w3.org/ns/auth/cert#PublicKey"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:ObjectProperty>
+
+<owl:DatatypeProperty rdf:about="http://www.w3.org/ns/auth/cert#int">
+<rdfs:label>int</rdfs:label>
+<rdfs:comment>A positive integer in base 10 notation. xsd:nonNegativeInteger could be used, but is a bit long to write, and may be too strictly defined.
+This is here to provice a pair with cert:hex, to avoid needing to import a new namespace, and to give a bit more flexibility in the future.</rdfs:comment>
+<vs:term_status>unstable</vs:term_status>
+</owl:DatatypeProperty>
+
+<owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/cert#public_key">
+<rdfs:label>public key</rdfs:label>
+<rdfs:comment>relates the private key to the public key component, in a public/private key pair.</rdfs:comment>
+<rdfs:domain rdf:resource="http://www.w3.org/ns/auth/cert#PrivateKey"/>
+<rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#PublicKey"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:ObjectProperty>
+</rdf:RDF>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/diff/README.txt Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,8 @@
+diff:
+1. cert_diff
+oryginal - http://www.w3.org/ns/auth/cert
+modified - ../cert.owl
+
+2. rsa_diff
+oryginal - http://www.w3.org/ns/auth/rsa
+modified - ../rsa.owl
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/diff/cert Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,182 @@
+
+<!-- Processed by Id: cwm.py,v 1.197 2007/12/13 15:38:39 syosi Exp -->
+<!-- using base file:///Users/hjs/Programming/w3.org/WWW/ns/auth/cert.n3-->
+
+
+<rdf:RDF xmlns="http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:foaf="http://xmlns.com/foaf/0.1/"
+ xmlns:owl="http://www.w3.org/2002/07/owl#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:skos="http://www.w3.org/2004/02/skos/core#"
+ xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+
+ <owl:Ontology rdf:about="cert">
+ <dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+ <comment>
+ Ontology for Certificates and crypto stuff.
+ This is in development.
+ Some other ontologies to look at:
+ * http://www.w3.org/2000/10/swap/crypto
+ + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust
+ - a bit old perhaps. It imports daml+oil
+ - would help to be more completely specified
+ - uses literals as subjects a little liberally, which makes this a
+ bit difficult to work with frameworks that don't permit this
+ * http://xmlns.com/wot/0.1/
+ - limited very much to PGP (though on can map PGP to X509)
+ - a little coarse grained, mixes up the PGP certificate with the PGP
+ public key
+ *
+ Todo:
+ - add some classes and relations for DSA
+ - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter?
+ - expand more on the certification side of things
+ - verify this by security experts
+ - owl2 has some constructs for combined inverse functional properties.
+ This may be useful to use in defining an RSA key which is identified
+ by two numbers.
+ - also create html version of the spec by using this as a template.
+ - should comments such as this be in html?
+ - add more todos
+ </comment>
+ <seeAlso rdf:resource="X509Uml.svg"/>
+ <seeAlso rdf:resource="rsa"/>
+ <seeAlso rdf:resource="http://lists.foaf-project.org/mailman/listinfo/foaf-protocols"/>
+ <vs:term_status>unstable</vs:term_status>
+ <foaf:maker rdf:resource="http://bblfish.net/people/henry/card#me"/>
+ </owl:Ontology>
+
+ <owl:Class rdf:about="cert#Certificate">
+ <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.'
+ </comment>
+ <subClassOf rdf:resource="http://xmlns.com/foaf/0.1/Document"/>
+ <vs:term_status>unstable</vs:term_status>
+ </owl:Class>
+
+ <owl:Class rdf:about="cert#Key">
+ <comment>the class of keys</comment>
+ <vs:term_status>unstable</vs:term_status>
+ </owl:Class>
+
+ <owl:Class rdf:about="cert#PGPCertificate">
+ <comment>the class of PGP Certificates</comment>
+ <subClassOf rdf:resource="cert#Certificate"/>
+ <owl:equivalentClass rdf:resource="http://xmlns.com/wot/0.1/PubKey"/>
+ <vs:term_status>unstable</vs:term_status>
+ </owl:Class>
+
+ <owl:Class rdf:about="cert#PrivateKey">
+ <comment>Private Key</comment>
+ <subClassOf rdf:resource="cert#Key"/>
+ </owl:Class>
+
+ <owl:Class rdf:about="cert#PublicKey">
+ <comment>Public Key</comment>
+ <subClassOf rdf:resource="cert#Key"/>
+ <vs:term_status>unstable</vs:term_status>
+ </owl:Class>
+
+ <owl:Class rdf:about="cert#Signature">
+ <comment>the class of signtatures</comment>
+ <vs:term_status>unstable</vs:term_status>
+ </owl:Class>
+
+ <owl:Class rdf:about="cert#X509Certificate">
+ <comment>the class of X509 Certificates</comment>
+ <seeAlso rdf:resource="http://en.wikipedia.org/wiki/X509"/>
+ <subClassOf rdf:resource="cert#Certificate"/>
+ <vs:term_status>unstable</vs:term_status>
+ </owl:Class>
+
+ <owl:DatatypeProperty rdf:about="cert#decimal">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+ <comment xml:lang="en">
+ An encoding of an integer in base 10 notation. Use cert:int instead.
+ </comment>
+ <domain rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+ <range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
+ <vs:term_status>archaic</vs:term_status>
+ <skos:editorialNote xml:lang="en">
+ The name for this relation is not good. Even though Decimal is clearly defined as numbers in base 10 notation ( conf http://en.wikipedia.org/wiki/Decimal ), it is most often understood as refering to numbers with decimal fractions, which in cryptgraphic integer arithmetic do not turn up.
+ Instead one should use cert:int
+ </skos:editorialNote>
+ </owl:DatatypeProperty>
+
+ <Datatype rdf:about="cert#hex">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#DatatypeProperty"/>
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+ <comment xml:lang="en">
+ 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.
+ 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
+
+ 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
+
+ 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.
+ The letters can be uppercase or lowercase, or mixed.
+ 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)
+ In order to make this fun, we allow any unicode characters in the string. A parser should
+ 1. remove all non hexadecimal characters
+ 2. treat the resulting as a hexadecimal representation of a number
+ This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.
+ </comment>
+ <domain rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+ <label xml:lang="en">hexadecimal</label>
+ <range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
+ <seeAlso rdf:resource="http://en.wikipedia.org/wiki/Hexadecimal"/>
+ <owl:equivalentClass rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+ <vs:term_status>unstable</vs:term_status>
+ <skos:editorialNote xml:lang="en">
+ This relation should slowly be transited to just being a datatype.
+ Being a datatype and a property is legal as explained here
+ http://lists.w3.org/Archives/Public/semantic-web/2010Mar/0037.html
+ 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.
+ </skos:editorialNote>
+ </Datatype>
+
+ <rdf:Property rdf:about="cert#identity">
+ <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. It can be an Agent, or an idirect identifier of an agent such as a foaf:OnlineAccount .
+ Should one specify the range as being the union of those two classes, or should one leave this open?
+ </comment>
+ <domain rdf:resource="cert#PublicKey"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Property>
+
+ <Datatype rdf:about="cert#int">
+ <comment xml:lang="en">
+ A positive integer in base 10 notation.
+ xsd:nonNegativeInteger could be used, but is a bit long to write, and may be too strictly defined.
+ This is here to provice a pair with cert:hex, to avoid needing to import a new namespace, and to give a bit more flexibility in the future.
+ </comment>
+ <owl:equivalentClass rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+ <vs:term_status>unstable</vs:term_status>
+ <skos:editorialNote xml:lang="en">
+ We may decide to make it easier to write integers than what xsd:integer provides, if needed.
+ </skos:editorialNote>
+ </Datatype>
+
+ <rdf:Property rdf:about="cert#public_key">
+ <comment>
+ relates the private key to the public key component, in a public/private
+ key pair.
+ </comment>
+ <domain rdf:resource="cert#PrivateKey"/>
+ <range rdf:resource="cert#PublicKey"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Property>
+</rdf:RDF>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/diff/cert_diff Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,288 @@
+1,5d0
+<
+< <!-- Processed by Id: cwm.py,v 1.197 2007/12/13 15:38:39 syosi Exp -->
+< <!-- using base file:///Users/hjs/Programming/w3.org/WWW/ns/auth/cert.n3-->
+<
+<
+7,181c2,106
+< xmlns:dc="http://purl.org/dc/terms/"
+< xmlns:foaf="http://xmlns.com/foaf/0.1/"
+< xmlns:owl="http://www.w3.org/2002/07/owl#"
+< xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+< xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+< xmlns:skos="http://www.w3.org/2004/02/skos/core#"
+< xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+<
+< <owl:Ontology rdf:about="cert">
+< <dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+< <comment>
+< Ontology for Certificates and crypto stuff.
+< This is in development.
+< Some other ontologies to look at:
+< * http://www.w3.org/2000/10/swap/crypto
+< + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust
+< - a bit old perhaps. It imports daml+oil
+< - would help to be more completely specified
+< - uses literals as subjects a little liberally, which makes this a
+< bit difficult to work with frameworks that don't permit this
+< * http://xmlns.com/wot/0.1/
+< - limited very much to PGP (though on can map PGP to X509)
+< - a little coarse grained, mixes up the PGP certificate with the PGP
+< public key
+< *
+< Todo:
+< - add some classes and relations for DSA
+< - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter?
+< - expand more on the certification side of things
+< - verify this by security experts
+< - owl2 has some constructs for combined inverse functional properties.
+< This may be useful to use in defining an RSA key which is identified
+< by two numbers.
+< - also create html version of the spec by using this as a template.
+< - should comments such as this be in html?
+< - add more todos
+< </comment>
+< <seeAlso rdf:resource="X509Uml.svg"/>
+< <seeAlso rdf:resource="rsa"/>
+< <seeAlso rdf:resource="http://lists.foaf-project.org/mailman/listinfo/foaf-protocols"/>
+< <vs:term_status>unstable</vs:term_status>
+< <foaf:maker rdf:resource="http://bblfish.net/people/henry/card#me"/>
+< </owl:Ontology>
+<
+< <owl:Class rdf:about="cert#Certificate">
+< <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.'
+< </comment>
+< <subClassOf rdf:resource="http://xmlns.com/foaf/0.1/Document"/>
+< <vs:term_status>unstable</vs:term_status>
+< </owl:Class>
+<
+< <owl:Class rdf:about="cert#Key">
+< <comment>the class of keys</comment>
+< <vs:term_status>unstable</vs:term_status>
+< </owl:Class>
+<
+< <owl:Class rdf:about="cert#PGPCertificate">
+< <comment>the class of PGP Certificates</comment>
+< <subClassOf rdf:resource="cert#Certificate"/>
+< <owl:equivalentClass rdf:resource="http://xmlns.com/wot/0.1/PubKey"/>
+< <vs:term_status>unstable</vs:term_status>
+< </owl:Class>
+<
+< <owl:Class rdf:about="cert#PrivateKey">
+< <comment>Private Key</comment>
+< <subClassOf rdf:resource="cert#Key"/>
+< </owl:Class>
+<
+< <owl:Class rdf:about="cert#PublicKey">
+< <comment>Public Key</comment>
+< <subClassOf rdf:resource="cert#Key"/>
+< <vs:term_status>unstable</vs:term_status>
+< </owl:Class>
+<
+< <owl:Class rdf:about="cert#Signature">
+< <comment>the class of signtatures</comment>
+< <vs:term_status>unstable</vs:term_status>
+< </owl:Class>
+<
+< <owl:Class rdf:about="cert#X509Certificate">
+< <comment>the class of X509 Certificates</comment>
+< <seeAlso rdf:resource="http://en.wikipedia.org/wiki/X509"/>
+< <subClassOf rdf:resource="cert#Certificate"/>
+< <vs:term_status>unstable</vs:term_status>
+< </owl:Class>
+<
+< <owl:DatatypeProperty rdf:about="cert#decimal">
+< <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+< <comment xml:lang="en">
+< An encoding of an integer in base 10 notation. Use cert:int instead.
+< </comment>
+< <domain rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+< <range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
+< <vs:term_status>archaic</vs:term_status>
+< <skos:editorialNote xml:lang="en">
+< The name for this relation is not good. Even though Decimal is clearly defined as numbers in base 10 notation ( conf http://en.wikipedia.org/wiki/Decimal ), it is most often understood as refering to numbers with decimal fractions, which in cryptgraphic integer arithmetic do not turn up.
+< Instead one should use cert:int
+< </skos:editorialNote>
+< </owl:DatatypeProperty>
+<
+< <Datatype rdf:about="cert#hex">
+< <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#DatatypeProperty"/>
+< <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+< <comment xml:lang="en">
+< 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.
+< 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
+<
+< 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
+<
+< 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.
+< The letters can be uppercase or lowercase, or mixed.
+< 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)
+< In order to make this fun, we allow any unicode characters in the string. A parser should
+< 1. remove all non hexadecimal characters
+< 2. treat the resulting as a hexadecimal representation of a number
+< This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.
+< </comment>
+< <domain rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+< <label xml:lang="en">hexadecimal</label>
+< <range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
+< <seeAlso rdf:resource="http://en.wikipedia.org/wiki/Hexadecimal"/>
+< <owl:equivalentClass rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+< <vs:term_status>unstable</vs:term_status>
+< <skos:editorialNote xml:lang="en">
+< This relation should slowly be transited to just being a datatype.
+< Being a datatype and a property is legal as explained here
+< http://lists.w3.org/Archives/Public/semantic-web/2010Mar/0037.html
+< 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.
+< </skos:editorialNote>
+< </Datatype>
+<
+< <rdf:Property rdf:about="cert#identity">
+< <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. It can be an Agent, or an idirect identifier of an agent such as a foaf:OnlineAccount .
+< Should one specify the range as being the union of those two classes, or should one leave this open?
+< </comment>
+< <domain rdf:resource="cert#PublicKey"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Property>
+<
+< <Datatype rdf:about="cert#int">
+< <comment xml:lang="en">
+< A positive integer in base 10 notation.
+< xsd:nonNegativeInteger could be used, but is a bit long to write, and may be too strictly defined.
+< This is here to provice a pair with cert:hex, to avoid needing to import a new namespace, and to give a bit more flexibility in the future.
+< </comment>
+< <owl:equivalentClass rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+< <vs:term_status>unstable</vs:term_status>
+< <skos:editorialNote xml:lang="en">
+< We may decide to make it easier to write integers than what xsd:integer provides, if needed.
+< </skos:editorialNote>
+< </Datatype>
+<
+< <rdf:Property rdf:about="cert#public_key">
+< <comment>
+< relates the private key to the public key component, in a public/private
+< key pair.
+< </comment>
+< <domain rdf:resource="cert#PrivateKey"/>
+< <range rdf:resource="cert#PublicKey"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Property>
+---
+> xmlns:dc="http://purl.org/dc/terms/"
+> xmlns:foaf="http://xmlns.com/foaf/0.1/"
+> xmlns:owl="http://www.w3.org/2002/07/owl#"
+> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+> xmlns:skos="http://www.w3.org/2004/02/skos/core#"
+> xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+>
+> <owl:Ontology rdf:about="http://www.w3.org/ns/auth/cert#">
+> <owl:versionInfo>1.0</owl:versionInfo>
+> <rdfs:seeAlso rdf:resource="http://www.w3.org/2005/Incubator/webid/"/>
+> <rdfs:comment>Ontology for Certificates and crypto stuff.</rdfs:comment>
+> <dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+> <dc:title>The Cert Ontology</dc:title>
+> </owl:Ontology>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#Certificate">
+> <rdfs:label>Certificate</rdfs:label>
+> <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: (1) A public key. (2) Certificate information. 'Identity' information about the user, such as name, user ID, and so on. (3) One or more digital signatures.'</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://xmlns.com/foaf/0.1/Document"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#Key">
+> <rdfs:label>Key</rdfs:label>
+> <rdfs:comment>the class of keys</rdfs:comment>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PGPCertificate">
+> <rdfs:label>PGP Certificate</rdfs:label>
+> <rdfs:comment>the class of PGP Certificates</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Certificate"/>
+> <owl:equivalentClass rdf:resource="http://xmlns.com/wot/0.1/PubKey"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PrivateKey">
+> <rdfs:label>Private Key</rdfs:label>
+> <rdfs:comment>Private Key</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Key"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PublicKey">
+> <rdfs:label>Public Key</rdfs:label>
+> <rdfs:comment>Public Key</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Key"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#Signature">
+> <rdfs:label>Signature</rdfs:label>
+> <rdfs:comment>the class of signtatures</rdfs:comment>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#X509Certificate">
+> <rdfs:label>Certificate</rdfs:label>
+> <rdfs:comment>the class of X509 Certificates</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Certificate"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/auth/cert#decimal">
+> <rdfs:label>decimal</rdfs:label>
+> <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+> <rdfs:comment>An encoding of an integer in base 10 notation. Use cert:int instead.</rdfs:comment>
+> <rdfs:domain rdf:resource="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"/>
+> <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
+> <vs:term_status>archaic</vs:term_status>
+> </owl:DatatypeProperty>
+>
+> <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/auth/cert#hex">
+> <rdfs:label>hex</rdfs:label>
+> <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#InverseFunctionalProperty"/>
+> <rdfs:comment>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.
+> 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 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 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. The letters can be uppercase or lowercase, or mixed.
+> 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 ofthe 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) In order to make this fun, we allow any unicode characters in the string. A parser should 1. remove all non hexadecimal characters
+> 2. treat the resulting as a hexadecimal representation of a number This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.</rdfs:comment>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:DatatypeProperty>
+>
+> <owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/cert#identity">
+> <rdfs:label>identity</rdfs:label>
+> <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. It can be an Agent, or an idirect identifier of an agent such as a foaf:OnlineAccount .
+> Should one specify the range as being the union of those two classes, or should one leave this open?</rdfs:comment>
+> <rdfs:domain rdf:resource="http://www.w3.org/ns/auth/cert#PublicKey"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:ObjectProperty>
+>
+> <owl:DatatypeProperty rdf:about="http://www.w3.org/ns/auth/cert#int">
+> <rdfs:label>int</rdfs:label>
+> <rdfs:comment>A positive integer in base 10 notation. xsd:nonNegativeInteger could be used, but is a bit long to write, and may be too strictly defined.
+> This is here to provice a pair with cert:hex, to avoid needing to import a new namespace, and to give a bit more flexibility in the future.</rdfs:comment>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:DatatypeProperty>
+>
+> <owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/cert#public_key">
+> <rdfs:label>public key</rdfs:label>
+> <rdfs:comment>relates the private key to the public key component, in a public/private key pair.</rdfs:comment>
+> <rdfs:domain rdf:resource="http://www.w3.org/ns/auth/cert#PrivateKey"/>
+> <rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#PublicKey"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:ObjectProperty>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/diff/rsa Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,85 @@
+
+<!-- Processed by Id: cwm.py,v 1.197 2007/12/13 15:38:39 syosi Exp -->
+<!-- using base file:///Users/hjs/Programming/w3.org/WWW/ns/auth/rsa.n3-->
+
+
+<rdf:RDF xmlns="http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:dc="http://purl.org/dc/terms/"
+ xmlns:foaf="http://xmlns.com/foaf/0.1/"
+ xmlns:owl="http://www.w3.org/2002/07/owl#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+
+ <owl:Ontology rdf:about="rsa">
+ <dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+ <comment>ontology for the RSA public private keys </comment>
+ <seeAlso rdf:resource="X509Uml.svg"/>
+ <seeAlso rdf:resource="http://en.wikipedia.org/wiki/RSA"/>
+ <seeAlso rdf:resource="http://lists.foaf-project.org/mailman/listinfo/foaf-protocols"/>
+ <vs:term_status>unstable</vs:term_status>
+ <foaf:maker rdf:resource="http://bblfish.net/people/henry/card#me"/>
+ </owl:Ontology>
+
+ <rdf:Description rdf:about="rsa#RSAKey">
+ <comment>
+ The union of the public and private components of an RSAKey.
+ Usually those pieces are not kept together
+ </comment>
+ <subClassOf rdf:resource="cert#Key"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Description>
+
+ <rdf:Description rdf:about="rsa#RSAPrivateKey">
+ <comment>
+ A Private Key in the RSA framework
+ </comment>
+ <seeAlso rdf:resource="http://en.wikipedia.org/wiki/RSA"/>
+ <subClassOf rdf:resource="cert#PrivateKey"/>
+ <subClassOf rdf:resource="rsa#RSAKey"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Description>
+
+ <rdf:Description rdf:about="rsa#RSAPublicKey">
+ <comment>
+ The RSA public key. Padded message m are encrypted by applying the function
+ modulus(power(m,exponent),modulus)
+ </comment>
+ <seeAlso rdf:resource="http://en.wikipedia.org/wiki/RSA"/>
+ <subClassOf rdf:resource="cert#PublicKey"/>
+ <subClassOf rdf:resource="rsa#RSAKey"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Description>
+
+ <rdf:Property rdf:about="rsa#modulus">
+ <comment>
+ The modulus of an RSA public and private key.
+ This is defined as n = p*q
+ </comment>
+ <domain rdf:resource="rsa#RSAKey"/>
+ <range rdf:resource="cert#int"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Property>
+
+ <rdf:Property rdf:about="rsa#private_exponent">
+ <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'
+ </comment>
+ <domain rdf:resource="rsa#RSAPrivateKey"/>
+ <range rdf:resource="cert#int"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Property>
+
+ <rdf:Property rdf:about="rsa#public_exponent">
+ <comment>
+ The exponent used to encrypt the message. Number chosen between
+ 1 and the totient(p*q). Often named 'e' .
+ </comment>
+ <domain rdf:resource="rsa#RSAPublicKey"/>
+ <range rdf:resource="cert#int"/>
+ <vs:term_status>unstable</vs:term_status>
+ </rdf:Property>
+</rdf:RDF>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/diff/rsa_diff Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,152 @@
+1,5d0
+<
+< <!-- Processed by Id: cwm.py,v 1.197 2007/12/13 15:38:39 syosi Exp -->
+< <!-- using base file:///Users/hjs/Programming/w3.org/WWW/ns/auth/rsa.n3-->
+<
+<
+7,84c2,65
+< xmlns:dc="http://purl.org/dc/terms/"
+< xmlns:foaf="http://xmlns.com/foaf/0.1/"
+< xmlns:owl="http://www.w3.org/2002/07/owl#"
+< xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+< xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+< xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+<
+< <owl:Ontology rdf:about="rsa">
+< <dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+< <comment>ontology for the RSA public private keys </comment>
+< <seeAlso rdf:resource="X509Uml.svg"/>
+< <seeAlso rdf:resource="http://en.wikipedia.org/wiki/RSA"/>
+< <seeAlso rdf:resource="http://lists.foaf-project.org/mailman/listinfo/foaf-protocols"/>
+< <vs:term_status>unstable</vs:term_status>
+< <foaf:maker rdf:resource="http://bblfish.net/people/henry/card#me"/>
+< </owl:Ontology>
+<
+< <rdf:Description rdf:about="rsa#RSAKey">
+< <comment>
+< The union of the public and private components of an RSAKey.
+< Usually those pieces are not kept together
+< </comment>
+< <subClassOf rdf:resource="cert#Key"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Description>
+<
+< <rdf:Description rdf:about="rsa#RSAPrivateKey">
+< <comment>
+< A Private Key in the RSA framework
+< </comment>
+< <seeAlso rdf:resource="http://en.wikipedia.org/wiki/RSA"/>
+< <subClassOf rdf:resource="cert#PrivateKey"/>
+< <subClassOf rdf:resource="rsa#RSAKey"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Description>
+<
+< <rdf:Description rdf:about="rsa#RSAPublicKey">
+< <comment>
+< The RSA public key. Padded message m are encrypted by applying the function
+< modulus(power(m,exponent),modulus)
+< </comment>
+< <seeAlso rdf:resource="http://en.wikipedia.org/wiki/RSA"/>
+< <subClassOf rdf:resource="cert#PublicKey"/>
+< <subClassOf rdf:resource="rsa#RSAKey"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Description>
+<
+< <rdf:Property rdf:about="rsa#modulus">
+< <comment>
+< The modulus of an RSA public and private key.
+< This is defined as n = p*q
+< </comment>
+< <domain rdf:resource="rsa#RSAKey"/>
+< <range rdf:resource="cert#int"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Property>
+<
+< <rdf:Property rdf:about="rsa#private_exponent">
+< <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'
+< </comment>
+< <domain rdf:resource="rsa#RSAPrivateKey"/>
+< <range rdf:resource="cert#int"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Property>
+<
+< <rdf:Property rdf:about="rsa#public_exponent">
+< <comment>
+< The exponent used to encrypt the message. Number chosen between
+< 1 and the totient(p*q). Often named 'e' .
+< </comment>
+< <domain rdf:resource="rsa#RSAPublicKey"/>
+< <range rdf:resource="cert#int"/>
+< <vs:term_status>unstable</vs:term_status>
+< </rdf:Property>
+---
+> xmlns:dc="http://purl.org/dc/terms/"
+> xmlns:foaf="http://xmlns.com/foaf/0.1/"
+> xmlns:owl="http://www.w3.org/2002/07/owl#"
+> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+> xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+>
+> <owl:Ontology rdf:about="http://www.w3.org/ns/auth/rsa#">
+> <owl:versionInfo>1.0</owl:versionInfo>
+> <rdfs:seeAlso rdf:resource="http://www.w3.org/2005/Incubator/webid/"/>
+> <rdfs:comment>Ontology for the RSA public private keys.</rdfs:comment>
+> <dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+> <dc:title>The RSA Ontology</dc:title>
+> </owl:Ontology>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/rsa#RSAKey">
+> <rdfs:label>RSA Key</rdfs:label>
+> <rdfs:comment>The union of the public and private components of an RSAKey. Usually those pieces are not kept together.</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Key"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/rsa#RSAPrivateKey">
+> <rdfs:label>RSA Private Key</rdfs:label>
+> <rdfs:comment>A Private Key in the RSA framework</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#PrivateKey"/>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/rsa#RSAKey"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/rsa#RSAPublicKey">
+> <rdfs:label>RSA Public Key</rdfs:label>
+> <rdfs:comment>The RSA public key. Padded message m are encrypted by applying the function modulus(power(m,exponent),modulus).</rdfs:comment>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#PublicKey"/>
+> <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/rsa#RSAKey"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:Class>
+>
+> <owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/rsa#modulus">
+> <rdfs:label>modulus</rdfs:label>
+> <rdfs:comment>The modulus of an RSA public and private key. This is defined as n = p*q.</rdfs:comment>
+> <rdfs:domain rdf:resource="http://www.w3.org/ns/auth/rsa#RSAKey"/>
+> <rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#int"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:ObjectProperty>
+>
+> <owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/rsa#private_exponent">
+> <rdfs:label>private exponent</rdfs:label>
+> <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'</rdfs:comment>
+> <rdfs:domain rdf:resource="http://www.w3.org/ns/auth/rsa#RSAPrivateKey"/>
+> <rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#int"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:ObjectProperty>
+>
+> <owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/rsa#public_exponent">
+> <rdfs:label>public exponent</rdfs:label>
+> <rdfs:comment>The exponent used to encrypt the message. Number chosen between 1 and the totient(p*q). Often named 'e'.</rdfs:comment>
+> <rdfs:domain rdf:resource="http://www.w3.org/ns/auth/rsa#RSAPublicKey"/>
+> <rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#int"/>
+> <vs:term_status>unstable</vs:term_status>
+> </owl:ObjectProperty>
+>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PrivateKey"><rdfs:label>Private Key</rdfs:label></owl:Class>
+> <owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PublicKey"><rdfs:label>Public Key</rdfs:label></owl:Class>
+85a67
+>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/modified/rsa.owl Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,67 @@
+<rdf:RDF xmlns="http://www.w3.org/2000/01/rdf-schema#"
+xmlns:dc="http://purl.org/dc/terms/"
+xmlns:foaf="http://xmlns.com/foaf/0.1/"
+xmlns:owl="http://www.w3.org/2002/07/owl#"
+xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#">
+
+<owl:Ontology rdf:about="http://www.w3.org/ns/auth/rsa#">
+<owl:versionInfo>1.0</owl:versionInfo>
+<rdfs:seeAlso rdf:resource="http://www.w3.org/2005/Incubator/webid/"/>
+<rdfs:comment>Ontology for the RSA public private keys.</rdfs:comment>
+<dc:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2008-11-13</dc:created>
+<dc:title>The RSA Ontology</dc:title>
+</owl:Ontology>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/rsa#RSAKey">
+<rdfs:label>RSA Key</rdfs:label>
+<rdfs:comment>The union of the public and private components of an RSAKey. Usually those pieces are not kept together.</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#Key"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/rsa#RSAPrivateKey">
+<rdfs:label>RSA Private Key</rdfs:label>
+<rdfs:comment>A Private Key in the RSA framework</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#PrivateKey"/>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/rsa#RSAKey"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/rsa#RSAPublicKey">
+<rdfs:label>RSA Public Key</rdfs:label>
+<rdfs:comment>The RSA public key. Padded message m are encrypted by applying the function modulus(power(m,exponent),modulus).</rdfs:comment>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/cert#PublicKey"/>
+<rdfs:subClassOf rdf:resource="http://www.w3.org/ns/auth/rsa#RSAKey"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:Class>
+
+<owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/rsa#modulus">
+<rdfs:label>modulus</rdfs:label>
+<rdfs:comment>The modulus of an RSA public and private key. This is defined as n = p*q.</rdfs:comment>
+<rdfs:domain rdf:resource="http://www.w3.org/ns/auth/rsa#RSAKey"/>
+<rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#int"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:ObjectProperty>
+
+<owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/rsa#private_exponent">
+<rdfs:label>private exponent</rdfs:label>
+<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'</rdfs:comment>
+<rdfs:domain rdf:resource="http://www.w3.org/ns/auth/rsa#RSAPrivateKey"/>
+<rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#int"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:ObjectProperty>
+
+<owl:ObjectProperty rdf:about="http://www.w3.org/ns/auth/rsa#public_exponent">
+<rdfs:label>public exponent</rdfs:label>
+<rdfs:comment>The exponent used to encrypt the message. Number chosen between 1 and the totient(p*q). Often named 'e'.</rdfs:comment>
+<rdfs:domain rdf:resource="http://www.w3.org/ns/auth/rsa#RSAPublicKey"/>
+<rdfs:range rdf:resource="http://www.w3.org/ns/auth/cert#int"/>
+<vs:term_status>unstable</vs:term_status>
+</owl:ObjectProperty>
+
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PrivateKey"><rdfs:label>Private Key</rdfs:label></owl:Class>
+<owl:Class rdf:about="http://www.w3.org/ns/auth/cert#PublicKey"><rdfs:label>Public Key</rdfs:label></owl:Class>
+</rdf:RDF>
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/proof/compare_n3_xml.py Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,69 @@
+# -*- coding: utf-8 -*-
+
+from rdflib.graph import Graph, ConjunctiveGraph, ReadOnlyGraphAggregate
+from rdflib.term import BNode
+import hashlib
+import sys
+import urllib
+
+try:
+ owl_url = sys.argv[1]
+ rdfa_url = sys.argv[2]
+ try:
+ owl_compare = sys.argv[3]
+ except IndexError:
+ owl_compare = "fileowl.nt"
+ try:
+ rdfa_compare = sys.argv[4]
+ except IndexError:
+ rdfa_compare = "filerdfa.nt"
+except IndexError:
+ print "Enter two URLs"
+ print "comp.py http://example.org/one.owl http://example.com/two.html [fileowl.nt] [filerdfa.nt]"
+ sys.exit(2)
+
+try:
+ urllib.urlopen(owl_url)
+ urllib.urlopen(rdfa_url)
+except IOError:
+ print "Not a real URL"
+ print "comp.py http://example.org/one.owl http://example.com/two.n3 [fileowl.nt] [filerdfa.nt]"
+ sys.exit(2)
+
+g1 = Graph().parse(owl_url, format='xml')
+g2 = Graph().parse(rdfa_url, format='n3')
+
+
+#OWL - RDF/XML to N-Triples
+file = open(owl_compare, 'w')
+for l in sorted(g1.serialize(format='nt').splitlines()):
+ if l:
+ file.write(l)
+ file.write("\n")
+file.close()
+
+#N3 to N-Triples
+file = open(rdfa_compare, 'w')
+for l in sorted(g2.serialize(format='nt').splitlines()):
+ if l:
+ file.write(l)
+ file.write("\n")
+file.close()
+
+
+print "SHA224 of N-Triples from XML/RDF:"
+owl_nt = open(owl_compare, 'r').read()
+owl_hash = hashlib.sha224(owl_nt).hexdigest()
+file.close()
+print owl_hash
+
+print "\nSHA224 of N-Triples from N3:"
+rdfa_nt = open(rdfa_compare, 'r').read()
+rdfa_hash = hashlib.sha224(rdfa_nt).hexdigest()
+file.close()
+print rdfa_hash
+
+if owl_hash == rdfa_hash:
+ print "\nVocabularies are the same"
+else:
+ print "\nVocabularies are NOT the same"
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/proof/compare_rdfa_xml.sh Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,27 @@
+#!/bin/bash
+
+if [ "$#" -ne 2 ]
+ then
+ echo "Usage:"
+ echo "$0 http://example.org/1.html http://example.org/2.owl"
+ echo ""
+ echo "Params:"
+ echo " http://example.org/1.html XHTML+RDFa"
+ echo " http://example.org/2.owl RDF/XML"
+ exit
+fi
+
+rapper -q -i rdfa $1 > unsortrdfa.txt
+rapper -q -i rdfxml $2 > unsortowl.txt
+sort unsortrdfa.txt > sortrdfa.txt
+sort unsortowl.txt > sortowl.txt
+rdfa=`md5sum sortrdfa.txt | awk '{ print $1 }'`
+owl=`md5sum sortowl.txt | awk '{ print $1 }'`
+#echo $rdfa
+#echo $owl
+if [ "$rdfa" = "$owl" ]
+ then
+ echo 'Graphs are the same'
+ else
+ echo 'Graphs are NOT the same'
+fi
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/rdfa/cert.html Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,388 @@
+<?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#"
+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");
+</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>)</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>)</dd>
+
+<dt>Authors:</dt>
+<dd><a href="http://ii.uwb.edu.pl/~dtomaszuk/">Dominik Tomaszuk</a> (<a href="http://ii.uwb.edu.pl/">University of Bialystok</a>)</dd>
+<dd><a href="http://bblfish.net/">Henry Story</a> </dd>
+</dl>
+
+<p class="copyright"><span>Copyright © 2010-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.</span></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>Classes: | <a href="#Certificate">Certificate</a> | <a href="#Key">Key</a> | <a href="#PGPCertificate">PGPCertificate</a> | <a href="#PrivateKey">PrivateKey</a> | <a href="#PublicKey">PublicKey</a> | <a href="#Signature">Signature</a> | <a href="#X509Certificate">X509Certificate</a> |
+</p>
+<p>Properties: | <a href="#decimal">decimal</a> | <a href="#hex">hex</a> | <a href="#identity">identity</a> | <a href="#int">int</a> | <a href="#public_key">public_key</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> @prefix cert: <http://www.w3.org/ns/auth/cert#> .
+ @prefix rsa: <http://www.w3.org/ns/auth/rsa#> .
+ @prefix foaf: <http://xmlns.com/foaf/0.1/> .
+ @prefix : <https://joe.example/profile#> .
+
+ :me a foaf:Person;
+ foaf:name "Joe" .
+
+ [] a rsa:RSAPublicKey;
+ rsa:modulus """
+ 00:cb:24:ed:85:d6:4d:79:4b:69:c7:01:c1:86:ac:
+ c0:59:50:1e:85:60:00:f6:61:c9:32:04:d8:38:0e:
+ 07:19:1c:5c:8b:36:8d:2a:c3:2a:42:8a:cb:97:03:
+ 98:66:43:68:dc:2a:86:73:20:22:0f:75:5e:99:ca:
+ 2e:ec:da:e6:2e:8d:15:fb:58:e1:b7:6a:e5:9c:b7:
+ ac:e8:83:83:94:d5:9e:72:50:b4:49:17:6e:51:a4:
+ 94:95:1a:1c:36:6c:62:17:d8:76:8d:68:2d:de:78:
+ dd:4d:55:e6:13:f8:83:9c:f2:75:d4:c8:40:37:43:
+ e7:86:26:01:f3:c4:9a:63:66:e1:2b:b8:f4:98:26:
+ 2c:3c:77:de:19:bc:e4:0b:32:f8:9a:e6:2c:37:80:
+ f5:b6:27:5b:e3:37:e2:b3:15:3a:e2:ba:72:a9:97:
+ 5a:e7:1a:b7:24:64:94:97:06:6b:66:0f:cf:77:4b:
+ 75:43:d9:80:95:2d:2e:85:86:20:0e:da:41:58:b0:
+ 14:e7:54:65:d9:1e:cf:93:ef:c7:ac:17:0c:11:fc:
+ 72:46:fc:6d:ed:79:c3:77:80:00:0a:c4:e0:79:f6:
+ 71:fd:4f:20:7a:d7:70:80:9e:0e:2d:7b:0e:f5:49:
+ 3b:ef:e7:35:44:d8:e1:be:3d:dd:b5:24:55:c6:13:
+ 91:a1
+ """^^cert:hex;
+ rsa:public_exponent "65537"^^cert:int;
+ cert:identity :me .
+</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>Classes: | <a href="#Certificate">Certificate</a> | <a href="#Key">Key</a> | <a href="#PGPCertificate">PGPCertificate</a> | <a href="#PrivateKey">PrivateKey</a> | <a href="#PublicKey">PublicKey</a> | <a href="#Signature">Signature</a> | <a href="#X509Certificate">X509Certificate</a> |
+</p>
+<p>Properties: | <a href="#decimal">decimal</a> | <a href="#hex">hex</a> | <a href="#identity">identity</a> | <a href="#int">int</a> | <a href="#public_key">public_key</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: http://www.w3.org/ns/auth/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: (1) A public key. (2) Certificate information. 'Identity' information about the user, such as name, user ID, and so on. (3) One or more digital signatures.'</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th>Sub class of</th>
+ <td> <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>
+ </td></tr><tr><th>Has sub class</th>
+ <td> <a href="#X509Certificate">Certificate</a>
+ <a href="#PGPCertificate">PGP Certificate</a>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <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="Key" about="http://www.w3.org/ns/auth/cert#Key" typeof="owl:Class">
+ <h4>Class: http://www.w3.org/ns/auth/cert#:Key</h4>
+ <em property="rdfs:label" >Key</em> - <span property="rdfs:comment" >the class of keys</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th>Has sub class</th>
+ <td> <a href="#PublicKey">Public Key</a>
+ <a href="#PrivateKey">Private Key</a>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <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="PGPCertificate" about="http://www.w3.org/ns/auth/cert#PGPCertificate" typeof="owl:Class">
+ <h4>Class: http://www.w3.org/ns/auth/cert#:PGPCertificate</h4>
+ <em property="rdfs:label" >PGP Certificate</em> - <span property="rdfs:comment" >the class of PGP Certificates</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Certificate"><a href="#Certificate">Certificate</a></span>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <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="PrivateKey" about="http://www.w3.org/ns/auth/cert#PrivateKey" typeof="owl:Class">
+ <h4>Class: http://www.w3.org/ns/auth/cert#:PrivateKey</h4>
+ <em property="rdfs:label" >Private Key</em> - <span property="rdfs:comment" >Private Key</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Properties include:</th>
+ <td> <a href="#public_key">public_key</a>
+ </td></tr>
+ <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Key"><a href="#Key">Key</a></span>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#PrivateKey">#</a>] <!-- PrivateKey --> [<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: http://www.w3.org/ns/auth/cert#:PublicKey</h4>
+ <em property="rdfs:label" >Public Key</em> - <span property="rdfs:comment" >Public Key</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Properties include:</th>
+ <td> <a href="#identity">identity</a>
+ </td></tr>
+ <tr><th>Used with:</th>
+ <td> <a href="#public_key">public_key</a>
+</td></tr> <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Key"><a href="#Key">Key</a></span>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <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="Signature" about="http://www.w3.org/ns/auth/cert#Signature" typeof="owl:Class">
+ <h4>Class: http://www.w3.org/ns/auth/cert#:Signature</h4>
+ <em property="rdfs:label" >Signature</em> - <span property="rdfs:comment" >the class of signtatures</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <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: http://www.w3.org/ns/auth/cert#:X509Certificate</h4>
+ <em property="rdfs:label" >Certificate</em> - <span property="rdfs:comment" >the class of X509 Certificates</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Certificate"><a href="#Certificate">Certificate</a></span>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#X509Certificate">#</a>] <!-- X509Certificate --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div>
+<h3>Properties</h3>
+
+
+<div class="specterm" id="hex" about="http://www.w3.org/ns/auth/cert#hex" typeof="owl:InverseFunctionalProperty">
+ <h4>Property: http://www.w3.org/ns/auth/cert#:hex</h4>
+ <em property="rdfs:label" >hex</em> - <span property="rdfs:comment" >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.
+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 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 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. The letters can be uppercase or lowercase, or mixed.
+ 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 ofthe 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) In order to make this fun, we allow any unicode characters in the string. A parser should 1. remove all non hexadecimal characters
+2. treat the resulting as a hexadecimal representation of a number This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th colspan="2">Datatype Property</th>
+ <td> <span rel="rdf:type" href="http://www.w3.org/2002/07/owl#DatatypeProperty"></span> </td></tr><tr><th colspan="2">Inverse Functional Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#hex">#</a>] <!-- hex --> [<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: http://www.w3.org/ns/auth/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. It can be an Agent, or an idirect identifier of an agent such as a foaf:OnlineAccount .
+Should one specify the range as being the union of those two classes, or should one leave this open?</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Domain:</th>
+ <td> <span rel="rdfs:domain" href="http://www.w3.org/ns/auth/cert#PublicKey"><a href="#PublicKey">Public Key</a></span>
+</td></tr>
+ <tr><th colspan="2">Object Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#identity">#</a>] <!-- identity --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div><div class="specterm" id="int" about="http://www.w3.org/ns/auth/cert#int" typeof="owl:DatatypeProperty">
+ <h4>Property: http://www.w3.org/ns/auth/cert#:int</h4>
+ <em property="rdfs:label" >int</em> - <span property="rdfs:comment" >A positive integer in base 10 notation. xsd:nonNegativeInteger could be used, but is a bit long to write, and may be too strictly defined.
+This is here to provice a pair with cert:hex, to avoid needing to import a new namespace, and to give a bit more flexibility in the future.</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+
+ <tr><th colspan="2">Datatype Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#int">#</a>] <!-- int --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div><div class="specterm" id="public_key" about="http://www.w3.org/ns/auth/cert#public_key" typeof="owl:ObjectProperty">
+ <h4>Property: http://www.w3.org/ns/auth/cert#:public_key</h4>
+ <em property="rdfs:label" >public key</em> - <span property="rdfs:comment" >relates the private key to the public key component, in a public/private key pair.</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Domain:</th>
+ <td> <span rel="rdfs:domain" href="http://www.w3.org/ns/auth/cert#PrivateKey"><a href="#PrivateKey">Private Key</a></span>
+</td></tr>
+ <tr><th>Range:</th>
+ <td> <span rel="rdfs:range" href="http://www.w3.org/ns/auth/cert#PublicKey"><a href="#PublicKey">Public Key</a></span>
+</td> </tr><tr><th colspan="2">Object Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#public_key">#</a>] <!-- public_key --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div>
+<div class="specterm" id="decimal" about="http://www.w3.org/ns/auth/cert#decimal" typeof="owl:InverseFunctionalProperty">
+ <h4>Property: http://www.w3.org/ns/auth/cert#:decimal</h4>
+ <em property="rdfs:label" >decimal</em> - <span property="rdfs:comment" >An encoding of an integer in base 10 notation. Use cert:int instead.</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >archaic</span></td></tr>
+ <tr><th>Domain:</th>
+ <td> <span rel="rdfs:domain" href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger"><a href="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">xsd:nonNegativeInteger</a></span>
+ </td></tr>
+ <tr><th>Range:</th>
+ <td> <span rel="rdfs:range" href="http://www.w3.org/2001/XMLSchema#string"><a href="http://www.w3.org/2001/XMLSchema#string">xsd:string</a></span>
+ </td></tr><tr><th colspan="2">Datatype Property</th>
+ <td> <span rel="rdf:type" href="http://www.w3.org/2002/07/owl#DatatypeProperty"></span> </td></tr><tr><th colspan="2">Inverse Functional Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#decimal">#</a>] <!-- decimal --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div>
+
+
+
+
+
+
+
+</div>
+</div>
+
+<!-- dirty hack for specgen -->
+<span about="http://www.w3.org/ns/auth/cert#PGPCertificate" rel="owl:equivalentClass" href="http://xmlns.com/wot/0.1/PubKey"></span>
+
+
+<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>
+</ul>
+
+</body>
+</html>
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/rdfa/rsa.html Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,301 @@
+<?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#"
+version="XHTML+RDFa 1.0" typeof="owl:Ontology" about="http://www.w3.org/ns/auth/rsa#">
+<head>
+<title>The RSA 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");
+</style>
+</head>
+
+<body>
+<h1><span property="dc:title" about="http://www.w3.org/ns/auth/rsa#">The RSA Ontology</span> <span property="owl:versionInfo" about="http://www.w3.org/ns/auth/rsa#">1.0</span></h1>
+
+<h2>Namespace Document <span property="dc:created" about="http://www.w3.org/ns/auth/rsa#" 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/rsa#">http://www.w3.org/ns/auth/rsa#</a> (<a href="http://www.w3.org/ns/auth/rsa.n3">N3</a>)</dd>
+
+<dt>Latest version:</dt>
+<dd><a href="http://www.w3.org/ns/auth/rsa#">http://www.w3.org/ns/auth/rsa#</a> (<a href="http://www.w3.org/ns/auth/rsa.n3">N3</a>)</dd>
+
+<dt>Authors:</dt>
+<dd><a href="http://ii.uwb.edu.pl/~dtomaszuk/">Dominik Tomaszuk</a> (<a href="http://ii.uwb.edu.pl/">University of Bialystok</a>)</dd>
+<dd><a href="http://bblfish.net/">Henry Story</a> </dd>
+</dl>
+
+<p class="copyright"><span>Copyright © 2010-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.</span></p>
+
+<hr />
+
+<h2 id="sec-status">Abstract</h2>
+<p about="http://www.w3.org/ns/auth/rsa#" property="rdfs:comment">Ontology for the RSA public private keys.</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/rsa#" 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 RSA Ontology at a glance</a></li>
+<li><a href="#sec-example">Examples</a></li>
+<li><a href="#sec-crossref">Cross-reference for Cert classes and properties</a></li>
+<li><a href="#sec-ack">Acknowledgments</a></li>
+</ul>
+
+
+<a id="sec-glance"></a>
+<h2 id="glance">The Ontology at a glance</h2>
+
+<p>An a-z index of <em>RSA Ontology</em> terms, by class (categories or types) and by property.</p>
+
+
+<div class="azlist">
+<p>Classes: | <a href="#RSAKey">RSAKey</a> | <a href="#RSAPrivateKey">RSAPrivateKey</a> | <a href="#RSAPublicKey">RSAPublicKey</a> |
+</p>
+<p>Properties: | <a href="#modulus">modulus</a> | <a href="#private_exponent">private_exponent</a> | <a href="#public_exponent">public_exponent</a> |
+</p>
+</div>
+
+<div style="clear: left;"></div>
+
+<div style="clear: left;"></div>
+
+
+<!-- ================================================================== -->
+
+
+
+
+<p>
+The evolution of the <em>RSA 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>@prefix cert: <http://www.w3.org/ns/auth/cert#> .
+ @prefix rsa: <http://www.w3.org/ns/auth/rsa#> .
+ @prefix foaf: <http://xmlns.com/foaf/0.1/> .
+ @prefix : <https://joe.example/profile#> .
+
+ :me a foaf:Person;
+ foaf:name "Joe" .
+
+ [] a rsa:RSAPublicKey;
+ rsa:modulus """
+ 00:cb:24:ed:85:d6:4d:79:4b:69:c7:01:c1:86:ac:
+ c0:59:50:1e:85:60:00:f6:61:c9:32:04:d8:38:0e:
+ 07:19:1c:5c:8b:36:8d:2a:c3:2a:42:8a:cb:97:03:
+ 98:66:43:68:dc:2a:86:73:20:22:0f:75:5e:99:ca:
+ 2e:ec:da:e6:2e:8d:15:fb:58:e1:b7:6a:e5:9c:b7:
+ ac:e8:83:83:94:d5:9e:72:50:b4:49:17:6e:51:a4:
+ 94:95:1a:1c:36:6c:62:17:d8:76:8d:68:2d:de:78:
+ dd:4d:55:e6:13:f8:83:9c:f2:75:d4:c8:40:37:43:
+ e7:86:26:01:f3:c4:9a:63:66:e1:2b:b8:f4:98:26:
+ 2c:3c:77:de:19:bc:e4:0b:32:f8:9a:e6:2c:37:80:
+ f5:b6:27:5b:e3:37:e2:b3:15:3a:e2:ba:72:a9:97:
+ 5a:e7:1a:b7:24:64:94:97:06:6b:66:0f:cf:77:4b:
+ 75:43:d9:80:95:2d:2e:85:86:20:0e:da:41:58:b0:
+ 14:e7:54:65:d9:1e:cf:93:ef:c7:ac:17:0c:11:fc:
+ 72:46:fc:6d:ed:79:c3:77:80:00:0a:c4:e0:79:f6:
+ 71:fd:4f:20:7a:d7:70:80:9e:0e:2d:7b:0e:f5:49:
+ 3b:ef:e7:35:44:d8:e1:be:3d:dd:b5:24:55:c6:13:
+ 91:a1
+ """^^cert:hex;
+ rsa:public_exponent "65537"^^cert:int;
+ cert:identity :me .
+</pre>
+
+<h2 id="sec-crossref">Cross-reference for Cert classes and properties</h2>
+
+<p>The <em>RSA 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>Classes: | <a href="#RSAKey">RSAKey</a> | <a href="#RSAPrivateKey">RSAPrivateKey</a> | <a href="#RSAPublicKey">RSAPublicKey</a> |
+</p>
+<p>Properties: | <a href="#modulus">modulus</a> | <a href="#private_exponent">private_exponent</a> | <a href="#public_exponent">public_exponent</a> |
+</p>
+</div>
+
+<!-- and this is the bulk of the vocab descriptions -->
+<div class="termlist"><h3>Classes and Properties (full detail)</h3>
+<div class='termdetails'><br />
+
+<h2>Classes</h2>
+
+
+<div class="specterm" id="RSAKey" about="http://www.w3.org/ns/auth/rsa#RSAKey" typeof="owl:Class">
+ <h3>Class: http://www.w3.org/ns/auth/rsa#:RSAKey</h3>
+ <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 /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Properties include:</th>
+ <td> <a href="#modulus">modulus</a>
+ </td></tr>
+ <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#Key"><a href="http://www.w3.org/ns/auth/cert#Key">http://www.w3.org/ns/auth/cert#:Key</a></span>
+ </td></tr><tr><th>Has sub class</th>
+ <td> <a href="#RSAPublicKey">RSA Public Key</a>
+ <a href="#RSAPrivateKey">RSA Private Key</a>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <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="RSAPrivateKey" about="http://www.w3.org/ns/auth/rsa#RSAPrivateKey" typeof="owl:Class">
+ <h3>Class: http://www.w3.org/ns/auth/rsa#:RSAPrivateKey</h3>
+ <em property="rdfs:label" >RSA Private Key</em> - <span property="rdfs:comment" >A Private Key in the RSA framework</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Properties include:</th>
+ <td> <a href="#private_exponent">private_exponent</a>
+ </td></tr>
+ <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#PrivateKey"><a href="#PrivateKey">Private Key</a></span>
+ <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/rsa#RSAKey"><a href="#RSAKey">RSA Key</a></span>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#RSAPrivateKey">#</a>] <!-- RSAPrivateKey --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div><div class="specterm" id="RSAPublicKey" about="http://www.w3.org/ns/auth/rsa#RSAPublicKey" typeof="owl:Class">
+ <h3>Class: http://www.w3.org/ns/auth/rsa#:RSAPublicKey</h3>
+ <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 /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Properties include:</th>
+ <td> <a href="#public_exponent">public_exponent</a>
+ </td></tr>
+ <tr><th>Sub class of</th>
+ <td> <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/cert#PublicKey"><a href="#PublicKey">Public Key</a></span>
+ <span rel="rdfs:subClassOf" href="http://www.w3.org/ns/auth/rsa#RSAKey"><a href="#RSAKey">RSA Key</a></span>
+ </td></tr><tr><th colspan="2">OWL Class</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#RSAPublicKey">#</a>] <!-- RSAPublicKey --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div>
+<h2>Properties</h2>
+
+
+<div class="specterm" id="modulus" about="http://www.w3.org/ns/auth/rsa#modulus" typeof="owl:ObjectProperty">
+ <h3>Property: http://www.w3.org/ns/auth/rsa#:modulus</h3>
+ <em property="rdfs:label" >modulus</em> - <span property="rdfs:comment" >The modulus of an RSA public and private key. This is defined as n = p*q.</span> <br /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Domain:</th>
+ <td> <span rel="rdfs:domain" href="http://www.w3.org/ns/auth/rsa#RSAKey"><a href="#RSAKey">RSA Key</a></span>
+</td></tr>
+ <tr><th>Range:</th>
+ <td> <span rel="rdfs:range" href="http://www.w3.org/ns/auth/cert#int"><a href="http://www.w3.org/ns/auth/cert#int">http://www.w3.org/ns/auth/cert#:int</a></span>
+ </td></tr><tr><th colspan="2">Object Property</th>
+ <td> </td></tr>
+ </table>
+
+ <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="private_exponent" about="http://www.w3.org/ns/auth/rsa#private_exponent" typeof="owl:ObjectProperty">
+ <h3>Property: http://www.w3.org/ns/auth/rsa#:private_exponent</h3>
+ <em property="rdfs:label" >private exponent</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 /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Domain:</th>
+ <td> <span rel="rdfs:domain" href="http://www.w3.org/ns/auth/rsa#RSAPrivateKey"><a href="#RSAPrivateKey">RSA Private Key</a></span>
+</td></tr>
+ <tr><th>Range:</th>
+ <td> <span rel="rdfs:range" href="http://www.w3.org/ns/auth/cert#int"><a href="http://www.w3.org/ns/auth/cert#int">http://www.w3.org/ns/auth/cert#:int</a></span>
+ </td></tr><tr><th colspan="2">Object Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#private_exponent">#</a>] <!-- private_exponent --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div><div class="specterm" id="public_exponent" about="http://www.w3.org/ns/auth/rsa#public_exponent" typeof="owl:ObjectProperty">
+ <h3>Property: http://www.w3.org/ns/auth/rsa#:public_exponent</h3>
+ <em property="rdfs:label" >public 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 /><table style="float: top;">
+ <tr><th>Status:</th>
+ <td><span property="vs:term_status" >unstable</span></td></tr>
+ <tr><th>Domain:</th>
+ <td> <span rel="rdfs:domain" href="http://www.w3.org/ns/auth/rsa#RSAPublicKey"><a href="#RSAPublicKey">RSA Public Key</a></span>
+</td></tr>
+ <tr><th>Range:</th>
+ <td> <span rel="rdfs:range" href="http://www.w3.org/ns/auth/cert#int"><a href="http://www.w3.org/ns/auth/cert#int">http://www.w3.org/ns/auth/cert#:int</a></span>
+ </td></tr><tr><th colspan="2">Object Property</th>
+ <td> </td></tr>
+ </table>
+
+ <p style="float: right; font-size: small;">[<a href="#public_exponent">#</a>] <!-- public_exponent --> [<a href="#glance">back to top</a>]</p>
+ <br/>
+ </div>
+
+
+
+
+</div>
+</div>
+
+<!-- other ns classes -->
+<span class="specterm" id="PrivateKey" about="http://www.w3.org/ns/auth/cert#PrivateKey" typeof="owl:Class"><span property="rdfs:label" content="Private Key"></span></span>
+<span class="specterm" id="PublicKey" about="http://www.w3.org/ns/auth/cert#PublicKey" typeof="owl:Class"><span property="rdfs:label" content="Public Key"></span></span>
+<h3 id="sec-ack">Acknowledgments</h3>
+
+<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>
+</ul>
+
+</body>
+</html>
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/rdfa/template_cert.html Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,175 @@
+<?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#"
+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");
+</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>)</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>)</dd>
+
+<dt>Authors:</dt>
+<dd><a href="http://ii.uwb.edu.pl/~dtomaszuk/">Dominik Tomaszuk</a> (<a href="http://ii.uwb.edu.pl/">University of Bialystok</a>)</dd>
+<dd><a href="http://bblfish.net/">Henry Story</a> </dd>
+</dl>
+
+<p class="copyright"><span>Copyright © 2010-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.</span></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>
+
+
+%s
+
+<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> @prefix cert: <http://www.w3.org/ns/auth/cert#> .
+ @prefix rsa: <http://www.w3.org/ns/auth/rsa#> .
+ @prefix foaf: <http://xmlns.com/foaf/0.1/> .
+ @prefix : <https://joe.example/profile#> .
+
+ :me a foaf:Person;
+ foaf:name "Joe" .
+
+ [] a rsa:RSAPublicKey;
+ rsa:modulus """
+ 00:cb:24:ed:85:d6:4d:79:4b:69:c7:01:c1:86:ac:
+ c0:59:50:1e:85:60:00:f6:61:c9:32:04:d8:38:0e:
+ 07:19:1c:5c:8b:36:8d:2a:c3:2a:42:8a:cb:97:03:
+ 98:66:43:68:dc:2a:86:73:20:22:0f:75:5e:99:ca:
+ 2e:ec:da:e6:2e:8d:15:fb:58:e1:b7:6a:e5:9c:b7:
+ ac:e8:83:83:94:d5:9e:72:50:b4:49:17:6e:51:a4:
+ 94:95:1a:1c:36:6c:62:17:d8:76:8d:68:2d:de:78:
+ dd:4d:55:e6:13:f8:83:9c:f2:75:d4:c8:40:37:43:
+ e7:86:26:01:f3:c4:9a:63:66:e1:2b:b8:f4:98:26:
+ 2c:3c:77:de:19:bc:e4:0b:32:f8:9a:e6:2c:37:80:
+ f5:b6:27:5b:e3:37:e2:b3:15:3a:e2:ba:72:a9:97:
+ 5a:e7:1a:b7:24:64:94:97:06:6b:66:0f:cf:77:4b:
+ 75:43:d9:80:95:2d:2e:85:86:20:0e:da:41:58:b0:
+ 14:e7:54:65:d9:1e:cf:93:ef:c7:ac:17:0c:11:fc:
+ 72:46:fc:6d:ed:79:c3:77:80:00:0a:c4:e0:79:f6:
+ 71:fd:4f:20:7a:d7:70:80:9e:0e:2d:7b:0e:f5:49:
+ 3b:ef:e7:35:44:d8:e1:be:3d:dd:b5:24:55:c6:13:
+ 91:a1
+ """^^cert:hex;
+ rsa:public_exponent "65537"^^cert:int;
+ cert:identity :me .
+</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 -->
+%s
+
+<!-- and this is the bulk of the vocab descriptions -->
+%s
+
+<!-- dirty hack for specgen -->
+<span about="http://www.w3.org/ns/auth/cert#PGPCertificate" rel="owl:equivalentClass" href="http://xmlns.com/wot/0.1/PubKey"></span>
+
+
+<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>
+</ul>
+
+</body>
+</html>
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontologies/rdfa/template_rsa.html Sun Oct 02 23:48:48 2011 +0200
@@ -0,0 +1,178 @@
+<?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#"
+version="XHTML+RDFa 1.0" typeof="owl:Ontology" about="http://www.w3.org/ns/auth/rsa#">
+<head>
+<title>The RSA 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");
+</style>
+</head>
+
+<body>
+<h1><span property="dc:title" about="http://www.w3.org/ns/auth/rsa#">The RSA Ontology</span> <span property="owl:versionInfo" about="http://www.w3.org/ns/auth/rsa#">1.0</span></h1>
+
+<h2>Namespace Document <span property="dc:created" about="http://www.w3.org/ns/auth/rsa#" 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/rsa#">http://www.w3.org/ns/auth/rsa#</a> (<a href="http://www.w3.org/ns/auth/rsa.n3">N3</a>)</dd>
+
+<dt>Latest version:</dt>
+<dd><a href="http://www.w3.org/ns/auth/rsa#">http://www.w3.org/ns/auth/rsa#</a> (<a href="http://www.w3.org/ns/auth/rsa.n3">N3</a>)</dd>
+
+<dt>Authors:</dt>
+<dd><a href="http://ii.uwb.edu.pl/~dtomaszuk/">Dominik Tomaszuk</a> (<a href="http://ii.uwb.edu.pl/">University of Bialystok</a>)</dd>
+<dd><a href="http://bblfish.net/">Henry Story</a> </dd>
+</dl>
+
+<p class="copyright"><span>Copyright © 2010-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.</span></p>
+
+<hr />
+
+<h2 id="sec-status">Abstract</h2>
+<p about="http://www.w3.org/ns/auth/rsa#" property="rdfs:comment">Ontology for the RSA public private keys.</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/rsa#" 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 RSA 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 Ontology at a glance</h2>
+
+<p>An a-z index of <em>RSA Ontology</em> terms, by class (categories or types) and by property.</p>
+
+
+%s
+
+<div style="clear: left;"></div>
+
+<div style="clear: left;"></div>
+
+
+<!-- ================================================================== -->
+
+
+
+
+<p>
+The evolution of the <em>RSA 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> @prefix cert: <http://www.w3.org/ns/auth/cert#> .
+ @prefix rsa: <http://www.w3.org/ns/auth/rsa#> .
+ @prefix foaf: <http://xmlns.com/foaf/0.1/> .
+ @prefix : <https://joe.example/profile#> .
+
+ :me a foaf:Person;
+ foaf:name "Joe" .
+
+ [] a rsa:RSAPublicKey;
+ rsa:modulus """
+ 00:cb:24:ed:85:d6:4d:79:4b:69:c7:01:c1:86:ac:
+ c0:59:50:1e:85:60:00:f6:61:c9:32:04:d8:38:0e:
+ 07:19:1c:5c:8b:36:8d:2a:c3:2a:42:8a:cb:97:03:
+ 98:66:43:68:dc:2a:86:73:20:22:0f:75:5e:99:ca:
+ 2e:ec:da:e6:2e:8d:15:fb:58:e1:b7:6a:e5:9c:b7:
+ ac:e8:83:83:94:d5:9e:72:50:b4:49:17:6e:51:a4:
+ 94:95:1a:1c:36:6c:62:17:d8:76:8d:68:2d:de:78:
+ dd:4d:55:e6:13:f8:83:9c:f2:75:d4:c8:40:37:43:
+ e7:86:26:01:f3:c4:9a:63:66:e1:2b:b8:f4:98:26:
+ 2c:3c:77:de:19:bc:e4:0b:32:f8:9a:e6:2c:37:80:
+ f5:b6:27:5b:e3:37:e2:b3:15:3a:e2:ba:72:a9:97:
+ 5a:e7:1a:b7:24:64:94:97:06:6b:66:0f:cf:77:4b:
+ 75:43:d9:80:95:2d:2e:85:86:20:0e:da:41:58:b0:
+ 14:e7:54:65:d9:1e:cf:93:ef:c7:ac:17:0c:11:fc:
+ 72:46:fc:6d:ed:79:c3:77:80:00:0a:c4:e0:79:f6:
+ 71:fd:4f:20:7a:d7:70:80:9e:0e:2d:7b:0e:f5:49:
+ 3b:ef:e7:35:44:d8:e1:be:3d:dd:b5:24:55:c6:13:
+ 91:a1
+ """^^cert:hex;
+ rsa:public_exponent "65537"^^cert:int;
+ cert:identity :me .
+</pre>
+
+<h2 id="sec-crossref">Cross-reference for Cert classes and properties</h2>
+
+<p>The <em>RSA 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 -->
+%s
+
+<!-- and this is the bulk of the vocab descriptions -->
+%s
+
+<!-- other ns classes -->
+<h3>Other vocabularies terms</h3>
+<ul>
+<li class="specterm" id="PrivateKey" about="http://www.w3.org/ns/auth/cert#PrivateKey" typeof="owl:Class"><em property="rdfs:label" content="Private Key"><a href="http://www.w3.org/ns/auth/cert.html#PrivateKey">Private Key</a></em></li>
+<li class="specterm" id="PublicKey" about="http://www.w3.org/ns/auth/cert#PublicKey" typeof="owl:Class"><em property="rdfs:label" content="Public Key"><a href="http://www.w3.org/ns/auth/cert.html#PublicKey">Public Key</a></em></li>
+</ul>
+
+<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>
+</ul>
+
+</body>
+</html>
+
+