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
Jack Brighton, WILL Public Media
Christophe Debruyne, RIA
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
Kim Viljanen, YLE
Knut-Olav Hoven, NRK
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 Platform as a subclass of Service.
Add hasLocationRelatedAsset.
Add agentFee and agentAge.
Add isPartOf with domain Part and range EditorialObject.
Add Licensing as a subclass of Rights
Change Domain of isAgent from Cast to Agent.
Change countryOfResidence and agentNationality into hasAgentCountryOfResidence and hasAgentNationality
Add totalNumberOfgroupMembers with domain Group and totalNumberOfEpisodes with domain Series or Season.
Add hasImageCodec as subproperty of hasCodec.
Add agentRelatedInformationLink and agentRelatedPressLink.
Add ebucore:placeOfDeath as subproperty of core:placeOfDeath
Move cast, crew, staff as subclasses of Agent.
Add hasRelatedPublicationChannel to PublicationEvent
Change domain of seasonNumber to EditorialObject for more flexibility in implementation.
Add agentPreviousName.
Add rightsTerritory/includes/Excludes.
Add hasRelatedPublicationChannel with domain PublicationEvent.
Add firstShowingThisService with domain PublicationEvent.
Add isAgent relation
Add tag as a subproperty of description to provide tags.
Add hasCountryOfBirth and hasCountryOfDeath
Move Character as subclass of Agent to allow characters other than persons (e.g. animals)
Add timeCreated to BusinessObject and Resource
Add missing artefactBrand.
Add Locator class.
Add Award (for BO/EO, Contributor) and associated properties.
Define Resource and BusinessObject as subclass of Asset. Add properties hasAssetRelatedResource, hasAssetRelatedBusinessObject and hasAssetEditorialObject (for harmonisation with CCDM).
Change AudioChannelPurpoose into AudioTrackPurpose, a subclass of skos:Concept.
Correction: empty range for hasRelatedEvent and hasRelatedLocation
Add missing class Element.
Add dateOfRetirement
Version draft 1.9
Add rightsStart/EndDateTime and righst Duration.
Add flag midRollAdAllowed with domain Essence.
Add geoblocking, licensing, copyright, targetPlatform as a subproperties of description as a shortcut to provide such usage restrictions without the heavy use of asset.
Enrich list of EOs from CCDM school discussion e.g. BreakingNewsItem...
Add isDistributedOn with domain EditorialObject and range string or Platform.
Add hasProducer as subproperty of hasContributor.
Add relation hasRelatedAsset with domain BusinessObject.
Add hasEventRelatedLocation/Event/Artefact/BusinessObject/Event
Add missing relations from EBUCore schema: has/isParent, has/isChild, has/isMaster...
Change hasEvent and hasLocation into hasRelatedEVent and hasRelatedLocation.
Add hasAgentBiography
Add hasAgentRelatedArtefact
Replace AudioChannel with AudioObject for better ADM compliance. Change AudioChannelPurpose into AudioTrackPurpose, Change audioChannelNumber into audioTrackNumber. Add a relation hasRelatedAudioObject with domain MediaResource.
Remove placeOfBirth and placeOfDeath in conflict with hasPlaceOfBirth and hasPlaceofDeath
Change artefactPriceCurrency into hasArtefactPriceCurrency to allow using Concept / currency codes.
Add new class UsageRestriction as subclass of Rights.
Add hasArtefactRelatedLocation.
Add dateProduced with domain Resource or BusinessObject.
Add hasBeenAwarded with domain Agent.
Add Person weight and height.
Add artefactComment.
Add personName for compound names

Generated with TopBraid Composer by TopQuadrant, Inc.