Naming convention is not aligned with other vocabularies

[msporny]

The current naming conventions used in the specification are not aligned with other broadly used vocabularies (such as schema.org and all the VC vocabularies published by the VCWG). The conventions are:

• Class names are Pascal Case (example: ListOperator)
• Property names are Camel Case (example: nextUpdate)
• You do not need to prefix properties with the class in which they belong (example: No need for TSL, ListOperator, List prefixes)

The classes and properties in the data model should be updated to align with best practices.

[David-Chadwick]

We followed the naming convention used by ETSI since the data model itself was based on that in ETSI TS 119 612 V2.3.1 (2024-11). However we can easily change the naming convention to match that of the VCDM

[TallTed]

I think there are also some plural names which should all be singular (unless a single predicate instance always contains mutiple values, in contrast to multiple predicate instances each with one value).

(I have not verified that this remains the case, so I cannot provide live examples of such, but for illustration's sake, nextUpdate would generally be appropriate; nextUpdates would generally not.)