1. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Godfrey Rust, Ontologyx DOI Metadata consultant Metadata interoperability for real

2. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Crossref mEDRA Metadata interoperability for real

3. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Crossref mEDRA Metadata interoperability for real

4. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability semantic problems 1.Different names (and languages) for the same thing (journal_article vs SerialArticleWork) 2.Data elements at different levels of speciality (title vs FullTitle,AlternativeTitle). 3.Different allowed values for elements (pii vs not pii) 4.Data at different levels of granularity (journal_article vs SerialArticleWork/SerialArticleVersion). 5.Data in different structures (article as attribute of journal or vice versa). 6.Data from different sources (local codes vs ONIX codes). 7.Contextual meaning (DOI of what…?) 8.Different representation (1 title vs n titles). 9.Different mandatory requirements (ISSN mandatory vs optional). 10.Schemas are being updated all the time. All this is tricky one-to-one. Many-to-many it is a nightmare.

5. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Crossref mEDRA Metadata interoperability problems

6. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Crossref mEDRA CAL Metadata interoperability problems

7. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability problems Crossref Any RA mEDRA CAL

8. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability solutions 1.iDD (indecs Data Dictionary): contextual mapping of terms and schemas to the IDFs data dictionary (or ontology). 2.RMD (Resource Metadata Declaration): a single interchange schema for a domain supported by the iDD (journalRMD is the prototype) 3.Cross-domain interoperability: an underlying generic interchange scheme (COA).

9. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 iDD (indecs Data Dictionary) Starts from the indecs contecs:dd Context Model. Built on the Contextual Ontologyx Architecture (COA), the formal manifestation of the indecs framework model by Ontologyx: This represents an ontology language (extensible to cover OWL and other axioms) which provides the iDDs computing power). iDD is an ontology of ontologies. Contains other dictionaries or schemes in full (including representations of messages). Built entirely out of triples (expressed in XML/RDF): eg FullTitle IsSubClassOf Title. Extremely flexible: iDD is a database of relationships, not just a list or set of tables. Primitive Elements Context, Time, Place, Resource Representatives Descriptor, Name, Identifier, Annotation Category Type, Aspect, Quality, Quantity, Flag Composite Relators IsSubClassOf, IsSubRelatorOf, IsA, IsSameAs, IsReciprocalOf, HasPart, HasElement, HasCardinality, HasDataType etc

10. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 iDD tackling interoperability problems 1.iDD maps different names (and languages) for the same thing (journal_article vs SerialArticleWork) 2.iDD hierarchy links data elements at different levels of speciality (title vs FullTitle,AlternativeTitle). 3.iDD manages different allowed values for elements. 4.iDD stores data at different levels of granularity (journal_article vs SerialArticleWork/SerialArticleVersion). 5.iDD stores data in different structures (article as attribute of journal or vice versa). 6.iDD stores data from different sources (local codes vs ONIX codes). 7.iDD maps contextual meaning (DOI of what…?) 8.iDD maps different representation (1 title vs n titles). 9.iDD identifies different mandatory requirements (ISSN mandatory vs optional). 10.iDD supports schemas being updated all the time. (Health warning: some of this functionality is only partially developed, but the semantics to support it are built into the ontology )

11. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 iDD first release Will contain only the terms needed to support the schemas that are mapped into it (Crossref, mEDRA, CAL journal schemes). Other terms added or released as needed. Current draft shown here as an html view. [This slide was followed by an interactive demonstration of the iDD].

12. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability via journalRMD

13. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability via journalRMD Crossref Any RA mEDRA CAL BEFORE

14. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability via journalRMD Crossref Any RA mEDRA CAL After

15. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting 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…

16. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability via journalRMD Crossref Any RA mEDRA CAL

17. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability via journalRMD Crossref Any RA mEDRA CAL iDD Update Map terms and schemes

18. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability via journalRMD Crossref Any RA mEDRA CAL iDD Update Map terms and schemes THE VIRUS CHECKER MODEL

19. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Cross-domain interoperability…

20. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Cross-domain interoperability…

21. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Cross-domain interoperability…

22. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Cross-domain interoperability… For interoperability across domains, there is a highly generic COA schema.

23. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability real world assumptions Many DOI RAs will want to interchange metadata of many different types. RAs will use an ever increasing range of standard and proprietary terms and schemes. Domain metadata will be mixed across domains in many combinations. New versions of everything will keep coming out.

24. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability requirements Validate, test and implement journalRMD and iDD. Implement new RMDs for domains as required (it takes two or more to interoperate…). RAs to map terms and schemes as needed. iDD has other potential to support DOI interoperability beyond metadata: eg in defining constaints of DOI APs (discussion for tomorrows workshop…) All now driven by real business requirements. (Notes: iDD mapping is an aid to system and schema design).

25. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability elsewhere ONIX mapping to be completed following mEDRA validation (bookRMD?). MI3P (music industry dictionary and message standards) is built on COA and supports dozens of draft standard messages. MPEG-RDD Registration Authority will be implemented on COA architecture. ISO codes already in iDD. Other schemes (Dublin Core, MARC, PRISM, SCORM, CIDOC, SMPTE etc) can be included as needed according to RA demand.

26. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Metadata interoperability conclusion The combination of DOI and the iDD/RMD tools now offer a unique and unparalleled opportunity for metadata interoperability. Godfrey Rust, Ontologyx © 2004Presentation to DOI Members meeting June 2004

27. Godfrey Rust, Ontologyx © Rightscom 2004Presentation to DOI Members meeting June 2004 Godfrey Rust, Ontologyx DOI Metadata consultant Metadata interoperability for real