Post on 27-Mar-2015
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Metadata interoperability workshop
• using the iDD to define entities (what is being identified) • using the IDD to map metadata schemes (using other schemes)• using the iDD by RAs: access, content, management
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
“infant iDD” status report
What has iDD got today? COA (Contextual Ontologyx Architecture): model and “language”OntologyX: 150 “families”, 20000+ terms and underlying contextual structure.Mapping syntax & methodology for global, contextual and representative semantics.Initial RA schemes (crossref, mEDRA) formally mapped.Provisional or partial mappings of RDD, ONIX, MI3P and others.Some automated XML schema export.OntX in SQL database (RDF database under development as persistent platform).Strategic: OntologyX/iDD repository for iDD, MPEG-RDD, MI3P, [ONIX].
What are we developing?RDF-based persistence platform – version control, contextual management.Complete formal mapping of ONIX.Contextual transformation engine.Full XML schema import/export. Web mapping tool for RAs, including automated update of local schemes.User agreements.etc etc
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Act
Verb
Resource
Resource
Resource
Time
Context
PnTn
Rn
C1
1-nPlace1-n
0-n
RelatorAn intersection of time and place.
An Entity in a Context playing a role other than that of Time or Place.
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.
The Ontologyx Context Model
A Term which describes the nature of a relationship between one entity and another.
The characteristic activity or state of a Context
Ontologyx semantics are based on the principle that meaning is derived from the specific roles which entities play in events.
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Example: All possible statements about the simplest Adaptation event
Resource
Time
Adaptor
Adaptation
Source of 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
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
COA (Contextual Ontologyx Architecture) – “ontology starter pack”
Context Time Place Resource Agent
RepresentativeDescriptor (“string”) Name Identifier AnnotationCategory (“denotational string”, “semantic string” or “controlled value”) Type Boolean Characteristic Quality Adjective Property QuantityComposite (“element group” or “bag”)
RelatorIsSubClassOf, IsSubRelatorOf, IsA, IsSameAs, IsPartOf, IsReciprocalOf,HasDataType, HasCardinality etc
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
iDD structure
Authorities (“namespaces”) distinct.
Terms have global and contextual meaning. In many schemes this is not clear because there is no underlying dictionary, so the distinctions have to be made.
eg Medra:ContributorRole
Contextually:
“An ONIX code indicating the role played by a person or corporate body in the creation of the product.”
Globally:
“The role played by a person or corporate body in the creation of a product”.
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
medra:LastPageNumberxref:last_page
cal:LastPage
idd:EndPageNumber
IsSameAsIsSameAs
IsSameAs
Names DescriptionsCommentsInternal ontology links
ontx-id
ontx:EndPageNumber
IsSameAs
IsSubClassOf
cal:Page
ontx-id
ontx-id
ontx-id
ontx-id
ontx-id
doi>
ontx-id
iDD global mapping
xxx:Last page
IsSameAs
ontx-id
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Contextual mapping: JournalTitle example
JournalTitle IsSubClassOf TitleJournalTitle HasCCS JournalTitle_CCS
#1 IsA JournalTitle#1 IsTitleOf #2#2 IsA Journal
so if you come across…
“x” IsJournalTitleOf “y”
you can deduce that…
“x” IsA Title“x” IsTitleOf “y”“y” IsA Journal
CCS(Contextual Constraint Set)
A set of triples which provide contextual semantic rules for a term
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Contextual mapping: HostJournalTitle example
HostJournalTitle IsSubClassOf JournalTitleHostJournalTitle IsSubClassOf HostTitleHostJournalTitle HasCCS HostJournalTitle_CCS
#1 IsA HostJournalTitle#1 IsTitleOf #2#2 IsContentOf #3#3 IsA Journal
CCS(Contextual Constraint Set)
A set of triples which provide contextual semantic rules
Note the critical importance of Relators in OntologyX/iDD.
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Representational mapping: DOI Kernel example
ResourceKernelMetadataDeclaration HasElement #1#1 IsA DOI#1 HasDataType DOI#1 HasCardinality !1
ResourceKernelMetadataDeclaration HasElement #2.n #2.n IsA ResourceName#2.n HasElement #3
#3 IsA Type#3 IsOneOf KernelResourceNameType_AVS
#2.n HasElement #4#4 IsA PrimaryLanguage#4 IsOneOf IsoLanguage_AVS#4 HasCodeSet Iso639A2LanguageCode_CS
#2.n HasMinCardinality !0#2.n HasMaxCardinality !n
ResourceKernelMetadataDeclaration HasElement #5.n #5.n IsA ResourceIdentifier#5.n HasElement #6
#6 IsA Type#6 IsOneOf KernelResourceIdentifierType_AVS
#5.n HasMinCardinality !0#5.n HasMaxCardinality !n
etc
RCS(Representational Constraint Set)
A set of triples which provide representational semantic rules.
All schemes are representedfirst as an RCS.
OK – but what is the semantic relationship between these elements? We need a CCS…
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Contextual mapping: DOI Kernel example
(ResourceKernalMetadataDeclaration_CCS)#1001 IsA DoiResource#1001 HasDOI #1#1001 HasResourceName #2.n
#2.n HasPrimaryLanguage #3.n#2.n IsA #4
#1001 HasResourceIdentifier #5.n#5.n IsA #6
etc
ResourceKernelMetadataDeclaration SharesValuesWith ResourceKernelMetadataDeclaration_CCS
CCS(Contextual Constraint Set)
The # (variable) values are common to an RCS and its CCS: this is the mapping which allows OntologyX/iDD to interpret any schema in common terms.
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
journalRMD (“Journal Resource Metadata Declaration”)
An XML schema for journal metadata supporting Crossref, mEDRA, CAL and other likely requirements.
Prototype for RMDs for any other domains (bookRMD, coursepackRMD…)
journalRMD is designed for interchange: it is not a replacement for eg Crossref or ONIX messages (though it could be used by anyone).
It is similar to Crossref and mEDRA, but richer and less customized. For example…
journalRMD allows for registration of DOIs issued against Journals, Volumes, Issues and Articles, and their Fixations (8 different ResourceTypes where mEDRA and Crossref have no more than four).
journalRMD allows for the use of DOIs to link all Resources.CAL will base their schema on journalRMD, but will probably customize.
Requires XSLT transforms from Crossref, mEDRA and other participants (being done).
iDD mappings support automated change management of mappings and allowed values…
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Metadata interoperability via journalRMD
CrossrefCrossref
Any RAAny RA
mEDRAmEDRA
CALCAL
ONIXMedraSerialArticle.xml
CALJournalArticle.xmlAnyJournalMetadata.xml
crossref3.0.0.xml
XsltTransform.xsl
journalRMD.xml
XsltTransform.xsl
XsltTransform.xsl
XsltTransform.xsl
iDDiDD
Update
Map terms and schemes
THE “VIRUS CHECKER” MODEL
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Cross-domain interoperability…
For interoperability across domains, there is a highly generic COA schema.
journalRMD.xml
Coa.xml
ResourceKernel.xml
CoursepackRMD.xml
XsltTransform.xsl
XsltTransform.xsl
XsltTransform.xsl
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
Contextual mapping: Fragment of JournalRMD to Kernel
JournalRMD HasElement #1.n#1.n HasElement #2.n
JournalRMD HasElement #3.nJournalRMD HasElement #4.n
#4.n HasElement #5.n
JournalRMD_CCS:#1001 IsA Journal#1001 HasDOI #2.n#1001 HasContentIssue #1002.n#1002.n HasContentArticle #1003.n#1003.n HasDOI #5.n
Kernel_CCS#1001 HasDOI #1#1001 HasResourceIdentifier #2.n#1001 HasResourceType #3.n
JournalRMD_Kernel_CCSIF (#B3.n IsA Journal) THEN (#A2.n IsSameAs #B#1) (If Kernel is for Journal, it’s a DOI)IF (#B3.n IsA Article)THEN (#A2.n IsSameAs #B#2.n) (If Kernel is for an Article, it’s an Identifier)AND (#B3.n HasValue HostJournalDOI) (…and its type is “HostJournalDOI”)
CCS
CCS
CCS
RCS
RCS
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
COA generic XML schema
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
“infant iDD” issues
Access?
Mapping methodology?
Agreements?
Costs?
(all can be prototyped with JournalRMD)
Godfrey Rust, Ontologyx © Rightscom 2004
DOI Interoperability Workshop June 2004
iDD use for defining APs?
We are likely to need a schema for declaring attributes of a DOI-AP to support its discovery and maintenance and operation.
An instance of such a schema may contain, eg:
ResourceType SoundRecordings,SoundCarriers,Compositions
ServiceType LicenseApplication, LicensingQuery
Places [list of TerritoryCodes]
AgentType NOT Consumer
Terms used in such a schema would be registered in the iDD.
(nb: Each of these terms will have a DOI, but the iDD names are the people friendly identifiers, unique within iDD).