Added the error terms to the vocabulary

[iherman]

This PR is not against the main branch but, rather, against the branch behind #140

The PR extends the official security vocabulary to include all the error terms, as RDF individuals, in the security vocabulary.

Note that I have not defined the terms described in that version ("code", "title", etc.) that are in the proposed specification. It would require to add them as bona fide properties with the Errors class as a domain, but I do not believe those (JSON) objects will ever appear as Linked Data. If I am wrong, then these terms should be added to the vocabulary as well (although in that case, it is a possible problem to see that the terms like 'title' or 'code' are extremely generic, hopefully it will not lead to clashes...)

[iherman]

@msporny I have the impression that the change conflicts are related to some other problems. This PR, originally, was meant to be merged into another branch (merged since) and the rebase to main changed things.

Because the merge conflicts are in the index.html file, ie, the core spec, I would prefer you take care of those. Thx.

[msporny]

@msporny I have the impression that the change conflicts are related to some other problems. This PR, originally, was meant to be merged into another branch (merged since) and the rebase to main changed things.

The branch it was intended to be merged into (the one that added the error table) was merged into main, at which point, Github automatically changes the old target branch (the one that added the error table) into the branch that the old target branch got merged into (main).

Because the merge conflicts are in the index.html file, ie, the core spec, I would prefer you take care of those. Thx.

I'll take care of it. :)

[msporny]

Editorial, multiple reviews, changes requested and made, no objections, merging.