Developing a metadata exchange format for mathematical literature
This presentation is the property of its rightful owner.
Sponsored Links
1 / 20

Developing a Metadata Exchange Format for Mathematical Literature PowerPoint PPT Presentation


  • 74 Views
  • Uploaded on
  • Presentation posted in: General

Developing a Metadata Exchange Format for Mathematical Literature. David Ruddy Project Euclid Cornell University Library DML 2010 Paris 7 July 2010. History. Part of the early DML/WDML discussions Initial version of MLAP (qualified Dublin Core), 2004-2005

Download Presentation

Developing a Metadata Exchange Format for Mathematical Literature

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Developing a metadata exchange format for mathematical literature

Developing a Metadata Exchange Format for Mathematical Literature

David Ruddy

Project Euclid

Cornell University Library

DML 2010 Paris

7 July 2010


History

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


Dublin core application profile

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


Dcap compliance

DCAP Compliance

  • Functional requirements

  • Domain model

  • Description set profile

  • Usage guidelines

  • Syntax guidelines


Mlap functional requirements

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


Mlap out of scope

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


Mlap domain model

MLAP Domain Model

  • Entities of the application profile, and their relationships

Publication

Publication

Container

0 . . 1

Creator

Agent

0 . . n


Mlap description set profile

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


Mlap property namespaces

MLAP Property Namespaces

  • DCMI Metadata Terms

  • PRISM: Publishing Requirements for Industry Standard Metadata

  • DC Collections Metadata Terms


Mlap usage guidelines

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/


Mlap syntax guidelines

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


Developing a metadata exchange format for mathematical literature

@prefix dcterms: <http://purl.org/dc/terms/>

DescriptionSet (

Description (

ResourceURI ( <http://example.org/a/resource/uri > )

Statement (

PropertyURI ( dcterms:title )

LiteralValueString ( "<div xmlns="http://www.w3.org/

1998/Math/MathML">On <math alttext="$L$">

<mi>L</mi></math>-functions of twisted

<math alttext="$4$"><mn>4</mn></math>-dimensional

quaternionic Shimura varieties</div>"

Language ( en )

SyntaxEncodingSchemeURI ( <http://www.w3.org/

1999/02/22-rdf-syntax-ns#XMLLiteral> )

)

)

)

)


Developing a metadata exchange format for mathematical literature

<?xml version="1.0" encoding="utf-8"?>

<dcds:descriptionSet

xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">

<dcds:description dcds:resourceURI="http://example.org/a/resource/uri">

<dcds:statement dcds:propertyURI="http://purl.org/dc/terms/title">

<dcds:literalValueString xml:lang="en"

dcds:sesURI="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">

<div xmlns="http://www.w3.org/1998/Math/MathML">

On <math alttext="$L$"><mi>L</mi></math>-functions of

twisted <math alttext="$4$"><mn>4</mn></math>-dimensional

quaternionic Shimura varieties</div>

</dcds:literalValueString>

</dcds:statement>

</dcds:description>

</dcds:descriptionSet>


Developing a metadata exchange format for mathematical literature

<?xml version="1.0" encoding="utf-8"?>

<rdf:RDF

xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:dcterms="http://purl.org/dc/terms/">

<rdf:Description rdf:about="http://example.org/a/resource/uri">

<dcterms:title rdf:parseType="Literal">

<div xmlns="http://www.w3.org/1998/Math/MathML">

On <math alttext="$L$"><mi>L</mi></math>-functions of

twisted <math alttext="$4$"><mn>4</mn></math>-dimensional

quaternionic Shimura varieties</div>

</dcterms:title>

</rdf:Description>

</rdf:RDF>


Minimal record requirements

Minimal Record Requirements

  • Four required elements:

    <dcterms:title>

    <dcterms:issued>

    <dcterms:bibliographicCitation>

    <prism:url>


Potential for rich records

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


Dedicated identifiers

Dedicated Identifiers

  • For example:

    <prism:url>

    for the publication’s HTTP URI, instead of

    <dcterms:identifier>

  • Also:

    <prism:issn>

    <prism:eIssn>

    <prism:isbn>

    <prism:doi>

  • Likewise, the publicationContainer entity


Unresolved issues

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


  • Login