add EditorialObject relationship: consistsOf - to link a combined Programme/Essence to individual EditorialObjects

[wivaku]

EditorialObject has relationship isExtractOf:

Used for representing an extract, i. e. the playout of a part or the whole of some archived material on the playout. For attributes like duration and start, the data is placed in the instance representing the abstract. Other metadata is read from the original instance that is extracted.

The opposite (not: inverse of) is relevant as well: consistsOf (or: comprisedOf, etc.): if e.g. multiple Programmes are combined in a single broadcast.
E.g. "Smurfs marathon" could be transmitted as a single Programme (with its own metadata, with single essence) where it is useful to know it consisted of S12E01, S07E07, S03E04.

[wivaku]

I assume one of the existing relationships can be used:

• hasEditorialWork (sub of isMemberOf), but it is unclear what the intention/purpose of that one is
• references

However, as there is an explicit isExtractOf it would make sense to have an explicit version of the opposite.

[JuergenGrupp]

Thank you, @wivaku, for figuring this out! It really looks like something is missing ...

Here are my thoughts on this: We need to express a relation between two EditorialWorks that is not covered by isMemberOf, nor by hasMember (nor the subproperty hasEditorialWork). Membership is typically a relation of an entity to a group of entities, but in this case, the EditorialWork isExtractOf another EditorialWork and the relation is between two singular entities. However, it expresses the relation of a part and a whole thing, which is better phrased with a term like "contains" (implying that there can be more contained entities) than "consists of" (implying that it is the single building material).

Therefore, I suggest to introduce a new object property named "contains" as an inverse property to "isExtractOf".

Comments, please!

[RendersKoen]

Hi Juergen and Wivaku, Good discussion.

I agree with @wivaku that hasEditorialWork is a bit unclear: I noticed that EditorialWork hasEditorialWork EditorialWork is a subclass of EditorialWork

This seems to contradict the hasEditorialWork as a subclass of isMemberOf, since as @JuergenGrupp stated this relationship is reserved to relationship between a single entity and a group.

And I think its a good suggestion to create a Contains and an isExtractOf property.