Ontology for Certificates and crypto stuff.

IRI:
http://www.w3.org/ns/auth/cert#
Other visualisation:
Ontology source

Abstract

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?

Table of Content

  1. Classes
  2. Object Properties
  3. Data Properties
  4. Annotation Properties
  5. Namespace Declarations

Classes

Certificatec back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#Certificate

is defined by
http://www.w3.org/ns/auth/cert#
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.'
has super-classes
documentc
has sub-classes
PGPCertificatec, X509Certificatec

keyc back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#Key

is defined by
http://www.w3.org/ns/auth/cert#
the class of keys
has sub-classes
PrivateKeyc, PublicKeyc, RSA Keyc
is in range of
keyop

PGPCertificatec back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#PGPCertificate

is defined by
http://www.w3.org/ns/auth/cert#
the class of PGP Certificates
is equivalent to
pub keyc
has super-classes
Certificatec

PrivateKeyc back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#PrivateKey

is defined by
http://www.w3.org/ns/auth/cert#
Private Key
has super-classes
keyc

PublicKeyc back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#PublicKey

is defined by
http://www.w3.org/ns/auth/cert#
Public Key
has super-classes
keyc
has sub-classes
RSA Public Keyc
is in domain of
identityop
is in range of
keyop

RSA Keyc back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#RSAKey

is defined by
http://www.w3.org/ns/auth/cert#
The union of the public and private components of an RSAKey. Usually those pieces are not kept together
has super-classes
keyc
has sub-classes
RSA Public Keyc
is in domain of
modulusdp

RSA Public Keyc back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#RSAPublicKey

is defined by
http://www.w3.org/ns/auth/cert#
The RSA public key. Padded message m are encrypted by applying the function modulus(power(m,exponent),modulus)
has super-classes
PublicKeyc
RSA Keyc
is in domain of
exponentdp

Signaturec back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#Signature

is defined by
http://www.w3.org/ns/auth/cert#
the class of signtatures

X509Certificatec back to ToC or Class ToC

IRI: http://www.w3.org/ns/auth/cert#X509Certificate

is defined by
http://www.w3.org/ns/auth/cert#
the class of X509 Certificates
has super-classes
Certificatec

Object Properties

identityop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/auth/cert#identity

is defined by
http://www.w3.org/ns/auth/cert#
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.
has domain
PublicKeyc
is inverse of
keyop

keyop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/auth/cert#key

is defined by
http://www.w3.org/ns/auth/cert#
relates an agent to a key - most often the public key.

has characteristics: inverse functional

has domain
agentc
has range
keyc
PublicKeyc
is inverse of
identityop

Data Properties

exponentdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/auth/cert#exponent

is defined by
http://www.w3.org/ns/auth/cert#
The exponent used to encrypt the message. Number chosen between 1 and the totient(p*q). Often named 'e' .
has domain
RSA Public Keyc
has range
non negative integer

modulusdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/auth/cert#modulus

is defined by
http://www.w3.org/ns/auth/cert#
<p>The modulus of an RSA public and private key. Or the modulus of a DSA Key. The modulus is encoded as a hex binary. The binary is the same as the one encoded in the <a href="http://www.w3.org/TR/xmldsig-core/#sec-CryptoBinary">XML DSIG CryptoBinary</a> </p> <blockquote> This specification defines the ds:CryptoBinary simple type for representing arbitrary-length integers (e.g. "bignums") in XML as octet strings. The integer value is first converted to a "big endian" bitstring. The bitstring is then padded with leading zero bits so that the total number of bits == 0 mod 8 (so that there are an integral number of octets). If the bitstring contains entire leading octets that are zero, these are removed (so the high-order octet is always non-zero). </blockquote> <p>The only difference is that the octet string is then encoded using either xsd:base64Binary or xsd:hexBinary. Currently for all usages of this relation, the xsd:hexBinary datatype should be used until the SPARQL working group specifies specifies in its <a href="http://www.w3.org/TR/sparql11-entailment/#DEntRegime">D-Entailment</a> that those two types are equivalent.</p> <p>It would have been better had there been a hexInteger datatype that was standard and supported by all tools.</p>
has domain
d s a keyc
RSA Keyc
has range
base64 binary
hex binary

privatedp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/auth/cert#privateExponent

is defined by
http://www.w3.org/ns/auth/cert#
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'
has range
non negative integer
is also defined as
annotation property

Annotation Properties

editorial noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#editorialNote

privateap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/auth/cert#privateExponent

is defined by
http://www.w3.org/ns/auth/cert#
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'
has domain
r s a private key
is also defined as
data property

term statusap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2003/06/sw-vocab-status/ns#term_status

Namespace Declarations back to ToC

default namespace
http://www.w3.org/ns/auth/cert#
0-1
http://xmlns.com/wot/0.1/
auth
http://www.w3.org/ns/auth/
card
http://bblfish.net/people/henry/card#
cert
http://www.w3.org/ns/auth/cert#
foaf
http://xmlns.com/foaf/0.1/
listinfo
http://lists.foaf-project.org/mailman/listinfo/
ns
http://www.w3.org/2003/06/sw-vocab-status/ns#
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
skos
http://www.w3.org/2004/02/skos/core#
terms
http://purl.org/dc/terms/
wiki
http://en.wikipedia.org/wiki/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.