Talk:OAI-ORE Publication Item

From MPDLMediaWiki
Jump to navigation Jump to search

The basic question will be if we want to express eSciDoc publication item in oai-ore or if we additionally want to use only the standard namespaces from the specification (which is no MUST).

Example: Aggregation of a eSciDoc publication item[edit]

This aggregation is an example of the publication escidoc:66202.

Aggregation[edit]

PubItem Aggregation.jpg

Red framed resources might be aggregations themselves.


Could a ReM part look as follows?

       Previous Versions
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/pubman/item/escidoc:66202:1"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/pubman/item/escidoc:66202:2"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/pubman/item/escidoc:66202:3"/>
       ...
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/pubman/item/escidoc:66202:13"/>
       Components
       <ore:aggregates rdf:resource="http://coreservice.mpdl.mpg.de:8080/ir/item/escidoc:66202/components/component/escidoc:68328"/>
       <ore:aggregates rdf:resource="http://coreservice.mpdl.mpg.de:8080/ir/item/escidoc:66202/components/component/escidoc:68329"/>
       Metadata formats
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=bibtex"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=endnote"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=escidoc"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=APA_text/html"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=APA_application/pdf"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=APA(Snippet)_application/xml"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=AJP_text/html"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=AJP_application/pdf"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de:8080/dataacquisition/view/unapi?id=escidoc:66202&format=AJP(Snippet)_application/xml"/>
       Persons & Affiliations
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/cone/html/persons/urn:cone:persons177"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/cone/html/persons/urn:cone:persons51"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/cone/html/persons/urn:cone:persons18"/>
       <ore:aggregates rdf:resource="http://pubman.mpdl.mpg.de/cone/html/persons/urn:cone:persons78"/>
       <ore:aggregates rdf:resource="http://coreservice.mpdl.mpg.de:8080/oum/organizational-unit/escidoc:55201"/>
       <ore:aggregates rdf:resource="http://coreservice.mpdl.mpg.de:8080/oum/organizational-unit/escidoc:55202"/>
       <ore:aggregates rdf:resource="http://coreservice.mpdl.mpg.de:8080/oum/organizational-unit/escidoc:55216"/>
       <ore:aggregates rdf:resource="http://coreservice.mpdl.mpg.de:8080/oum/organizational-unit/escidoc:55204"/>
       Other presentations
       <rdfs:seeAlso rdf:resource="http://pubman.mpdl.mpg.de/pubman/item/escidoc:66202:14"/>
       <ore:similarTo rdf:resource="http://dx.doi.org/10.1073/pnas.0903616106"/>

I'm not quite sure what previous versions are, but if this is the "intellectual versioning" thing, then they should not be aggregated, i'd say, but have resource maps of their own.--Robert 13:17, 26 June 2009 (UTC)

i think all versions are not important, rather only releases. Agree that intellectual versioning should not be aggregated, it is an item on its own --Natasa 10:58, 30 June 2009 (UTC)


Authors and should be rather linked via rdf:resource attributes of dc:creator, possibly with a nested link to the organizational units, i'd say.--Robert 13:17, 26 June 2009 (UTC)

Discussion[edit]

  • Is Max Planck Society part of the aggregation or is this implicitly via MPI for Psycholinguistics
Should be a relation, no aggregation--Friederike 06:48, 29 June 2009 (UTC)
  • Is MPI for Psycholinguistics part of the aggregation or is this implicitly via the research groups
Should be a relation, no aggregation--Friederike 06:48, 29 June 2009 (UTC)
  • Is the collection of the publication a resource of the publication aggregation, as well?
I think the publication aggregation will be a resource of the collection aggregation, but I am not sure other way round.--Friederike 11:54, 26 June 2009 (UTC)
  • Are the escidoc metadata profiles part of the aggregation, or is this implicitly via escidoc.xml
Also a relation?, but anyway referenced in the escidoc.xml --Friederike 06:48, 29 June 2009 (UTC)
  • If an item has a DDC Subject, should the DDC Vocabulary be part of the aggregation?
i think things like the DDC Vocabulary are only tangential to the publication, and in addition can be inferred when following the DDC Subject URLs which actually make up part of the metadata of the item.
  • Are the different 'representations' of an item (e.g. citation styles) part of the aggregation or is this a relation like ore:similarTo ?


The (cone) person should probably also be a relation and not an aggregation.--Friederike 06:48, 29 June 2009 (UTC)

Previous version is a relation, no aggregation--Friederike 06:58, 29 June 2009 (UTC)

In general, i think we should first determine which atomic resources we want to publish as simple linked data; once this is in place, it will be easier to experiment with different levels of granularity/completeness of resource maps. experimentation and flexibility in this regard will be needed anyway, because the use cases for resource maps are not entirely clear yet - or are they?--Robert 12:39, 26 June 2009 (UTC)

Aggregation Metadata[edit]

Publication Item Graph Comment
Creator.CreatorType.Person
Creator.CreatorType.Organization
Creator.CreatorType.Person
Creator.CreatorType.Organization
Title
Alternative Title
Language
Identifier.Id TODO: Different types
PublishingInfo.Publisher
PublishingInfo.Place
PublishingInfo.Edition
Date TODO: Different types
TotalNumberOfPages
Degree
Abstract
Subject
TableOfContents
Location
Genre
Event
Language
Review Method
Source
Source.Title
Source.Genre
Source.Alternativetitle
Source.Creator.CreatorType.Person
Source.Creator.CreatorType.Organization
Source.Volume
Source.Issue
Source.StartPage
Source.EndPage
Source.Identifier.Id
Source.TotalNumberOfPages
Source.Publisher
Source.PublishingInfo
Source.Place
Source.Edition

Example Data[edit]

The following examples have been copied from the ORE User Guide - Resource Map Implementation in RDF/XML. Please note that currently no OAI-ORE implementation seems to be available for arXiv, therefore all corresponding URLs can't be resolved.

Description of ReM[edit]

arXiv example:
   <rdf:Description rdf:about="http://arxiv.org/rem/rdf/astro-ph/0601007"> 
<ore:describes rdf:resource="http://arxiv.org/aggregation/astro-ph/0601007"/>
<dcterms:creator rdf:parseType="Resource">
<foaf:name>arXiv.org e-Print Repository</foaf:name>
<foaf:page rdf:resource="http://arXiv.org" />
</dcterms:creator>
<dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2008-10-01T18:30:02Z</dcterms:created>
<dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2008-10-03T07:30:34Z</dcterms:modified>
<dc:rights>This Resource Map is available under the Creative Commons Attribution-Noncommercial 2.5 Generic license</dc:rights>
<dcterms:rights rdf:resource="http://creativecommons.org/licenses/by-nc/2.5/"/>
</rdf:Description>

Description of A[edit]

arXiv example:
 <rdf:Description rdf:about="http://arxiv.org/aggregation/astro-ph/0601007"> 
<ore:isDescribedBy rdf:resource="http://arxiv.org/rem/atom/astro-ph/0601007"/>
<ore:isDescribedBy rdf:resource="http://arxiv.org/rem/xhtml/astro-ph/0601007" />
<dc:title>Parametrization of K-essence and Its Kinetic Term</dc:title>
<dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2005-12-31T04:01:23Z</dcterms:created>
<dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2006-01-18T06:16:15Z</dcterms:modified>
<dcterms:creator rdf:parseType="Resource">
<foaf:name>Hui Li</foaf:name>
<foaf:mbox rdf:resource="mailto:lihui@somewhere.cn" />
</dcterms:creator>
<dcterms:creator rdf:parseType="Resource">
<foaf:name>Zong-Kuan Guo</foaf:name>
</dcterms:creator>
<dcterms:creator rdf:parseType="Resource">
<foaf:name>Yuan-Zhong Zhang</foaf:name>
</dcterms:creator>
<ore:aggregates rdf:resource="http://arxiv.org/abs/astro-ph/0601007"/>
<ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
<ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
<ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007?dpi=600&font=bitmapped"/>
<ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007?dpi=300&font=bitmapped"/>
<ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007?fname=cm&font=TypeI"/>
<ore:aggregates rdf:resource="http://arxiv.org/dvi/astro-ph/0601007"/>
<ore:aggregates rdf:resource="http://export.arxiv.org/oai2?verb=GetRecord&metadataPrefix=oai_dc&identifier=astro-ph/0601007"/>
<ore:aggregates rdf:resource="http://arxiv.org/cits/astro-ph/0601007"/>
<ore:aggregates rdf:resource="http://www.citebase.org/abstract?id=oai:arXiv.org:astro-ph/0601007"/>
<rdfs:seeAlso rdf:resource="http://arxiv.org/abs/astro-ph/0601007"/>
<rdfs:seeAlso rdf:resource="http://jp.arxiv.org/aggregation/astro-ph/0601007"/>
<ore:similarTo rdf:resource="info:arxiv/astro-ph/0601007"/>
<ore:similarTo rdf:resource="info:doi/10.1142/S0217732306019475"/>
</rdf:Description>