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.

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)

Digital Author Identifier

Classification Schemes

XML Schema's and ontologies

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

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

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.

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?

Access Rights

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

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

Date Types and value

this is a suggestion

Grant Agreement Identifiers

a vocabulary must be made for Funders and programs

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

Object types

Date of submission of the resource.