Skip to end of metadata
Go to start of metadata

ORE application profile

Decisions for the Dutch repositories following the Dutch Tender project 2009 in which experiments were done with Enhanced Publications.

Content

1. #Use of ORE
2. #Linear Publications
3. #Enhancements
4. #Persistent Identifiers
5. #Author Identifiers
6. Jump-off Pages
7. #Descriptive Metadata
8. #Context
9. #ORE Proxies
10. #Minimal Metadata
11. #Use of ontologies
12. #Serialisation format
13. #Quality indication

SURFShare Tender 2009

1. Use of ORE

Statement:

The use of ORE is limited to describing relations between linear publications and enhancements

Rational:

The primary goal of ORE is to enhance the traditional (linear) publication, generally in PDF, with extra material.

Implications:

 

2. Linear Publications

Statement:

In the context of ORE, linear publications are viewed as black boxes 

Rational:

The linear publication is generally created in a regular editor and saved in a format which, with new XML-based formats, is exceptionally suitable for preserving  the structure.

Implications:

  • Possible internal structures of linear publication or enrichments must be defined in the appropriate format applicable. The structure of a text document is dissolved e.g. in ODF, OOXML, or TEI.
  • A chapter from a thesis may be taken as a linear publication

3. Enhancements

Statement:

Enhancements are addititions that add value to the linear publication and have a semantic type. 

Rational:

-

Implications:

An enhancement must have a semantic type.
Examples of enhancements are: datasets, images, workflows, references to other (enhanced publications)

4. Persistent Identifiers

Statement: 

The relation between objects and URN:NBN Persistent Identifiers is indicated with the predicate ore:similarTo

Rational:

The persistent identifier only identifies the content, not an exact copy.

Implications:

<subject> ore:similarTo <urn:nbn:ui:...>

5. Author Identifiers

Statement:

The relation between the person and the DAI is indicated with the predicate owl:sameAs

Rational:

The author identifier always identifies the same concept of a person.

Implications:

Author Identifiers are included as:
<subject> owl:sameAs <info:eu-repo/dai/...>

6. Jump-off Pages

Statement:

Jump-off pages that are related to an enhanced publication are  included with the predicate hasHumanStartpage regarding the subject and as an aggregated resource with semantic type info:eu-repo/semantics/humanStartpage.

Rational:

Jump-off pages belong with the enhanced publication as aggregated resource. It is however not unthinkable that Jump-off pages are aggregated which are not directly related to the enhanced publication.
With the hasHumanStartpage predicate agents and services can unambiguously identify the Jump-off page of the enhanced publication.

Implications:

Jump-Off Pages are included as:
<URI-A> ore:aggregates <URI-J>
<URI-A> hasHumanStartpage <URI-J>

7. Descriptive Metadata

Statement:

Descriptive metadata (e.g. a MODS-record) is included as object with the predicate hasDescriptiveMetadata of the subject and as aggregated resource with semantic type info:eu-repo/semantics/descripteMetadata

Rational:

It is possible to aggregate multiple metadata

Implications:

Descriptive metadata is included as:
<URI-A> ore:aggregates <URI-D>
<subject> hasDescriptiveMetadata <URI-D>

8. Context

Statement: 

All claims that are made within an aggregation are only valid within that aggregation.

Rational:

Organisation and infrastructure are not ready to guarantee Proof and Trust. No services have been defined with which agent scan check the reputation of other agents, for checking the validity of their statements and thus building trust. This is essential for an infrastructure in which the integrity of data needs to be warranted.

Implications:

RDF triples have to be considered as quads in "named graphs".

9. ORE Proxies

Statement:

Proxies are not used

Rational:

Because of point 8 the necessity of this functionality fell away. In order to reduce complexity this functionality will not be supported in the current infrastructure.

Implications:

Proxies are not supported in the infrastructure.

10. Minimal Metadata

Statement:

In the Resource Map, use the minimal set of metadata as defined by Verhaar. If no minimal set has been described for the semantic type, the set to use is free.

Rational:

In order to establish a workable service for Enhanced Publications and to guarantee interoperability a minimal set of metadata is required.

Implications:

A minimal set of metadata is required for semantic types for which such a set has been defined.

11. Use of ontologies

Statement:

Use only within SURFShare registered ontologies. If an ontology is missing this can be applied.

Rational:

Many ontologies contain inconsistencies, conflicts and other ontologies. When they are used without being checked on this, the integrity of the service might be harmed.

Implications:

Ontologies not registered are not supported.

12. Serialisation format

Statement:

RDF/XML serialisation of ORE is used

Rational:

RDF/XML is considered the most sustainable serialisation format pertaining to Atom, as in the last next to Atom XML also RDF/XML are used in order to express statements that are not available within the Atom semantics.

Implications:

Only RDF/XML is supported

13. Quality indication

Statement:

Aggregations that are made conform the SURFshare agreements are indicated with <aggregation> dcterms:conformsTo <info:eu-repo/applicationProfile/tender2009>

Rational:

The developers community need a quality indication of descriptions in order toe define services.

Implications:

Aggregations that conform to the points made in this document indicate this as follows:
<URI-A> dc:conformsTo <info:eu-repo/applicationProfile/tender2009>

  • No labels