--- a/spec/tls-respec.html Mon Sep 09 22:01:35 2013 +0200
+++ b/spec/tls-respec.html Sun Oct 13 19:58:53 2013 +0200
@@ -646,37 +646,35 @@
<h2>Vocabulary</h2>
<p>RDF graphs are built using vocabularies defined by URIs, that can be placed in subject, predicate or object position.
- The definition of each URI should be found at the namespace of the URI, by dereferencing it.
- Here we list the core cryptographic terms needed, and detail some of the useful optional relations from the FOAF
- vocabulary that we have used in the diagrams.
+ The definition of each URI should be found at the namespace of the URI.
+ Here we detail the core cryptographic terms needed. The optional foaf vocabulary used to describe
+ agents can be found at the <a href="http://xmlns.com/foaf/0.1/">the foaf namespace vocabulary document</a>.
</p>
-<section class='normative'>
-<h2>Cryptographic Vocabulary</h2>
-<p>The following properties MUST be used when conveying the relation between the
- <tref>Subject</tref> and his or her key, within <tref>WebID Profile</tref> documents:</p>
+<p>Below is a short summary of the vocabulary elements to be used when conveying the relation between the
+ <tref>Subject</tref> and his or her key, within a <tref>WebID Profile</tref> document.
+ For more details please consult the <a href="http://www.w3.org/ns/auth/cert">cert ontology document</a>. </p>
<dl>
<dt><a href="http://www.w3.org/ns/auth/cert#key">cert:key</a></dt>
- <dd>Used to associate a <tref>WebID</tref> URI with an RSAPublicKey. A <tref>WebID Profile</tref>
- MUST contain at least one RSAPublicKey that is associated with the
+ <dd>Used to associate a <tref>WebID</tref> URI with any PublicKey. A <tref>WebID Profile</tref>
+ MUST contain at least one PublicKey that is associated with the
corresponding <tref>WebID</tref> URI.</dd>
<dt><a href="http://www.w3.org/ns/auth/cert#RSAPublicKey">cert:RSAPublicKey</a></dt>
- <dd>Refers to the class of RSA public key. The RSAPublicKey MUST specify the
- cert:modulus and cert:exponent properties.</dd>
+ <dd>Refers to the class of RSA Public Keys. A RSAPublicKey MUST specify both a
+ cert:modulus and a cert:exponent property. As the cert:modulus and cert:exponent relations both
+ have as domain a cert:RSAPublicKey, the type of the key can be inferred by the use of those relations
+ and need not be written out explicitly.</dd>
<dt><a href="http://www.w3.org/ns/auth/cert#modulus">cert:modulus</a></dt>
<dd>Used to relate an RSAPublic key to its modulus expressed as a hexBinary.
- An RSA key MUST have one and only one modulus. The datatype of a modulus is xsd:hexBinary.
+ An RSA key MUST have one and only one modulus. The datatype of a modulus is xsd:hexBinary. The string representation of the hex:Binary MUST not contain any whitespaces in between the hex numbers.
</dd>
<dt><a href="http://www.w3.org/ns/auth/cert#exponent">cert:exponent</a></dt>
- <dd>Used to relate an RSAPublic key to its exponent expressed as an integer.
+ <dd>Used to relate an RSAPublic key to its exponent expressed as a decimal integer.
An RSA key MUST have one and only one exponent. The datatype of a modulus is xsd:integer.
</dd>
</dl>
</section>
-
-
-
</section>
<section class='informative'>
<h1>Turtle</h1>