Godfrey Rust, FRBR Workshop, Ohio May 4 2005 © Rightscom 2005 Thoughts from a different planet

Godfrey Rust, FRBR Workshop, Ohio May 4 2005© Rightscom 2005

Thoughts from a different planet


Thoughts from a different planet(Only slightly different).


Some activities in parallel worlds.Some thoughts on metadata and models.

A contextual approach to metadata – 2 examples.Some thoughts on FRBR.


The nice thing about standards is that there are so many of them to choose from.


An appallingly inaccurate summary of the development

of metadata standards and identifiersfor content and media.


FRBR

Handle

Multimedia

ISRC

ISAN

ISMN CIS

Dublin Core

IMS

DOI

IIM

ISWC

url

urnSICI

Books

Audio

Audiovisual

Libraries

Copyright

Journals

Magazines

Newspapers

STANDARDS

Education

MARC

CAE

ISBN

ISSN

Music

Texts

EAN

Technology

Archives Museums

UPC

ISO codes

today1980s mid 90’s

ERMIIPI

UMIDISTCSMPTE

DMCS

EPICS

ONIX

LOM

abc

<indecs>

MPEG7

MPEG21

ISO11179

RDFXML schema

IPDA

PRISMeBooks

OeBF

NITFCIDOC

CrossRef

P/META

XrML

uri

BICIMPEG21 RDD/REL

MI3P

SCORMNewsML

GRidMPid

MWLI

SAN

V-ISANERMI


MI3P (Music Industry Integrated Identifiers Project) (www.mi3p.org)

Four year development funded by recording industry (RIAA/IFPI) and copyright societies (CISAC/BIEM), supported by DSPs (“Digital Service Providers”).Managed by Rightscom.Standard to be declared May or June this year.

25+ XML message schemas for- declaring new digital releases- declaring rights claims

- declaring deals - reporting sales

Three new identifiers:GRID (Global Release ID) (Release = “box” of digital resources)MWLI (Musical Work License Identifier)MPID (Mi3p Party ID)

Makes use of ISRC, ISWC, ICPN and any others needed.Releases may contain digital audio, text, audiovisual, image, software – doesn’t have to include music: so MI3p is a generic multimedia standard.

Ongoing development of many new messages and identifiers.


ONIX (Online Information Exchange) (www.editeur.org)

Five years of message standards for text publishers.Managed by publishing industry standards body EDItEUR.Being widely implemented globally – data quality mixed.Being used a reference model for systems development.

Messages –ONIX for Books v2.1 (v 3 expected).ONIX for Serials (SPS – Subscription Products, SOH – Online

Holdings) in development. ONIX for DOI Registration.ONIX for Multimedia?ONIX LicensingTerms Message (first draft April 2005).

A generic licensing terms message, but first implementation (we hope) by journal publishers and digital libraries (“ONIX/ERMI”).

Onix Products may contain digital audio, text, audiovisual, image, software: so ONIX is a generic multimedia standard.

Ongoing development of many new messages (and identifiers?).


Why not one multimedia content metadata standard?

Different starting points.Different functional requirements.Different levels of granularity for different things.Different “views” of reality.

The days of “one size fits all” standards are over.

But domains are now overlapping and becoming “liquid”. MI3P will need to accommodate ONIX metadata, and vice versa.

The challenge now is interoperability and re-purposing.


Ontologyx (pronounced “onto-logics”)

Ontologyx was formed in 2003 to provide solutions for data interoperability using contextual semantics.

Its core resource is Ontology_X - an ontology which can include schemes and terminology from any domain, mapped together through the use of its Context Model (which is really cool).

Ontology_X is being built to answer the question: how can I preserve meaning and re-purpose data when combining information from different data sources, whether internal and external?


<indecs> project (1998-2000) brought music, text, visual and audiovisual industry groups together to address metadata interoperability - <indecs> framework resulted.

(The <indecs> project compared notes with Tom Delsey and others on FRBR and with the CIDOC CRM developers).

MPEG-21 Rights Data Dictionary 2001-3, backed by consortium including IFPI/RIAA (recording), MPAA (film), IDF and EDItEUR (text).

Ontologyx created as a brand of Rightscom in October 2003 to develop services and IP based on Ontology_X.

Ontologyx background


ExpressionExpression

FixationFixation

Abstract

Spatio-Temporal

Tangible

Atoms/bits “I made it”

Actions “I did it”

Thoughts “I conceived it”

Identifiersinclude...ISWCISANPIIDOI

Fixed in

Abstracted to

Creation primary typesDiagram 5Generic Metadata Schema

Diagram 10

Identifiers include...ISBNISSNUPC/EANDOI

Identifiers

include...ISRC

UMIDDOI

AbstractionAbstraction

Expressed in

Abstracted to

<indecs>

Version 2.1 © MUZE Inc April 1999


27,000 terms.

c 23,000 of them are “Relators”.

It is half a million “triple” statements (everything is a relationship).

Can be expressed in different schemas and languages (eg SQL, RDF and OWL) but has its own underlying “neutral” syntax.

Has a dozen ontologies mapped within it (some under development) including MI3P, ONIX, MPEG21 RDD and (a draft) MARC21 ontology.

All terms in each mapped scheme have an “IsSameAs” counterpart in Ontology_X, so it grows as an “ontology of ontologies”.

All triples are “asserted” by at least one authority but can be asserted or denied by any number of authorities (“who sez?”).

Ontology_X can support conflicting world views. It is a deeply postmodern ontology.

Ontology_X structure


Supports the MI3P and ONIX message developments, the IDF metadata profiles and will support the MPEG-21 Rights Data Dictionary.

Used as a basis for systems design by commercial clients – several initial implementations under way (it’s early days yet…).

Ontology_X includes schemas as well as simple term heirarchies. It can contain (for example) the complete specification for MARC21, including all syntactic components.

But it is a very polite ontology and keeps itself quietly out of the way while the message standards get the public attention.

Two projects in 2005 have brought us into the library domain:

- ONIX LicensingTerms Message

- JISC “TIME” project – eBook Metadata Testbed – transformation of eBook metadata between MARC21, ONIX, Dublin Core (and LOM?) schemes. Completing December 2005.

Ontology_X use


Metadata is a set of relationships.

21HasAuthor



21HasAuthorHasTitleIsPriceOf

HasDescriptionHasForeword

IsColorOfIsPlaceOfCreationOf

IsAdaptationOfHasDateOfPublication







HasDateOfPublicationInGermany







HasDateOfPublicationInGermanyHasSmallTextualBitAtTheBeginningWhichMayOrMayNotBeWrittenBySomeoneEls

e


Metadata is a point of view.

21HasAuthor

2 1IsAuthorOf


Some things don’t matter too much to some people.So they get names rather than identifiers.

1 HasAuthor: John Smith




Don’t let that fool you.Names are just lazy identifiers who are averse to

forming committed relationships.




Don’t let that fool you.Names are just lazy identifiers who are averse to

forming committed relationships.Keep an eye on the underlying data model.


The universal data model.


The universal data model.


A point or portion of time which forms a temporal parameter of a Context.

A point or portion of three-dimensional or virtual space which forms a spatial parameter of a Context.

An intersection of time and place.

A Term which describes the nature of a relationship between one entity and another.

The characteristic activity or state of a Context

An Entity in a Context playing a role other than that of Time or Place.

Resource

Resource

Context

Time Place

Verb

1-n 1-n

0-n

RelatorRelator

Relator

Ontologyx™ semantics are based on the principle that meaning is derived from the specific roles which entities play in events.

This is expressed through the underlying Context Model to which all terms are related.

These are the primitive elements of the ontology.

Contexts are of two kinds: Events in which (or as a result of which) something changes, and States, in which they don’t.

The Ontologyx Context Model


Contexts can deal with any kind of activity or state

egOriginatePayCopyTransformDigitizeDeleteAgreePublishProhibitRecordCommissionAggregate

EditJPGIssueInvoiceType99RunProgram123CropRectangularBitmapImageFilmWithCameraType12345DistributeInGermanyOnWednesdaysDanceWithNeighborWithGreenHat


Create Conceive CreatePerceivableOutput Express Perform Fix Say Write Speak ExpressAbout Assert Permit Prohibit Require Deny Agree Declare Ascribe MakeBinaryRelationship Specialize Classify SpecializeContextualClass SpecializeRelator Partition Represent Nominate Identify

These verbs are organized into an ontological hierarchy

NBThis is an illustrative subset of the OntologyX “Family Tree”


Resource

Time

Adaptor

Adaptation

Source of Adaptation

AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

Adapt


An Adaptation event


Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4IsAdaptorInContext

#2 IsAdaptorInContext #1

#1 IsContextOfAdaptor #2

Adapt


An Adaptation event


Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

IsAdaptedBy

#3 IsAdaptedBy #2

#2 IsAdaptorOf #3


An Adaptation event


All possible statements about the simplest Adaptation event

Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

#1 icoAdaptor #2#1 icoAdaptation #3#1 icoSourceOfAdaptation #4#1 icoTimeOfAdapting #5#1 icoPlaceOfAdapting #6#2 IsAdaptorInContext #1#3 IsAdaptationInContext #1#4 IsSourceOfAdaptationInContext #1#5 IsTimeOfAdaptingInContext #1#6 IsPlaceOfAdaptingInContext #1#2 IsAdaptorOf #3#3 IsAdaptedBy #2#2 IsAdaptorFrom #4#4 IsSourceOfAdaptationUsedBy #2#2 IsAdaptorAtTime #5#5 IsTimeOfAdaptingBy #2#2 IsAdaptorInPlace #6#6 IsPlaceOfAdaptor #2#3 IsAdaptedFrom #4#4 IsSourceOfAdaptationOf #3#3 IsAdaptationAtTime #5#5 IsTimeOfAdaptation #3#3 IsAdaptationInContextWithPlaceOfAdaptor #6#6 IsPlaceOfAdaptation #3#4 IsSourceOfAdaptationAtTime #5#5 IsTimeOfAdaptingFromSource #4#4 IsSourceOfAdaptationInPlace #6#6 IsPlaceOfAdaptingFromSource #4#5 IsTimeOfAdaptingInPlace #6#6 IsPlaceOfAdaptingAtTime #5

The Ontologyx Context Model – Family Relational View


Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

#1 icoAdaptor #2#1 icoAdaptation #3#1 icoSourceOfAdaptation #4#1 icoTimeOfAdapting #5#1 icoPlaceOfAdapting #6#2 IsAdaptorInContext #1#3 IsAdaptationInContext #1#4 IsSourceOfAdaptationInContext #1#5 IsTimeOfAdaptingInContext #1#6 IsPlaceOfAdaptingInContext #1#2 IsAdaptorOf #3#3 IsAdaptedBy #2#2 IsAdaptorFrom #4#4 IsSourceOfAdaptationUsedBy #2#2 IsAdaptorAtTime #5#5 IsTimeOfAdaptingBy #2#2 IsAdaptorInPlace #6#6 IsPlaceOfAdaptor #2#3 IsAdaptedFrom #4#4 IsSourceOfAdaptationOf #3#3 IsAdaptationAtTime #5#5 IsTimeOfAdaptation #3#3 IsAdaptationInContextWithPlaceOfAdaptor #6#6 IsPlaceOfAdaptation #3#4 IsSourceOfAdaptationAtTime #5#5 IsTimeOfAdaptingFromSource #4#4 IsSourceOfAdaptationInPlace #6#6 IsPlaceOfAdaptingFromSource #4#5 IsTimeOfAdaptingInPlace #6#6 IsPlaceOfAdaptingAtTime #5

Modified

IsVersionOf

LastChanged

TerritoryOfUse

EditedBy

The Ontologyx Context Model – Family Relational View

The statements map to commonplace descriptive semantics


Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

The Ontologyx Contextual transformation

Each Context has two “views” – the contextual view…


Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

Each Context has two “views” – the contextual view…and the relational view.



Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

An Adaptation event

Each Context has two “views” – the contextual view…and the relational view.

The relationship between the two provides the basis of Ontologyx transformation capability (“contextual transformation”).



Resource

Time

Adaptor

Adaptation


AdaptingEvent

Time ofAdapting

Place ofAdapting

#5 #6

#2

#1

#3

#4

An Adaptation event

Statements like this made in the relational view:

X MadeBy John Smith

X AdaptedFrom Y

X TimeOfCreation 1996

X MadeIn London

means that there was an event Z like this (shown in the contextual view):

Z icoAdapter John Smith

Z icoAdaptation X

Z icoSourceOfAdaptation Y

Z icoTimeOfAdaptation 1996

Z icoPlaceOfAdaptation London



Resource

Time

Resource

Verb

Recording Session 1Songs (1) Someday (2) NeverProducer Bill BrownEngineer Jim ScarlettStartTime 2004-06-27 14:30EndTime 2004-06-27 16:20Place Clapham Studios AVocal Sue WhiteBacking Vocal Ian GreenKeyboards Bert Blue

Recording Session 2Songs (1) Someday (2) AnydayProducer Bill BrownEngineer Ann PinkStartTime 2004-06-28 10:30 EndTime 2004-06-28 13:55Place Clapham Studios BVocal Sue WhiteKeyboards Sally PlumFlute Ian Green

Song: SomedayProducer Bill BrownEngineer Jim Scarlett, Ann PinkVocal Sue WhiteBacking Vocal Ian GreenKeyboards Bert BlueRecorded 27-28 June 2004Recorded at Clapham Studios A, Clapham Studios B

Contextual semantics

Song: NeverProducer Bill BrownEngineer Jim ScarlettVocal Sue WhiteBacking Vocal Ian GreenKeyboards Bert BlueRecorded 27 June 2004Recorded at Clapham Studios A

Song: AnydayProducer Bill BrownEngineers Ann PinkVocal Sue WhiteFlute Ian GreenKeyboards Sally PlumRecorded 28 June 2004Recorded at Clapham Studios B

Resource semanticsSimple transformation example…


Contextual transformation can be carried out to any level of complexity and granularity


COA (“Contextual Ontologyx Architecture”) Framework

The COA Framework is an “ontology starter pack”: a basic ontology which provides a complete Semantic framework within which all data elements can be placed. All Ontologyx client ontologies are based on this.

Attribute Types(All entities may have these)

(“strings”)Descriptor Name Identifier Annotation

(“controlled values”)Category Class Characteristic Quantity Quality TruthFlag

(“bags”)Composite

Element Classes (Context Model)(All entities belong to one of these)

Key Relators

(“parent/child”) IsSubClassOf IsSubRelatorOf

(“class/instance”) IsA

(“equivalence”) IsSameAs IsSubstitutableFor

(“part/whole”) IsPartOf

(“reverse links”) IsReciprocalOf

(“type/value”) IsOneOf

(“representation”) HasValue HasElement HasDatatype HasCardinality

Agent

PlaceTime

Resource

Context


The ERMI problem: how to deconstruct things like this…

and reconstruct them into something a computer can deal with.

The right to use licensed materials in collections or compilations of materials assembled in a print format by faculty members for use by students in a class for purposes of instruction

Or this…

[The Licensee may supply to an Authorised User of another library {within the same country as the Licensee}a copy of an individual document being part of the Licensed Materials by post, fax or electronic transmission via the Internet or otherwise, for the purposes of research or private study and not for Commercial Use.]

[The Licensee may supply to an Authorised User of another library {within the same country as the Licensee}(whether by post or fax [or secure transmission, using Ariel or its equivalent, whereby the electronic file is deleted immediately after printing]), for the purposes of research or private study and not for Commercial Use, a single paper copy of an electronic original of an individual document being part of the Licensed Materials.]

Or this…

Contextual approach to licensing and rights metadata


Contextual approach to licensing terms

LicensingEvent UsagePermits (MAY)

1-n

Usage

Prohibits (MUST NOT)

0-n

Payment

Activity Report

etc

Requires (MUST)

0-n

Has Exception

Has Condition

This structure allows for whatever level of flexibility or granularity may be required now or in the future.


Resource

Time Place

Party

Use

<UsageParty> (1-n) <UsedResource> (1-n)

<Tool> (0-n)<Medium> (0-n)<OtherResource> (0-n)

<UsageTime> (0-n) <UsagePlace> (0-n)

<Exception> (0-n)<Condition> (0-n)<ChainedUsage> (0-n)

Act

<PartyRole> (1-n)

UsagesONIX Usage

Compositestructure


Resource

Time Place

Party

Use<PartyRole> (1-n)

10 basic usesSearchAcquireAccess

PossessIncludeRecordDerive

ProvideRelate

Destroy

Usages Allowed values


Resource

Time Place

Party




ProvideRelate

Destroy

Copy eCopy CopyPart Adapt AdaptText Translate Transform etc

Each of these uses has differentspecialized “children”



Resource

Time Place

Party




ProvideRelate

Destroy



You can go as far as you like with verbs…“ProvideLimitedNumberOfPrintOrDigitalCopiesForAuthorizedUserOfAnotherLibraryInTheSameCountryToAccessAndPossess”



Resource

Time Place

Party




ProvideRelate

Destroy



You can go as far as you like with verbs…“ProvideLimitedNumberOfPrintOrDigitalCopiesForAuthorizedUserOfAnotherLibraryInTheSameCountryToAccessAndPossess”…but better to keep the verb simple and look at the other variables in the event.

Usages


ERMI modelling at present

Complex element: Permission• Permitted Use: ILL

• Method: Print or Fax• Constraint: Record-keeping required

This slide adapted from ERMI presentation


Resource

Time Place

Party

Use

<Medium> Fax, Post

<Condition> Record Keeping

Act

<UseType> ILL

Usages ERMI Usage example in ONIX

model


Resource

TimePlace

3 Verbs3 Parties 2 Resources2 Usages1 Purpose1 Place

InterLibraryLoan_1 (example #27)

ONIX Message Usage Model examples

PartyParty

[Cox] Clause 4.1 (alternative b) [The Licensee may supply to an Authorised User of another library {within the same country as the Licensee}a copy of an individual document being part of the Licensed Materials by post, fax or electronic transmission via the Internet or otherwise, for the purposes of research or private study and not for Commercial Use.]


Resource

TimePlace

Party



{P1}AcademicLibrary


PartyParty



Resource

TimePlace

Party


{P1}Provide


{P1}AcademicLibrary

Resource {R2}DigitalResource,Printed Resource


PartyParty



Resource

Time

Party


{P1}Provide

{R1}DigitalResource




PartyParty

{R2}PartCopyOf{P1}{P1}AcademicLibrary



Resource

TimePlace

Party


{P1}Provide

{R1}DigitalResource


{P2}Access,Possess



PartyParty

{R2}PartCopyOf{P1}

{P2}

{P1}AcademicLibrary



Resource

TimePlace

Party


{P1}Provide

{R1}DigitalResource


{P2}Access,Possess



PartyParty

{R2}PartCopyOf{P1}

{P2}

Purpose>NonCommercialUse

{P1}AcademicLibrary



Resource

TimePlace

Party


{P1}Provide

{R1}DigitalResource


{P2}Access,Possess



Party{P2}AuthUseOfLibrary{P3}Party

{R2}PartCopyOf{P1}

{P3}AcademicLibrary

{P2}


{P1}AcademicLibrary



Resource

TimePlace

Party


{P1}Provide

{R1}DigitalResource


{P2}Access,Possess



Party{P2}AuthUseOfLibrary{P3}Party

{L1}Country

{P1}HasPlaceOfPremises{L1}

{P3}HasPlaceOfPremises{L1}

{R2}PartCopyOf{P1}

{P3}AcademicLibrary

{P2}


{P1}AcademicLibrary



An ontology provides the semantic building blocks for a data model or implementation model.

It can also provide tools for managing allowed values and mapping data from different schemes.

Dublin Core is an example of a metadata scheme without an ontology. There is no clear model of the relationships between its terms. This has made consistent implementation problematic and limited the potential of DC.

FRBR would benefit from an ontology, especially with the emphasis being placed on relationships.

The value of ontologies


The FRBR systems you are designing now will be mainstream in several years time. Is your world going to get simpler or more complex? Can you predict the functional requirements you will have for 2010 or 2015? If not, then focus on the underlying flexibility of the model. Settle the model and put the change management into an ontology.

Use what is useful in other people’s standards and metadata, and find ways of helping them make them better so that you can get more benefit.

FRBR thoughts from a slightly different planet…


Things should be as simple as possible, but not simpler.(Einstein)

Documents

Godfrey Rust, FRBR Workshop, Ohio May 4 2005 © Rightscom 2005 Thoughts from a different planet