ebu
Skos:consept, PublicationChannel_type ,usage?
Lets say I want to describe PublicationCannel with type, and there is skos:consept class called PublicationChannel_type.
If there were:
http://urn.fi/urn:nbn:fi:rtva-ch-48 a ebucore:PublicationChannel ; ...
ebucore:objectType <https://metadata.rtva.kavi.fi/rtva/service-type/1>
...
all the type are:
https://metadata.rtva.kavi.fi/service-type/1 a PublicationChannel_Type ; skos:prefLabel "Valtakunnallinen"@fi , "Nationwide"@en , "National"@sv .
https://metadata.rtva.kavi.fi/service-type/2 a PublicationChannel_Type ; skos:prefLabel "Alueellinen"@fi , "Regional"@en , "Regional"@sv .
https://metadata.rtva.kavi.fi/service-type/3 a PublicationChannel_Type ; skos:prefLabel "Puolivaltakunnallinen"@fi , "Half national"@en , "Halv national"@sv .
https://metadata.rtva.kavi.fi/service-type/4 a PublicationChannel_Type ; skos:prefLabel "Maksullinen"@fi , "Pay"@en , "Betala"@sv .
Would this be according to standard?
I think this would be "grammatically" according with the standard. It is done in the intended way of using skos:concept.
However, from a more "semantic" point of view, I would recommend to rethink the list of categories: To me it seems that
https://metadata.rtva.kavi.fi/service-type/4 a PublicationChannel_Type ; skos:prefLabel "Maksullinen"@fi , "Pay"@en , "Betala"@sv .
is addressing the aspect of "fee condition" whereas the first three address the aspect "geografical scope in Finland". So, you might consider to create your own two properties to represent the two aspects.
In general, I am not yet sure how to handle the problem of multiple type aspects: for a PublicationChannel these aspects could be eg. "fee condition" (flat-rated, pay-per-use, , free to air, ...), "temporality" (linear, on-demand, hybrid), "geografical scope" (national, regional, international), "supported media types" (audio, video, text, data, ...), "supported player device" (radio set, tv set, browser, app, social media client ...), etc (this list is neither discussed, nor comprehensive) The question is, should we have one property for each of the aspects or are there better ways to handle multiple aspects? What do you think?
Thank you! This is still a learning process to implement truly semantic system for us, good to have discussion :) I think you have a good point. Our system archives only linear television and radio, so it also limits type available. This limitation is because our current legistlation, which pretty much ignores VOD services, unfortunately.
But it is true we should consider a separate type for "fee condition", as suggested, maybe simply "free-to-air" and "pay".
Does EBU members have something similar in use, for reference, I mean different approaches for classifying channels?