01.02 Value Lists (Classification Schemes) for Data Properties

Many data properties require predefined values from lists of allowed entries.

Although it is desirable to agree universally on these values to allow lossless exchange, reality teaches us, that different systems use different values even for the same thing.

EBUCorePlus usually offers a data property "objectType" to classify an individual. The predefined values are individuals of the class skos:concept (or a subclass thereof). skos:concept is built very smart. It is really a comprehensive class to represent a named list of hierarchical entries and an additional grouping mechanism that can group an arbitrary subset of all entries under a separate name. As an example: Think of a flat list of all countries of the world. Countries can then be sub-structured to regions and form a hierarchical list. You can then group subsets of countries or regions under a name that characterizes their membership to the group: "Europe", "Asia", "Africa", etc for a geographical grouping or "BRICS", "G7", "NAFTA", "EU", etc for economical contract grouping.

If you need to retain your own list of values, you can simply create your own, specific skos:concept list. Be aware that you still need to map the values when exchanging data with other system.

If you'd like to use a predefined list of values (eg. as a starting point), have a look a the EBU classification schemes). They are not yet formatted perfectly as skos:concept, but their ID-conventions support a hierarchical list and you can add any grouping you like (see "EBU Reference Data & Classification Schemes"). You can also add missing values to a classification scheme. Just make sure that you then give the list a new, distinguishable name, like "[Your Org]_AudioFormatCS". If you think the value is missing in the EBU List too, drop us a note or create an issue.