Version 1.6, EBUCore based on Dublin Core + SKOS + some BBC Core Concepts + basic FOAF properties + equivalences to W3C MA-ONT, Improve the relations around the notions of "hasContributor", "Character", "Cast"., Add "Feature" as sub-class of EditorialObject, Added eventPeriod property., Leftovers from object audio components removed., More consistency on opening property ranges to allow resources or literals., New hasAudioDescription property pointing to a resource (new AudioDescription as subclass of audioTrack) or a presence flag, hasCaptioning, hasSigning, hasSubtitling: the range is either a resource or a literal/boolean indicating the presence/absence thereof, PBCore updates: dateBroadcast, dateLicenced, endLicencedate, dateDistributed, dateDeleted, dateIngested, dateMigrated, dateNormalized, dateTransferred, dateValidated, shotlog, folksonomy, clonedTo/isClonedFrom, dubbedTo/isDubbedfrom, derivedTo/isDerivedFrom, playbackSpeed, framesPerSecond, inchesPerSecond, hasGeneration, hasStandard, dimensions.
Guidelines: for the purpose of flexibility and interoperability with a wider range of implementations, some properties purposefully do not have a range and accept either a resource or a literal. When a resource is used, it is recommended to reuse objects defined in the model (e.g. pair hasEvent/Event or hasRole/Role). Example 1: x hasRole 'actor'. Example 2: x hasRole _:Role_1 (a reference to the Concept Id from a SKOS Role vocabulary defined in the ontology)., Note to implementers: The EBUCore ontology is used by a variety of users with different needs. Several EBUCore properties have no range to allow different implementations using entities or literals. As an implementer, it is your choice to go for one or the other for each property to have consistent expectations when parsing individuals. EBUCore also provides different classes defined as subclasses of skos:Concept. You can use these classes as entities in range of several properties currently left without range. EBUCore is expressed in RDF in order to facilitate such modelling and flexibility. As a consequence, propoerties appear in the documentation as annotation properties., The development of the EBUCore ontology is now a joint effort of the EBUCore and PBCore communities., The EBUCore has been designed to make users benefit from the flexibility of RDF to adapt the names of Classes and properties to their respective needs. This means users are welcome to add their own subclasses (e.g. to define the most appropriate BusinessObjects or Resources or Agents) and subproperties.
