SKOS Core RDF vocabulary


Contributor [dc:contributor]
Glenn Clatworthy, PBS
Michael J. Giarlo, Penn State University
Hugo Cordier, SetKeeper
Drew Myers, WGBH
Casey Davis, WGBH
Christophe Debruyne, RIA
Jack Brighton, WILL Public Media
Vincent Dabouineau, francetelevisions
Cliff Ingham, City of Bloomington
Hugo Manguinhas, Europeana
Guillaume Rachez, Perfect Memory
Valentine Charles, Europeana
Julie Hardesty, Indian University Library
Rebecca Fraimow, WGBH
Valerie J. Miller, PBS
Jürgen Grupp, SRG
Rebecca Guenther, Rebecca Guenther Consulting
Are Tverberg, TV2
Mark Guelbahar, IRT
Kara van Malssen, AV Preserve
Dalia R. Levine, HBO
Peggy Griesinger, George Mason University Libraries
Karen Cariani, WGBH
Cedric Klein, Perfect Memory
Chuck McCallum, WGBH
Knut-Olav Hoven, NRK
Kim Viljanen, YLE
Robert Engels, NRK
Matthieu Parmentier, francetelevisions
Laurence Cook, metaCirque
Tormod Vaervagen, NRK
Adam Wead, Penn State University
Sadie Roosa, WGBH
Creator [dc:creator]
Jean Pierre Evain, EBU
Description [dc:description]
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 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.
The development of the EBUCore ontology is a joint effort of the EBUCore and PBCore communities.
Publisher [dc:publisher]
European Broadcasting Union (EBU)
Rights [dc:rights]
Copyright 2015 EBU
Title [dc:title]
EBUCore - the Dublin Core for media
SKOS Core RDF vocabulary
Add for each class an ids, a name a description when missing
Add videoEncodingProfile and audioEncodingProfile properties as subproperties of encodingProfile
Introduced new TextLine Class and associated properties for timed text, annotation, etc.
Added social medias: agentFacebook, agentTwitter, agentInstagram
Add frameHeight and frameHeightUnit
Align with CCDM properties touching EBUCore classes
CORRECTION: change PublicationPlanning into PublicationPlan
Improved the relations around the notions of "hasContributor", "Character", "Cast".
Add numberOfAudioTracks and numberOfVideoTracks
Added locationCode and hasLocationPicture
Add hasAudioCodec and hasVideoCodec
Introduce Person as a superClass of Contact and rename Contact properties accordingly
Add hasAudioTrack and hasVideoTrack
seasonNumber, Episode and episodeNumber.
Harmonisation with EBU CCDM: businessObjectId, businessObjectType, editorialObjectId, editorialObjectType, storageId, storageType .
Add resourceType property.
Added eventPeriod property.
Manage addresses as locations
Add CreativeCommons subclass to Rights.
Sanity check on property domain and ranges and definitions or labels
Version 1.8
Support of specific timecode drop frame
Alignment with EBUCore schema: add missing rightsClearanceFlag
Clean the definition of equivalent classes and properties from external vocabularies like foaf: and core:
Add videoEncodingLevel and audioEncodingLevel properties as subproperties of encodingLevel
Introduce new classes Artefact/Props/Food...
Add FIMS Classes: BMContent, BMEssence, BMTemplate, etc.
Add Identifier as a class.
Extend bitRate properties with audio and video bitRate properties
Added two Classes: Action and Emotion.
Add event start and end times and dateTimes

Generated with TopBraid Composer by TopQuadrant, Inc.