RDF documents can make any number of statements. Without some kind of signature or other similar verification mechanism, there is no way to understand who made these statements. One way to document who made a set of statements is via the use of Digital Signatures: signing a document using Public Key Cryptography. The WOT, or Web Of Trust, schema is designed to facilitate the use of Public Key Cryptography tools such as PGP or GPG to sign RDF documents and document these signatures.
An example document utilizing all the classes and properties of the revised wot vocabulary.
A class describing a PGP/GPG key. To describe the key, note that you should use dc:title, rather than linking to a wot:User. This keeps the information for these keys seperate, since wot:Users can be merged based on InverseFunctionalProperties like foaf:mbox.
A link from a Document to the Key it is encrypted to. This allows tools which can import encrypted information to know when a document is encrypted to that tool.
The output of gpg --fingerprint HexKeyID, or equivilant for other software packages, with all whitespace removed. All alpha characters should be capitalized.
This property is designed to link from a wot:User to their wot:PubKey. This is especially useful as a property in conjunction with other schemas like FOAF, aimed at describing the aspects a user might store on their homepage.
Note that this property is not designed to point to the actual address of a Public Key, but rather to the URI identifying the PubKey class. Although these may be the same, it is still advisable to assert a wot:pubkeyAddress property attached to the PubKey, for tools which expect this.
An identifier string for a public key. This key is often used to identify the key, as it has ~4 billion possible values. Note that this is not an owl:InverseFunctionalProperty: there are multiple keys which have the same Key ID, even though there are significantly fewer than 4 billion keys in the public keyservers. This field should contain no whitespace, and should be listed in all capitals. An example is:
A link from a Public Key to an ascii version of said key. It is usually acceptable to include other content in this file as well: so long as the ascii signature has a newline before and after it, tools should be able to import the key regardless of whether it is included in other content.
Corresponding to the wot:signer property, this is designed to link from a signature event to the key which was signed, or the signee in the transaction.