This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• 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
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
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”.
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…
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”)