Authentication Ontology about cei2tei HOT 7 CLOSED

Removing materials and physical aspects of seals makes sense for the concept of authntication, but is problematic when the intersection of material and type of seal help authenticate an element, as in the case of the intersection of Great Seal of the Realm & green wax & patent of nobility & Elizabeth II. If a patent of nobility issued in the reign of Elizabeth II did not have a green wax pendant Great Seal, it would presumably be de facto inauthentic. It is cumbersome to add this level of detail to the authentication ontology, and so will require some rethinking. Individual seals could be defined and if they do not match, it would be inauthentic, but that becomes ridiculous, and it is not something that would be useful in markup for general charters over a long period. Perhaps an authentication element auth:correctMaterials and another auth:correctFormat could cover this and what is currently covered by auth:dimensions.

from cei2tei.

Most of the values should be transitive.

The soft biometric elements, specifically, should not be transitive, and should probably be some other category.

papal_seal should perhaps be replaced by a blank node _:papal referencing the pope as owner.

from cei2tei.

Should all categories under seal be removed and the appropriate value from the VIS be used instead? Most of the relevant values are linked, but I wonder if it should be suplicating that level of data, especially since the VIS has more values. On the other hand, the VIS also includes a number of non-authenticating aspects.

from cei2tei.

Knowledge Organisation is principally based on networks, thus we don't have to assume that the VIS is just a collection of sub-concepts to "seal". It might make sense just to reuse a selection of concepts from the VIS and even add further relationships that currently part of VIS (which, in fact, is only very flat).

from cei2tei.

SKOS says it follows BCP47, but the SKOS Play! validator is throwing an error on the ISO 639-2 code ota for Ottoman Turkish.

from cei2tei.

Currently, does not validate on SKOS Play due to
ilc - Incomplete Language Coverage
for every concept described in another language, it requires all other concepts to be documented in that language as well.

from cei2tei.

The language problems remain, but I am going to close this because I don't think it is practical or desirable to have every single language covered, especially given that some of these languages are just specific transliterations. This is a larger improvement concern, not a validation concern.

from cei2tei.