1. Developing a Metadata Exchange Format for Mathematical Literature David Ruddy Project Euclid Cornell University Library DML 2010 Paris 7 July 2010

2. History Part of the early DML/WDML discussions Initial version of MLAP (qualified Dublin Core), 2004-2005 Effort on a simple DC profile in 2005-2006 – Thierry Bouche, Thomas Fischer, Claude Goutorbe, David Ruddy Dublin Core community refines and documents its concept of an Application Profile, 2007-2009

3. Dublin Core Application Profile Dublin Core Abstract Model – Essentially, an RDF model All properties, vocabularies, and syntax encoding schemes identified by URIs Global semantic interoperability Semantic web, linked data

4. DCAP Compliance Functional requirements Domain model Description set profile Usage guidelines Syntax guidelines

5. MLAP Functional Requirements Typical functions of bibliographic records: find, identify, select, obtain Multilingual support Potential capabilities: – Linking to name authority records – Citation analysis – Embedded OpenURL Context Objects – Rich subject analysis

6. MLAP: Out of Scope Description of publications not available online Identification and description of distinct FRBR entities (supporting version control) Structured author/contributor descriptions Machine-processable descriptions of access embargo periods

7. MLAP Domain Model Entities of the application profile, and their relationships Publication Container 0.. 1 Creator 0.. n Agent

8. MLAP Description Set Profile Defines how metadata records adhere to the Description Set Model DSP uses a DC constraint language – Statement templates – Value constraints XML expression of the MLAP DSP: http://projecteuclid.org/documents/ metadata/mlap/mlap_dsp.xml

9. MLAP Property Namespaces DCMI Metadata Terms PRISM: Publishing Requirements for Industry Standard Metadata DC Collections Metadata Terms

10. MLAP Usage Guidelines Human-readable presentation of DSP Additional content value rules and/or recommendations Examples MLAP usage guidelines (HTML): http://projecteuclid.org/documents/ metadata/mlap/

11. MLAP Syntax Guidelines The Description Set Model is neutral regarding syntactic encoding of description sets DC provides specifications for how description sets may be serialized in plain text, XML, RDF/XML, and in XHTML meta tags MLAP usage guidelines encode examples in plain text, with alternate encodings in XML, and eventually RDF/XML Neutral approach allows for multiple ways to exchange metadata

12. @prefix dcterms: DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "<div xmlns="http://www.w3.org/ 1998/Math/MathML">On L -functions of twisted 4 -dimensional quaternionic Shimura varieties " Language ( en ) SyntaxEncodingSchemeURI ( <http://www.w3.org/ 1999/02/22-rdf-syntax-ns#XMLLiteral> ) )

13. <dcds:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/"> <dcds:literalValueString xml:lang="en" dcds:sesURI="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral"> On L -functions of twisted 4 -dimensional quaternionic Shimura varieties

14. <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/"> On L -functions of twisted 4 -dimensional quaternionic Shimura varieties

17. Minimal Record Requirements Four required elements:

18. Potential for Rich Records Multilingual values for many properties MathML in titles and abstracts Complete reference lists OpenURL Context Objects for described publication and all referenced resources

19. Dedicated Identifiers For example: for the publication’s HTTP URI, instead of Also: Likewise, the publicationContainer entity

20. Unresolved Issues Optimized for serial literature Contributor property – Not easy to capture a role attribute – Potential solutions add complexity MSC codes do not have URIs