• Created by Unknown User (lisanne), last modified by user-5e3f1 on Wed 25 Apr 2018

Table of contents

Document information

Title:
Subject:
Moderator:
Version:
Date published:
Excerpt: Write an excerpt here

(Optional information)
Type:
Format:
Identifier:
Language:
Rights:
Tags:

Document History

Date

Version

Owner

Changelog

PDF

 

 

 

 

 

Abstract

The abstract describes what the application profile is about. It should contain a problem definition, the standards described by the application profile and the goal of the application profile.

Introduction

The namespace info:eu-repo is registered at http://info-uri.info
This name space is an authoritive placeholder for semantic terms, controlled vocabularies and identifiers.
By using this namespace all the terms used have a "web presence". Therefore it is no longer an arbitrary string, but contains meaning. This utilisation makes it future-proof.

The INFO URI namespace has been DISCONTINUED since 22 May 2010!! The website info-uri.info writes: "it has been deemed appropriate to close the registry to further "info" namespace registrations. The "info" registry will continue to be supported for the foreseeable future, although prudent adopters should consider migrating their resource identity requirements towards mainstream Web practices over the long term." 

The already existing info:eu-repo namespace will NOT be DISCONTINUED. But will migrate toward mainstream Web practices applicable for Linked Data. Steps involve in prefixing the name space by the purl.org URL. Second to create OWL descriptions for each element in the namespace, making it possible for machines to understand the identified content.

The OWL of the info:eu-repo namespace could easily be maintained using this tool http://knoodl.com/ui/index/vocab/groups/infoeurepo . The http://purl.org/info:eu-repo/semantics/ could then be redirected to for example http://knoodl.com/ui/groups/infoeurepo/vocab/pubtypes/rdf/ 

The info:eu-repo URIs are persistent identifiers for non-informational resources. Such non-informational resources include classifications and "real world objects". One important category is concepts; concepts are classes or properties. For these a subclass of the info:eu-repo URIs is introduced: the info:eu-repo/semantics URIs. The info URIs are not resolvable which makes them ideal as persistent identifiers of abstract things like concepts. On the other hand there is a need to link the URIs to their semantics. In the Semantic Web this is done by a redirection to a RDF document in which the semantic relations of the object for which the URI stands are described. We propose a service that supports URIs of the following form: http://purl.org/info:eu-repo/... (which is the same as http://www.purl.org/info:eu-repo/... - default hostname is "www"). The URI http://purl.org/info:eu-repo/semantics URIs results in a 302 redirection to a RDF document in which the concepts for which the URIs stand are described.The namespace is an authoritive placeholder for semantic terms, controlled vocabularies and identifiers. By using this namespace all the terms used have a "web presence". Therefore it is no longer an arbitrary string, but contains meaning. This utilisation makes it future-proof.The purpose of the info:eu-repo registry is not to create a comprehensive, complete ontology. Instead its purpose is to fill holes. The registry introduces terms with which existing ontologies can be complemented and connected with each other.

The following types have been identified for controlled vocabularies and identifiers.

Practice

The http://purl.org/info:eu-repo/semantics URIs will be linked to URIs that stand for concepts from other vocabularies. E.g., several of the terms from Eprints Type Vocabulary Encoding Scheme (http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Type_Vocabulary_Encoding_Scheme) are owl:sameAs terms from info:eu-repo/semantics:
<info:eu-repo/semantics/article> <owl:sameAs> <http://purl.org/eprint/type/JournalArticle>
In the case a concept is already defined in another vocabulary, the concept gets a eu-repo/semantics URI if
•    the semantics of the concept is not described by that vocabulary
•    the concept is relevant for repositories
A review board is needed for checking of these criteria. The maintainer of the registry should see to it that a requested term is checked through http://sameas.org. All owl:sameAs relations can be accessed via this service. On short term SURFShare is able to do this. On the long term KNAW might be able to do it.

Projects used for input

DRIVERGuidlines (DRIVER)
Project SamenInDelen (SamenInDelen)
NEEO Technical guidelines (NEEO)
Use of MODS for institutional repositories (SURFshare)
OpenAIRE Guidelines v2(OpenAIRE)

User community

It is important to know who is using this namespace. When changes and modifications happen, we need to be able to contact these people, so they can tell others about changes. This makes the propagation of change possible.

name

organisation

country

representing a larger community or project

role

Maurice Vanderfeesten

SURF

NL

SURF - Dutch academic information infrastructure

Initiator and keeper of the info:eu-repo namespace account

Rik van Sommeren

SURF

NL

EduStandard

staff member of bureau EduStandard

Peter van Wonderen

VU

NL

SURF - Dutch repository administrators community

keeper of the purl.org/info:eu-repo sub-namespace account (redirecting url's)
chair of the Dutch repository administrators community

Benoit Pauwels

ULB

BE

NEEO

information specialist

Jochen Schirrwagen

UniBi

DE

DRIVER and OpenAIRE

information specialist

Maren Brodersen

D-NB

DE

n.a.

n.a.

Frank Waajen

WUR

NL

HBO-Kennisbank

information specialist in the HBO metadata working group

Vacancies: currently this wiki page with attachments needs a moderator. Volunteers are welcome. Send a mail to vanderfeesten@surf.nl or sommeren@surf.nl

Digital Author Identifier

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

dai

/

(country/identifier)

 

where "country" is an ISO639-1 country label. and where "identifier" is the Identification number for the author in that country. It is preferred to use the ISNI (International Standard for Name Identifier) syntax  

 

SURFshare, DRIVER, NEEO

Classification Schemes

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

classification

/

ddc

 

Dewey Decimal Classification (DDC)
http://www.oclc.org/dewey/

 

 

info:eu-repo

/

classification

/

udc

 

Universal Decimal Classification
http://www.udcc.org/http://www.udcc.org/

 

 

info:eu-repo

/

classification

/

lcc

 

Library of Congress Classification
http://www.loc.gov/catdir/cpso/lcco/http://www.loc.gov/catdir/cpso/lcco/

 

 

info:eu-repo

/

classification

/

lcsh

 

Library of Congress Subject Headings (LCSH)

 

 

info:eu-repo

/

classification

/

swd

 

Schlagwortnormdatei (SWD)

 

 

info:eu-repo

/

classification

/

bicssc

 

Book Industry Communication - Standard Subject Categories
http://www.bic.org.uk/7/BIC-Standard-Subject-Categories/

 

Open Access Publishing in European Networks (OAPEN)
http://www.oapen.org/

info:eu-repo

/

classification

/

nbc

 

Nederlandse Basisclassificatie (Dutch Basic Classification)
http://www.kb.nl/vak/basis/bc04.pdf

 

HBO-Kennisbank
http://www.hbo-kennisbank.nl

info:eu-repo

/

classification

/

jel

 

Journal of Economic Literature (JEL) Classification System
Articles in economics journals are usually classified according to the JEL classification codes. JEL code (sub)categories, including periodic updates, are referenced at Journal of Economic Literature (JEL) Classification System, published quarterly by the American Economic Association (AEA)
http://www.aeaweb.org/journal/jel_class_system.php

 

Network of European Economists Online (NEEO)
http://www.nereus4economics.info/network.html

XML Schema's and ontologies

The publicationTypes Schema can be referenced via a purl.org link, see below for available schema's.

publicationTypes schema (XSD)

http://purl.org/info:eu-repo/schemas/xmls/2010/04/15/publicationTypes.xsd

versionTypes schema (XSD)

http://purl.org/info:eu-repo/schemas/xmls/2010/05/07/versionTypes.xsd

info:eu-repo ontology (OWL/RDF)
(currently only publicationTypes are supported)

http://purl.org/info:eu-repo/

Publication types

?

The XML schema can be found here using this link: http://purl.org/info:eu-repo/schemas/xmls/2010/04/15/publicationTypes.xsd
Publication type ontology: http://purl.org/info:eu-repo/
Usage for actionable reference to machine readable content: add http://purl.org/ as a prefix to the authoritative term e.g. http://purl.org/info:eu-repo/semantics/annotation

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

semantics

/

article

 

article or an editorial published in a journal. (ed. Should this be specified specifically as an Scholarly article? Or does this list of publication types define a scholarly context by default?)

 

DRIVER
SURF
NEEO

info:eu-repo

/

semantics

/

bachelorThesis

 

lowest level of a thesis (normally after three years of study). See also http://en.wikipedia.org/wiki/Diplom

 

DRIVER
SURF

info:eu-repo

/

semantics

/

masterThesis

 

intermediate level of a thesis (normally after four or five years of study). See also http://en.wikipedia.org/wiki/DiplomThis also refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree

 

DRIVER
SURF

info:eu-repo

/

semantics

/

doctoralThesis

 

highest level of a thesis normally after more than four or five years of study. See also http://en.wikipedia.org/wiki/DiplomAlso everything equal and higher then a Doctoral thesis, that does not follow the "Bologna Convention", will be put in the category doctoralThesis. A free text field will Provide the opportunity to specify this further

 

DRIVER
SURF

info:eu-repo

/

semantics

/

book

 

book or monograph

 

DRIVER
SURF

info:eu-repo

/

semantics

/

bookPart

 

part or chapter of a book

 

DRIVER
SURF

info:eu-repo

/

semantics

/

review

 

review of a book or article

 

DRIVER

info:eu-repo

/

semantics

/

conferenceObject

 

all kind of documents related to a conference, p.e. conference papers, conference reports, conference lecture, papers published in conference proceedings, conference contributions, reports of abstracts of conference papers and conference posters

 

DRIVER

info:eu-repo

/

semantics

/

lecture

 

lecture or presentation presented during an academic event, e.g., inaugural lecture. Excluded is a conference lecture (see conferenceItem)

 

DRIVER
SURF

info:eu-repo

/

semantics

/

workingPaper

 

a preliminary scientific or technical paper that is published in a series of the institution where the research is done. Also known as research paper, research memorandum or discussion paper. The difference with a preprint is that a workingPaper is published in a institutional series. Examples are: working papers, research papers, research memoranda and discussion papers

 

DRIVER
SURF

info:eu-repo

/

semantics

/

preprint

 

like a workingPaper this is a preliminary scientific or technical paper, but it is not published in a institutional series. The paper is intended to be published in a scientific journal or as a chapter in a book

 

DRIVER
SURF

info:eu-repo

/

semantics

/

report

 

this is a more or less a rest category and covers commission reports, memoranda, external research reports, internal reports, statistical report, reports to funding agency, technical documentation, project deliverables etc. Excluded are conference reports (See conferenceItem)

 

DRIVER
SURF

info:eu-repo

/

semantics

/

annotation

 

note to a legal judgmen

 

DRIVER
SURF

info:eu-repo

/

semantics

/

contributionToPeriodical

 

contribution to a newspaper, weekly magazine or another non-academic periodical

 

DRIVER
SURF

info:eu-repo

/

semantics

/

patent

 

patent

 

DRIVER
SURF

info:eu-repo

/

semantics

/

other

 

especially meant for non-publication data like research data, audio-visual materials, animations etc.

 

DRIVER

info:eu-repo

/

semantics

/

conferenceObject

 

All kinds of documents related to a conference, e.g., conference papers, conference reports, conference lecture, papers published in conference proceedings, conference proceedings, conference contributions, reports of abstracts of conference papers and conference posters

 

DRIVER

info:eu-repo

/

semantics

/

reportPart

 

part of a report

 

SURF

info:eu-repo

/

semantics

/

bookReview

 

book review

 

SURF

info:eu-repo

/

semantics

/

conferencePaper

 

paper published in conference proceedings

 

SURF

info:eu-repo

/

semantics

/

researchProposal

 

documentation for grant request

 

SURF

info:eu-repo

/

semantics

/

studentThesis

 

this refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree

 

SURF

info:eu-repo

/

semantics

/

technicalDocumentation

 

technical documentation

 

SURF

info:eu-repo

/

semantics

/

conferencePaper

 

paper published in conference proceedings

 

NEEO

info:eu-repo

/

semantics

/

conferencePoster

 

poster presented at a conference

 

NEEO

info:eu-repo

/

semantics

/

conferenceProceedings

 

the conference proceedings

 

NEEO

info:eu-repo

/

semantics

/

conferenceContribution

 

contribution to a conference but not published in a conference

 

NEEO

info:eu-repo

/

semantics

/

conferencePaper

 

paper published in conference proceedings

 

DARE

info:eu-repo

/

semantics

/

ConferenceItem

 

contribution to a conference but not published in a conference

 

UKOLN

info:eu-repo

/

semantics

/

ConferencePaper

 

contribution to a conference but not published in a conference

 

UKOLN

info:eu-repo

/

semantics

/

ConferencePoster

 

contribution to a conference but not published in a conference

 

UKOLN

conferenceObject of Driver includes all other conference-related publications. This can be used if none of the more specific publicationtypes comply.
Within conferenceObject are two types: conferenceProceedings as proposed by NEOO and ConferenceItem from the vocabulary of UKOLN. The type conferenceProceedings is used for authors who want to include the conference proceedings of which they are the editor. It is helpful if conference proceedings are contained in the repositories as compound objects. ConferenceItem is not really necessary, because there are more specific types who cover all sorts of ConferenceItems: ConferencePaper and conferenceContribution. The distinction between these two subtypes is the whether or not it's included in conference proceedings.
conferenceContribution has a subtype: conferencePoster. Not published readings for a conference are a conferenceObject, a ConferenceItem and a ConferenceContribution.
The class-subclass relations can be represented with the following hierarchy.

 conferenceObject
    conferenceProceedings
    ConferenceItem
        conferencePaper = ConferenceItem in conferenceProceedings
        conferenceContribution = ConferenceItem not in conferenceProceedings
            conferencePoster

The term conferenceContribution is confusing. A more clear term is concerenteItemNotInProceedings. The proposal is to adopt conferenceObject, conferenceProceedings, conferencePaper, conferenceItemNotInProceedings, conferenceContribution (owl:sameAs conferenceNotInProceedings; the latter is the preferred term) and conferencePoster in the info:eu-repo/semantics namespace. If we specify in a more formal way the semantic relations, we can use ConferenceItem from the UKOLN vocabulary.

The new situation can be visualised as follows:

The proposal is to use conferenceProceedings, conferencePaper and conferencePoster within SURFshare. conferenceItemNotInProceedings can be used as rest category

Mappings with SWAP

Use for publication types identifiers from the info:eu-repo/semantics/ namespace, see the first column of the following table. E.g., the URI for articles is info:eurepo/semantics/article. The second column contains the vocabulary of the Eprints Application Profile (also known as Scholarly Works Application Profile - SWAP) (http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Type_Vocabulary_Encoding_Scheme). This vocabulary is included only for comparison reasons.

info:eu-repo/semantics/

http://purl.org/eprint/type/

Description

 

 

 

annotation

 

note to a legal judgment

article

JournalArticle

article in a journal

bachelorThesis

Thesis (broader)

bachelor thesis

book

Book

book or monograph.

bookPart

BookItem

part or chapter of a book

bookReview

BookReview

book review

conferencePaper

ConferencePaper

paper published in conference proceedings

contributionToPeriodical

 

contribution to a newspaper, weekly magazine or another non-academic periodical

doctoralThesis

Thesis (broader)

PhD dissertation

researchProposal

 

documentation for grant request

lecture

 

Published lecture presented during an academic event, e.g., inaugural lecture

masterThesis

Thesis (broader)

 

patent

Patent

patent

preprint

Report (broader)

like a research paper this is a preliminary scientific or technical paper, but it is not published in a institutional series. The paper is intended to be published in a scientific journal or as a chapter in a book.

report

Report (broader)

this is a more or less a rest category and covers commission reports, memoranda, conference reports, external research reports, internal reports, statistical report, reports to funding agency, etc.

studentThesis

Thesis (broader)

this refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree

technicalDocumentation

 

technical documentation

workingPaper

WorkingPaper

a preliminary scientific or technical paper that is published in a series of the institution where the research is done. Also known as research paper, research memorandum or discussion paper. The difference with a preprint is that a workingPaper is published in a institutional series.

 

ScholarlyText

all the other types are a sub-classe of this type

 

ConferenceItem

covers conference papers and conference posters

 

ConferencePoster

poster presented at a conference

 

JournalItem

a contribution to a journal; includes articles, editorials, conference reports, etc.

 

NewsItem

news item

 

SubmittedJournalArticle

the author's original manuscript submitted to and/or accepted by a journal. When not accepted it is a info:eu-repo/semantics/preprint or a info:eu-repo/semantics/workingPaper and when accepted it is a info:eu-repo/semantics/article

Mappings with Metis

There is a need to conduct a general agreement on the mapping result of species as proposed by the Metis Metis Group Results on the types of information: eu-repo/semantics. A first attempt is the following table.

resulttype nog vertalen?

CODE_OUTPUT

Resulttype

publicationType (info:eu-repo/semantics/)

10

annotatie

annotation

11

artikel in bundel - proceedings

conferencePaper

01

artikel in tijdschrift

article

02

boek / monografie

book

05

boekbespreking

bookReview

03

boekdeel - hoofdstuk

bookPart

04

boekredactie

 

20

dissertatie

doctoralThesis

70

erkenning

 

08

extern rapport

report

12

inaugurele rede

lecture

13

krantenartikel

contributionToPeriodical

30

octrooi

patent

50

overige resultaten

 

60

relevante functies

 

06

tijdschriftredactie - refereeschap

 

40

voordracht - lezing (ongepubl)

 

 

 

bachelorThesis

 

 

researchProposal

 

 

masterThesis

 

 

preprint

 

 

studenThesis

 

 

technicalDocumentation

 

 

workingPaper

 

 

conferencePoster

Access Rights

SAME AS the e-prints accessRights property in the Scholarly Works Application Profile

see: http://purl.org/eprint/accessRights/

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

semantics

/

closedAccess

 

This type of access is the opposite of Open Access. Also referred to as "toll gated access". The main incentive her to gain access is by financial means.

 

NEEO, SURFshare

info:eu-repo

/

semantics

/

embargoedAccess

 

This type of access means the resource is Closed Access, until released for Open Access on a certain date. (this date can be specified elsewhere in the metadata) The incentives to embargo a resource has often to do with the fairness towards publisher to provide them an advantage as the exclusive first deliverers of knowledge. Also embargoes are used in sections of a Ph.D. thesis that are concerned with classified corporate information.

 

OpenAIRE

info:eu-repo

/

semantics

/

restrictedAccess

 

Open Access, but with restrictions. Often the Author wants to control the people who have access to for example a dataset. Access is provided in exchange for an e-mail address, to keep in touch with other people who are interested.

 

NEEO, SURFshare

info:eu-repo

/

semantics

/

openAccess

 

Open Access, this refers to access without restrictions, and without financial incentives. Access to the resource is gained directly, without any obstacles.

 

NEEO, SURFshare

Date Types and value

this is a suggestion

Namespace

 

Type

 

Term

 

Value (examples)

 

Description

 

Used by project

info:eu-repo

/

date

/

embargoEnd

/

2008-04-12

 

This Embargo End date tells the user on which date the embargo on the publication is released. Commonly the Access rights changes from the value closedAcceess to openAccess. A harvester is notified and can update this metadata when the  modified date of the OAI-PMH record is updated aswell.

 

OpenAIRE

info:eu-repo

/

date

/

publication

/

2006-11-05

 

The official date of publication

 

 

info:eu-repo

/

date

/

accepted

/

2004-02-06

 

Date of acceptance of the resource. - DC qualifier: http://dublincore.org/documents/dcmi-terms/#terms-date

 

DCMI

info:eu-repo

/

date

/

copyrighted

/

2005-11-12

 

Date of copyright.- DC qualifier: http://dublincore.org/documents/dcmi-terms/#terms-date

 

DCMI

info:eu-repo

/

date

/

submitted

/

2004-10-05

 

Date of submission of the resource. - DC qualifier: http://dublincore.org/documents/dcmi-terms/#terms-date

 

DCMI

Grant Agreement Identifiers

a vocabulary must be made for Funders and programs

for the time being EC-FP7 project information is exposed via OpenAIRE-OAI

Non verbose

Namespace

 

Type

 

Funder (example)

 

Program (example)

 

Identifier (examples)

 

Description

 

Used by project

info:eu-repo

/

grantAgreement

/

EC

/

FP7

/

12345

 

 

 

OpenAIRE

Verbose

Namespace

 

Type

 

Funder (example)

 

Program (example)

 

Identifier (examples)

 

Jurisdiction

 

ProjectName

 

ProjectAcronym

 

Description

 

Used by project

info:eu-repo

/

grantAgreement

/

EC

/

FP7

/

12345

/

EU

/

name

/

acronym

 

 

 

OpenAIRE

Alternative Identifier

Namespace

 

Type

 

Term

 

Scheme (example)

 

Identifier (example)

 

Description

 

Used by project

info:eu-repo

/

semantics

/

altIdentifier

/

doi

/

10.1234-789.1

 

alternative and persistent identifier of a resource

 

OpenAIREplus

Supported Schemes

Scheme

Description

ark

Archival Resource Key

arxiv

arXiv.org identifier

doi

Digital Object Identifier

hdl

Handle Identifier

isbn

International Standard Book Number

issn

International Standard Serial Number

pmid

PubMed ID

purl

Persistent Uniform Resource Locator

urn

Uniform Resource Name

wos

Web of Science accession number

Reference Identifier

Namespace

 

Type

 

Term

 

Scheme (example)

 

Identifier (example)

 

Description

 

Used by project

info:eu-repo

/

semantics

/

reference

/

urn

/

urn:nbn:de:123-4567890

 

reference identifier of a publication mentioned in a given publication resource

 

OpenAIREplus

Supported Schemes

Scheme

Description

ark

Archival Resource Key

arxiv

arXiv.org identifier

doi

Digital Object Identifier

hdl

Handle Identifier

isbn

International Standard Book Number

issn

International Standard Serial Number

pmid

PubMed ID

purl

Persistent Uniform Resource Locator

url

Uniform Resource Locator

urn

Uniform Resource Name

wos

Web of Science accession number

Dataset Identifier

Namespace

 

Type

 

Term

 

Scheme (example)

 

Identifier (example)

 

Description

 

Used by project

info:eu-repo

/

semantics

/

dataset

/

doi

/

10.1234-567

 

reference identifier of a dataset related or described in a given publication resource

 

OpenAIREplus

Supported Schemes

Scheme

Description

ark

Archival Resource Key

doi

Digital Object Identifier

hdl

Handle Identifier

purl

Persistent Uniform Resource Locator

url

Uniform Resource Locator

urn

Uniform Resource Name

Versions

The XML schema can be found here using this link: http://purl.org/info:eu-repo/schemas/xmls/2010/05/07/versionTypes.xsd | NOTE: only the types are included used by the DRIVER project 

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

semantics

/

publishedVersion

 

 

 

NEEO

info:eu-repo

/

semantics

/

authorVersion

 

 

 

NEEO

info:eu-repo

/

semantics

/

draft

 

Early version circulated as work in progress

 

DRIVER

info:eu-repo

/

semantics

/

submittedVersion

 

The version that has been submitted to a journal for peer review

 

DRIVER

info:eu-repo

/

semantics

/

acceptedVersion

 

The author-created version that incorporates referee comments and is the accepted for publication version

 

DRIVER

info:eu-repo

/

semantics

/

publishedVersion

 

The publisher created published version

 

DRIVER

info:eu-repo

/

semantics

/

updatedVersion

 

A version updated since publication

 

DRIVER

Object types

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

semantics

/

objectFile

 

 

 

SURFshare, DRIVER, NEEO

info:eu-repo

/

semantics

/

humanStartPage

 

 

 

SURFshare, DRIVER, NEEO

info:eu-repo

/

semantics

/

descriptiveMetadata

 

 

 

SURFshare, DRIVER, NEEO

info:eu-repo

/

semantics

/

publication

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

dataset

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

enhancedObjectFile

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

DDIInstance

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

SPSSdatafile

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

SPSSsetupfile

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

other

 

 

 

SamenInDelen

info:eu-repo

/

semantics

/

datafile

 

 

 

SamenInDelen

Namespace

 

Type

 

Term

 

Description

 

Used by project

info:eu-repo

/

semantics

/

closedAccess

 

 

 

NEEO, SURFshare

Date of submission of the resource.

8 Comments

  1. Unknown User (ham@surf.nl)

    Volgens mij is de term SSPSsetupfile niet correct ik vermoed dat dit SPSSsetupfile moet zijn

    1. Unknown User (magchiel)

      Gewijzigd.

  2. Unknown User (maurice)

    in dit project http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData/worden andere ontologieën gebruikt.

    Als we bovenstaande ontologie af hebben, kunnen we deze koppelen aan de Bibontology die daar ook staat genoemd:

    http://umbel.org/images/lod_constellation.html(overzicht in de umbel context)

    de bibliontology.comwebsite

    "The Bibliographic Ontology describe bibliographic things on the semantic Web in RDF.  This ontology can be used as a citation ontology, as a document classification ontology, or simply as a way to describe any kind of document in RDF. It has been inspired by many existing document description metadata formats, and can be used as a common ground for converting other bibliographic data sources."

    Hier staat de RDF code: http://code.google.com/p/bibotools/source/browse/bibo-ontology/trunk/bibo.n3

    en hier de uitleg per item http://bibotools.googlecode.com/svn/bibo-ontology/trunk/doc/index.html

  3. Unknown User (maurice)

    http://bibliontology.com/

    has the folowing classes. (entities and properties such as identifiers are not shown in this map)

  4. Anonymous

    Zou dit ook niet goed bruikbaar zijn voor andere financiers? Ik zit zelf te denken aan NWO.

    Peter van der Togt
    Wageningen UR

  5. Unknown User (maurice)

    Maurice,

    I added it as a issue on the PURLZ project page:

    http://code.google.com/p/persistenturls/issues/detail?id=31

    I don’t think there is anyone doing active development, though, so it probably won’t get addressed within a useful timeframe.

    OTOH, I would argue that the whole idea of “info:” as a URI scheme was a bad idea anyway, so omitting this phrase from the PURL seems reasonable to me. Since the set of ‘info’ URI namespaces is finite and now frozen, I took the liberty of reserving PURL domain names for each like so:

    http://purl.org/ark

    http://purl.org/arxiv

    http://purl.org/bibcode

    etc.

    A couple of info namespaces were already allocated as PURL domains, so there’s not much I can do about those.

    In the case of http://purl.org/eu-repo, I gave you ownership of the domain so you could use it to automate your info:eu-repo/* resources if you want. I would suggest creating a PURL partial redirect from http://purl.org/eu-repo/ to a Linked Data base URI on your server and then adding an assertion like so to reconcile the PURL and ‘info’ URIs:

    <http://purl.org/eu-repo/dai/nl/12345>

    owl:sameAs <info:eu-repo/dai/nl/12345> .

    See http://purl.org/docs/help.html#purladvcreate for detail on how to create a PURL partial redirect.

    Hope this helps.

    Jeff

    1. Unknown User (maurice)

      I am not sure to abandon the "info:" prefix

  6. Unknown User (maurice)

    From e-mail conversation with Jochen Schirrwagen. For the OpenAIRE project there is a need to extend the terms, adding classifications and identifiers.
    This is done in consideration of the remarks below in the e-mail conversation.

    -----Oorspronkelijk bericht-----
Van: Jochen Schirrwagen [mailto:jochen.schirrwagen@uni-bielefeld.de]
Verzonden: vrijdag 8 maart 2013 14:49
Aan: Vanderfeesten, Maurice
CC: Eloy Rodrigues; Pedro Príncipe; Mathias Lösch; Friedrich Summann
Onderwerp: Re: info:eu-repo update with terms

Dear Maurice,

thanks a lot for your comments.
On 03/04/2013 11:59 AM, Vanderfeesten, Maurice wrote:
> Hi Jochen,
>
> I have seen your e-mail. I will process this in the following week. Coming day's I have several deadlines.
thank you, no problem.

>
> Note: The first thing that came to my mind when I saw the extensions is that it has a deep hierarchical structure. This could be a drawback when keeping semantic web in mind, keep it flat, make the semantics explicit and use it as pointer.

You are dead right!
But we need the workaround for the time being.
Moving to a more complex metadata format wouldn't help us since formats other than DC are not globally accepted or established.
Keeping DC means, we need to press even complex things in a single field.
Although reasonable we cannot split the components for the project identifier in separate terms. In case of more than one project the order of the given terms cannot be guaranteed.
>
> info:eu-repo/grantAgreement/Funder/[string:URIencoding]
>   info:eu-repo/grantAgreement/FundingProgram/[string:URIencoding]
> info:eu-repo/grantAgreement/ProjectNumber/[string:URIencoding]
> info:eu-repo/grantAgreement/Jurisdiction/[enumeration ISO:xyz]
> info:eu-repo/grantAgreement/ProjectName/[string:URIencoding]
> info:eu-repo/grantAgreement/ProjectAcronym/[string:URIencoding]
>

Of course it will change as soon as we transfer the vocabulary to the semantic web.

> Second; I guess things like [Jurisdiction] need to be enumerated, think about that.
Yes true.
>
> Third; for example [ProjectName]  can have spaces, how to encode this, as an URI?
[ProjectName] and [ProjectAcronym] are optional fields for human readability. They are not targeted for encoding as URIs.

>
> Fourth; do you need to make a list of possible [Funder], [FundingProgram] etc. to prevent variations in the writing.
Yes true, the same as for [Jurisdiction]. OpenAIRE needs to provide such a list.

> [Funder] if you'll leave this free text you'll get variations like EU, European Commission, EC, EU-EC , etc etc. do you want this? Maybe yes...
no, it needs to be a controlled vocabulary
>
> Fifth; maybe you have to use existing vocabularies/ontologies for project and law terms, and write these in the OpenAIRE guidelines. Go for it. Look in http://sindice.com/ this might help a lot.
I'll take a look, but I guess they are not much helpful at the current stage.

>
> Sixth; reuse as much as there already is out there. Think of why should this be part of the vocabulary, why not use a different metadata format like MODS or MARC21 where you can do your complete bibliographic cataloguing of all the different identifiers?


> What enumeration is there for [scheme] and what encoding for
> [identifier]
the [scheme] takes values from a controlled set:
doi - Digital Object Identifier
hdl - Handle
ark - Archival Resource Key
purl - Persistent Uniform Resource Locator issn - International Standard Serial Number isbn - International Standard Book Number wos - Web of Science accession number pmid - PubMed ID arxiv - arXiv.org identifier urn - Uniform Resource Name uri - Uniform Resource Identifier

[identifier] as no specific encoding but depends on the given scheme.
>
> Think about all this first. And I, or you, will come back to this later on this week.

I know the extensions are not optimal, but pragmatic enough to apply them in DC at the moment.

Best regards,
Jochen