Godfrey Rust - Rights.com - Linked Content Coalition 062013


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Godfrey Rust - Rights.com - Linked Content Coalition 062013

  1. 1. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013From a parallel universeThe Linked Content Coalition - a working relationship withEuropeana?Godfrey Rust, Rightscom/Linked Content CoalitionEuropeana Licensing Workshop June 2013www.linkedcontentcoalition.org
  2. 2. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCCRDI project, Copyright HubLCC rights modelFuture applicationsLCC and Europeana?
  3. 3. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Linked Content CoalitionLCC was established in 2012 as a project to develop buildingblocks for the expression and management of rights andlicensing across all content and media types.Membership (50+ organizations) global, but EC/US focussed.All media types and all parts of the digital content supply chain,some technology providers. No cultural institutions in firstphase.Supported by EC (funding the forthcoming RDI project) and inUK “Copyright Works” report leading to Copyright Hub.Phase 1 completed – “LCC Framework” published April 2013.“Digital Identifier Network” paper yet to come.3
  4. 4. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013SourceCreator or repositoryof rights dataSourceCreator or repositoryof rights dataExchangeMaking rightsavailable to UsersExchangeMaking rightsavailable to UsersUserSeeking information about rights(from Sources),or to acquire rights (from Exchanges)UserSeeking information about rights(from Sources),or to acquire rights (from Exchanges)Scope of LCC - the Rights Data Supply ChainTTTTTTTTTTRights data flows along thesupply chain, undergoingtransformations as needed.This shows the flow of rightsinformation in the supply chain,identifying the key roles played.Different roles may be played bythe same party. The chain may beof any length or complexity.Rights data flows along the chain.indicates a point at whichtransformation (or “dataconversion”) may be needed fromone format or language toanother. The transformation maybe a task carried out by one of theparties in the flow, or by anintermediary acting as a“Transformer”.TT
  5. 5. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Scope of LCCLCC definition of a Right: “A state in which a Party is entitled todo something in relation to a Creation, as a consequence of alaw, agreement or policy”.No core differences in data model by sector or media, orbetween commercial/cultural, paid/free, owned/pd. Differencesare in vocabulary, not structure.Covers all kinds of rights data – ownership, licences, conflicts.Focus on automation.Isn’t it easier to “start small”?Content flows through all types of domain, and is fragmented,re-purposed, adapted and aggregated in any number of ways.You have no idea what kind of deals you will need to describetomorrow, and how complex they will be.5
  6. 6. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013First deliverable - LCC Framework (April 2013)Specification for best practice and interoperability in the digitalrights data supply chain.Principles for identification and messaging (and, in future,user interface/iconography) in the digital network.Rights Reference Model (RRM) – comprehensive data modelfor all types of rights in all types of content for all types of useand control. With XML and RDF/TTL representations (“CRF” –common rights format – development of specificimplementations of this is continuing).RRM can be used for system/message/app design, or datatransformation for interoperability between other schemas– a“hub” model to allow anyone to talk to anyone about rights.6
  7. 7. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC next step: standards consortiumSufficient value seen in first LCC outputs and in creating across-sector forum for LCC to continue.LCC proposed to be a consortium of standards bodies.The aim of the LCC will be to facilitate and expand thelegitimate use of content in the digital network throughinteroperable identifier and metadata standards.Members: organizations who create and manage identifier,metadata and messaging standards for content of all mediatype.Any other organization or person may show their support forthe aims of the LCC by declaring themselves as an affiliate.7
  8. 8. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC consortium initial membershipJune 2013 invited six organizations active in original project:DDEX (primary content – music)EDItEUR (primary content – text)MovieLabs (primary content – audiovisual)IDF (any content –strong in journals, data, av)IPTC (primary content – news)The Plus Coalition (primary content – images)Further invitations will be sent to other eligible groups.Any other types of organizations may be “Affiliates” (all LCCphase 1 partners will be invited).8
  9. 9. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC will……support interoperability between the computer systems ofany and all legitimate participants in the digital network,including creators, rightsholders, publishers, aggregators, rightsand content exchanges, retailers, consumers, culturalinstitutions, (including libraries, museums and archives) andtheir agents and associations.…focus principally on rights-related data (includes content andparty identifiers and metadata).…facilitate the legitimate use of copyright and public domainworks, under any business model or none, including "free use".9
  10. 10. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC will not……compete with any activities of existing standards bodies, butwill deal with matters of common interest across existingstandards bodies.…address matters of copyright law.10
  11. 11. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC work itemsWork items proposed and carried out by groups of its members,which may result in (for example):- common controlled vocabularies (eg “link relators“, rightsverbs)- authorized vocabulary mappings and/or schematransformation rules for interoperability- specific multimedia messages/schemas/applications- standard "icons" and other user interface elements forrights data and services- presenting consortium views and proposals and co-operate with other bodies (eg schema.org, DC,bibliographic/cultural projects)11
  12. 12. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC obligations and governanceOwn and maintain the LCC Framework specifications and futureLCC standards and outputs, and make these generally availableunder free use license arrangements.Provide a real and virtual forum for discussion and consultationamong members (for example, hosting email reflectors, webinarsand real and virtual meetings).Self-governed by a council of its members.All projects individually funded by members, affiliates or others,including with grant funding.12
  13. 13. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Next: RDI (“Rights Data Integration”) projectBeginning June 2013 (?), for 27 months, EC funded (under ICTPSP 6thcall 2012).An implementation of the RRM as a “hub” .Real businesses dealing with real data and hoping for reallong-term business opportunities from RDI.A range of data flows across the supply chain to show thatdifferent rights expressions (licenses and rightsholding claims)from all media types can be integrate.Hub to be built by CINECA (also run ARROW). Using MINT forschema mapping. VMF for vocabulary mapping.Also show how new standards can be implemented to fill gaps(identifiers and registries in image sector – CEPIC/Getty/Album/PLUS Coalition).13
  14. 14. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013mEDRARDI participants (initial – others may be added)14IFRRO/IPTC member(s)PearsonAxel SpringerARROWPublishing Still imagesPPLEMI MusicPublishingCIMusicFremantleMediaDanishProducersAssociationAVCINECARightscomNTUAEdiserSourcesTransformer/mappingExchangesKobalt MusicCEPIC Gettyage fotostock/THPGetty/Picscout/PLUSRightsDirectUsersBrackets denote contributing partnerwhich is not a member of the consortiumPLUSCapture/British LibraryAlbum
  15. 15. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Next: Copyright HubOutcome of UK government “Copyright Works” report.Supports LCC as its data Framework.Starting with pilot portal July 1 2013.Goals: enable users to discover who owns rights and toacquire licenses (including supporting “orphan works”registry). Later to enable registration/declaration.All media sectors, CMOs and major content publishersinvolved.Though UK based, international in scope.Focus is the “long tail” of unlicensed, low value use.Phase 1 just a portal linking to websites. Phase 2 (2014)federated search. Phase 3, support License transactions?15
  16. 16. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC Rights Model - structureAbstract – can be expressed in any language or schema (LCCuses XML and RDF et present).Two parts: general Entity Model, then specific Rights ReferenceModel (“RRM”) – a “profile” of the Entity Model using 8specialized types of Entity.Two levels: “Full” model, which provides the richest possiblemodel for mapping and integrating any data – this is beingused in the RDI “Hub”. Very expressive, but verbose and notideal for more targetted applications.“Flattened” models, which are optimized “fragments” usingspecific vocabularies for specific purposes, but can beautomatically expanded back to “Full”.16
  17. 17. Godfrey Rust Europeana Licensing © LCC/Rightscom 20130-n1-n110-n0-n 0-nLinkLinkLCC Entity Model: Attribute ModelEntityCategoryEntityLCC Entity ModelThis diagram shows the commonstructure for each Entity in the RRM(and other models which LCC mayspecify in future).Each Entity is built in a modular wayfrom combinations of five types ofAttribute, each of which has adifferent “micro-model” structure,exemplified here. Each Attribute isan Entity in its own right and mayhave Attributes of its own.TypeValueexamplexyz:RightTypexyz:PlayTypeValueNameTypeDesignationPartPartexamplelcc:Name“John Smith”ReferenceName“Smith, John”, Indexed“John”, NamesBeforeKeyName“Smith”, KeyNameTypeModeProximityValueUnitexamplexyz:FileSizelcc:SingleQuantitylcc:NotMoreThan10xyz:MBDescriptorA Name, Identifieror Annotation of anEntity in the form ofan uncontrolled orpartially controlleddata valueTypeModeProximityFromProximityToexamplexyz:ValidPeriodlcc:Periodlcc:Exactly2012-01-01lcc:NotAfter2013-12-31LinkTypeEntity1Entity1RoleEntity2Entity2Roleexamplelcc:Creation_PartyA123 (=“Moby Dick”)B987 (=“Herman Melville”)xyz:AuthorNote: Some element names are abbreviated because of spaceCategoryA categorization ofof an Entity with afully controlleddata valueQuantityA measure ofsome aspect of anEntityTimeA point orperiod oftimeassociatedwith anEntityLinkA typedrelationshipbetweentwo Entities
  18. 18. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013RRM Entity and Link TypesCreationPartyRightsConflictAssertionRightsAssignmentContext PlaceRight
  19. 19. Godfrey Rust Europeana Licensing © LCC/Rightscom 20130-n0-n0-10-n1-n0-1RRM RightRightParty=Right ContextType=Context EntityType1-n Territory1-n ValidPeriodPercentageShareRelatedParty0-nCreationRelatedCreationContext1-n RightType0-n ToolType0-n MaterialType0-n OutputCreationType0-n HostCreationTypeNumberOfUsesPlace0-n ValidContextType1 IsExclusiveRelatedContextRelatedPlaceLike all LCC Contexts, a Right inherits theattributes of the Context Entity. In anyimplementation of the RRM, a Right may haveother specialized Attributes modelled accordingto the LCC Entity Model and constrained by rules.RelatedRight
  20. 20. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC Rights Model – background and testingDeveloped from indecs Framework work in 2000. Underlyingmodel used in many proprietary and standard applications (egDDEX, DOI, ONIX) and maps well to CIDOC (museum/archive)and FRBR (bibliographic) reference models, though LCC is moregeneric and comprehensive.Use cases from existing rights languages/messages (eg ODRL,RightsML, Creative Commons, ONIX-PL, Plus Coalition) mapped.Examples will be published soon in LCC “Common RightsFormat” XML and RDF. No significant issues.More exhaustive proof will be done in RDI.20
  21. 21. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013LCC Rights Model – profilesAn RRM “profile” is defined by a set of constraint rules whichdepend on Categories, and may be written in any schema orlanguage. For example:In a PermittedRight in an XYZ License:- there may be no more than one RightType, from Code List B- the Rightsholder must be an Organization ofOrganizationType=Library- There may be any number of Conditions which are Payments orUsageReportingEvents.The structure of the RRM allows for any level of complexity ofsuch rules without the need for extending the model orschema.21
  22. 22. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Future applications of model – (1) HubsFull model being piloted in RDI (as described), then CopyrightHub.Other discussions under way.22
  23. 23. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Future applications of model – (2) “WCDs”“Web Content Declaration of Interest” .Most items of content are now published first in digital form onthe web. Much of this content is of some commercial value (orpotential commercial value).Much is “self-published” by individuals or by organizations whoare not primarily publishers, but primary publishers also nowrelease a great deal of content through websites, blogs and file-sharing services.The total number of new and adapted works newly published onthe web each day is now much greater than the total publishedprint output of books of civilisation.There may now be more than a billion “web content publishers”.
  24. 24. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013WCD formatMachine-interpretable declarations of content and rights madeat the point of first publication of digital content on theweb.Using (and supplementing) existing identifier and metadatastandards and registries wherever possible.Link digital IDs (“fingerprints”) to authoritative metadata forcontent and rights.Using mapped controlled vocabularies.Declarations should be integrated with content loading systems,but web content aggregators are not expected to be registries –Apps and APIs to provide links to registries.Content publishers can set up “profiles” which will automatemuch of the process.
  25. 25. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013The identifier gapMost direct-to-web publishing captures metadata –who is the creator / rightsholderwhat is the contentand sometimeswhat rights are availablebut much of it is not machine-interpretable (that is – notcaptured as shared or standard identifiers) or authorized. It iscaptured as free text or proprietary IDs.
  26. 26. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013use case: a music video (but could be any content)Performer “Ebony Day”Creation “Kiss You - One Direction (Ebony Day LiveCover)”This is a version of: Music video by One Directionperforming Kiss You. (c) 2013 Simco Limited underexclusive licence to Sony Music Entertainment UKLimitedRights No information published.
  27. 27. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013As a Web Content Declaration of InterestContentID 0101010101010101 IDType=AcmeFingerprintPerformer ID=00000001 IDType=ISNICreation ID=1234567890 IDType=ISRCType=ddex:MusicalWorkVideo (etc)LinkTo ID=987654321 IDType=ISRCLinkType=lcc:VideoCoverOfLinkTo ID=55555555 IDType=ISWCLinkType=lcc:RecordedPerformanceOfRights ID=123456789 IDType=LccOwnershipClaimAsserter ID=00000002 IDType=ISNIMost WCD data can be stored as a default “profile” and createdautomatically as part of the content publication process.
  28. 28. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013A WCD in URIs – the goal (can be Linked Data)ContentID 0101010101010101 IDType=[URI]Performer [URI]Creation [URI]Type=[URI]LinkTo=[URI]LinkType=[URI]LinkTo=[URI]LinkType=[URI]Rights [URI]Asserter [URI]
  29. 29. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013WCD summaryDifferent profiles of WCDs for different situations. Can be assimple or complex as required.Based on the LCC models and existing, mapped vocabularies,so fully extensible.Support simple text metadata, existing standard/proprietaryschemas (which can include Europeana), and new generic LCCschemas to fill gaps.Customised for specific content and services using Apps andAPIs.
  30. 30. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013Where might LCC and Europeana work together?Data modelling: issues outlined for next period of Euorpeanare the same that LCC has already to deal with.Common and mapped vocabularies.Work with CC (LCC and CC have begun dialogue). Create a fullcommon rights expression language?PK: “Explore the ability to move rights statements to anamespace that can be shared with similar projects”.Identifiers and Assertions for Rights Statements – “who sez?”Is there any Europeana use case for a WCD?What points of integration of data and use are there from thecommercial and Europeana sectors? Should Europeana be onthe Copyright Hub?
  31. 31. Godfrey Rust Europeana Licensing © LCC/Rightscom 2013From a parallel universeThe Linked Content Coalition - a working relationship withEuropeana?Godfrey Rust, Rightscom/Linked Content Coalitiongodfrey.rust@rightscom.comwww.linkedcontentcoalition.org