> EprintsApplicationProfile

The following 1063 words could not be found in the dictionary of 550 words (including 550 LocalSpellingWords) and are highlighted below:

01company   15doi   5200590a   A456   about   above   Abstract   abstract   Abu   ac   acceptable   access   Access   according   account   across   adaptation   Adaptation   added   adding   addition   Additional   additional   Adolf   Aeronautics   affiliated   Affiliated   after   agent   Agent   aip   airgap   Ajournal   Akev   algorithmically   all   All   alpha   already   also   alternative   Although   Alu   Alus   amp   Amtx   an   An   analysis   Anchor   and   Andy   Anthropologues   anticipated   any   Aofi   appears   Application   application   Applications   applications   approach   approaches   appropriate   archive   are   arrangements   Article   article   as   As   Asid   aspects   assign   assigned   assigning   assignment   associated   Astronautics   at   atitle   Attempts   aufirst   auinit   aulast   author   Authority   authority   autonomous   Available   available   avoiding   axial   Azetoc   based   bath   be   become   been   before   being   below   best   between   bham   bibliographic   Bibliographic   Bloggs   boaifaq   body   Book   book   both   boundary   brackets   Bristol   bristol   bristoluni   brushless   Budapest   bulk   but   by   C3066   can   candidate   capitalisation   capitalization   capitalize   capture   care   case   cases   cause   cell   Centre   change   changed   chapter   checking   choose   Citation   citation   cite   cites   class   classification   clear   clearly   Closed   coating   collaboration   collection   colon   com   comma   commercial   complete   complies   comprises   Computer   concludes   Conference   conference   configured   conforming   conforms   Congress   considered   consistency   Constraint   constraints   constructed   containing   content   Content   context   Context   contribute   copy   Copy   Copyright   copyright   Core   corporate   correspond   corresponding   corresponds   could   creativecommons   Creator   creator   critical   crossref   Crossref   ctx   current   currently   cvips   damage   dash   data   date   Date   Day   dc   dces   dcterms   de   defence   defined   Definition   degree   deletion   deletions   demonstrator   Department   dereference   des   describe   described   describes   describing   description   Description   descriptions   descriptor   design   detect   detectable   determine   developed   develops   device   diameter   did   different   difficult   digirep   Digital   digital   dimensions   directing   disallowed   discussed   discussion   dispersed   Dispersed   dissertation   do   doc   docs   document   documentation   documents   does   doi   done   double   down   downstream   Dublin   dublincore   duct   dumb   dumbed   dx   dynamics   each   Each   earlham   edition   editor   Editor   editorial   edu   efficiency   either   ejhg   Electric   Electrical   Electronics   Element   elements   elsewhere   elucidating   en   enables   Encode   encode   encoded   encoding   Encoding   engineering   Engineering   entities   Entity   entity   epa   epage   eprint   Eprint   eprints   Eprints   etc   Eu   ever   evidence   exactly   example   Example   Examples   examples   exceptions   exemplar   exist   experimental   experiments   explicitly   Expressed   Expression   expression   expression1   expressions   extreme   fact   faired   fall   familiar   Family   family   familyname   Ffmt   File   filetype   financial   fine   first   fits   fitted   Fitting   Fmimas   fmt   foaf   followed   following   For   for   forenames   form   formally   Format   format   formats   formatted   fos   Foundation   fr   fred   Fred   free   French   frequencies   from   full   functional   funder   Funder   funding   furnished   future   gateways   Gen   general   generated   genome   genomic   genre   genuine   Germany   germline   Get   getpdf   give   given   Given   givenname   giving   gla   gov   grained   grant   Grant   granularity   Group   guidelines   Guidelines   Handbook   handbook   handle   Handle   Harvesting   Has   has   have   hdl   heading   headings   Heery   her   here   hierarchy   highly   his   Historikerstreit   history   History   Hitler   holder   Holder   Hollies   home   homepage   how   however   However   htm   Hum   human   Hydraulic   id   Id   identifier   Identifier   identifiers   identify   identifying   idtype   ie   iesr   ietdl   if   If   implementation   important   imposes   improve   In   in   Inc   include   including   inclusion   index   indicate   indicates   indicating   indication   individual   individuals   industry   Information   Initial   initials   Initiative   insertion   insertions   instability   institution   Institution   integrated   intellectual   intended   internal   into   intro   Introduction   introductory   inverse   ip   irrespective   is   Is   issn   issue   issues   it   It   item   Item   its   itself   Jeffreys   John   Joseph   Journal   journal   journals   jsp   jtitle   jump   kev   keywords   lack   Lai   Lang   language   Language   languages   large   larger   largest   last   least   Leeds   leedsuni   legal   length   level   Library   licence   Licence   license   licenses   likely   limit   lines   link   linking   list   listed   lists   literal   Literal   literature   loc   loci   locus   logical   Loughborough   lower   machine   made   Mailbox   mailbox   mailto   making   mandatory   Manifestation   manifestation   manifestation1   manifestations   Manifested   map   mapping   Mapping   mappings   marcrel   matter   max   mbox   means   Media   media   mediated   Mellon   member   Metadata   metadata   methods   Michael   min   miniature   minimal   mm   Model   model   modified   Modified   moire   molecule   molecules   Monckton   more   most   Motor   motor   Moved   mtx   Multiple   multiple   must   mutant   mypaper   n2   name   Name   namely   names   nationalism   Nature   nature   necessary   need   net   new   New   News   no   Non   nonliteral   normal   not   notation   Note   note   noted   noting   notion   nouns   novo   npg   Nuclear   Number   number   numeric   oai   Object   object   occur   occurrence   Ocean   oceanography   Of   of   off   official   ofi   often   old   omitted   on   one   Online   Only   only   Open   openarchives   openarchivesprotocol   optional   or   order   organisation   organisation1   organisational   organisations   Organization   organization   organization5   organizations   original   other   otherwise   out   own   owner   owning   page   paper   Paper   part   Part   particular   particularly   parts   Patent   pdf   pdfformat1   pdfmanifestation   Peer   peer   people   per   performance   performed   permission   Person   person   person15   person2   personal   Personal   persons   perspectives   peters   physical   placing   poi   points   polar   portion   possible   Poster   Powell   Power   powerpoint   ppt   practical   practice   preclude   preferred   prefix   prepares   preprint   present   presents   Preserve   primarily   Prints   problems   proceeding   Proceedings   processes   produced   production   profile   Profile   prog   project   projects   propeller   proper   properties   property   Property   protect   protective   Protocol   provide   Provide   provided   provides   public   publication   published   Publisher   publisher   publishers   Publishing   Punctuation   punctuation   purl   R000151000005000513000001   R2   Rachel   rachelheery   radial   raises   range   rate   rates   rather   rdn   re   read   readability   readable   Readers   Reading   recast   recombination   Recommendation   recommendation   Recommended   recommended   records   Ref   reference   referenced   references   References   reflect   regarding   registered   related   relates   relatively   relators   relevant   repeat   repeated   repeats   Report   report   reported   repositories   representation   requirements   research   Research   resolve   resource   Resource   respectively   responsible   Restricted   result   resulting   results   retroposition   retrotransposition   Review   reviewed   Reviewed   rfr   rft   Rights   rim   rotor   round   rule   Rural   safer   same   Scheme   scheme   Scholarly   scholarly   scholarwiki   Science   scientific   scitation   sections   security   See   see   select   sensitive   separate   separated   sequencing   served   server   servlet   Servlet   ses   Set   set   sets   Sharkh   short   should   showed   sid   significant   Simple   simple   simpledc   since   single   slides   small   smaller   smallest   software   somatic   some   something   Sons   soton   sotonuni   Southampton   space   spaces   spage   Spanish   specific   specification   spelled   spelling   sperm   Springer   staff   standalone   standard   statement   Statement   statements   static   stator   Status   status   stitle   stop   stops   string   String   strings   Structurally   structure   study   style   subfields   Subject   subject   subjects   Submitted   subscriptions   Subtitles   such   Such   suggested   Suleiman   Sulston   summary   supervision   Supervisor   supervisor   support   surname   surrounds   syntax   Syntax   systems   tag   taken   technically   Technology   term   terms   tested   Text   text   textual   than   that   The   the   theiet   their   them   then   theoretical   There   there   therefore   Therefore   these   thesis   Thesis   they   thick   thickness   thin   thing   this   This   those   though   thruster   thrusters   Time   time   Title   title   to   To   too   topic   transform   Translated   translated   translation   Translation   turn   Turnock   two   type   Type   typed   types   Types   typical   typically   Typically   typing   uk   ukoln   unambiguous   unclear   under   underwater   unequal   unique   uniquely   University   Unless   up   upper   usage   use   Use   used   uses   Using   using   usual   v9   val   Validation   Value   value   vehicles   ver   Version   version   very   Vocabulary   vocabulary   volume   W3   Walker   War   was   way   we   Web   well   West   when   Where   where   whether   which   While   who   whose   Wiley   will   with   within   word   wording   words   work   Work   working   Working   Workplace   workplace   Works   works   World   worth   would   wrapped   written   xmlns   xsl   yes   yet   York   Z39  

Clear message

2009-01-20. Moved: see http://dublincore.org/scholarwiki/SWAPDSP

Introduction

This document describes a DC Application Profile for describing an eprint, or scholarly work. The application profile is based on the SWAP [WWW]Model, which is in turn based on FRBR. The model comprises 5 entities - ScholarlyWork, Expression, Manifestation, Copy and Agent. This application profile provides a way of describing these entities as part of a description set (a set of related DC descriptions).

The notion of a description set is part of the DCMI Abstract Model. Readers that are not familiar with the DCMI Abstract Model should read [WWW]A note about the DCMI Abstract Model before proceeding.

All the examples in this document are formatted according to the DC-Text notation. Readers who are not familiar with DC-Text should read [WWW]A note about DC-Text before proceeding.

In the context of this work an eprint is defined to be a scientific or scholarly research text (as defined by the [WWW]Budapest Open Access Initiative), for example a peer-reviewed journal article, a preprint, a working paper, a thesis, a book chapter, a report, etc.

Scholarly Works Application Profile

Each description set that complies with the Scholarly Works Application Profile is made up of a set of related descriptions about the entities listed above. Therefore, a typical description set (using the DC-Text notation) has the following structure:

Each description set describes only one eprint (i.e. one ScholarlyWork entity). However, multiple descriptions may be used to describe multiple Expression, Manifestation and Agent entities as necessary.

The metadata terms that may be used to describe each entity are described below. Note that all properties may be repeated if necessary. Unless otherwise noted, multiple value strings should be provided using separate statements. Where appropriate, each value string may have an associated language tag.

A minimal description set that conforms to this application profile must include either:

All other aspects of the application profile are optional. #!DSP

Description of the eprint as a ScholarlyWork

Entity type

Property http://purl.org/dc/elements/1.1/type
Min occurrence 1
Max occurrence 1
Literal? No
Definition The type nature or genre of the content of the resource.
Eprint-specific recommendation Each of the entity descriptions in the description sets conforming with this application profile will need to be explicitly typed. This is done using a dc:type statement with one of the following value URIs taken from the [WWW]Eprints EntityType Vocabulary Encoding Scheme corresponding to the entity being described.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Choose from: http://purl.org/eprint/entityType/ScholarlyWork/
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/entityType/
Value String Constraint:
Max occurrence 0
For example:

Title

Property http://purl.org/dc/elements/1.1/title
Min occurrence 1
Literal? Yes
Definition A name given to the resource.
Eprint-specific recommendation The title of the eprint.

Preserve the original wording, order and spelling of the eprint title. In general, only capitalize proper nouns, though there may be exceptions to this rule particularly regarding Internet-related terms. Punctuation need not reflect the usage of the original. Subtitles should be separated from the title by 'space-colon-space'.

For example:

Subject

Property http://purl.org/dc/elements/1.1/subject
Literal? No
Definition The topic of the content of the resource.
Eprint-specific recommendation The topic of the eprint.

In general, choose the most significant and unique words for keywords, avoiding those too general to describe a particular eprint. For free-text keywords use multiple statements, one for each term. There are no requirements regarding the capitalization of keywords though internal (within archive) consistency is recommended.

Where terms are taken from a standard classification scheme encode each term in a separate statement. Use a vocabulary encoding scheme URI to indicate the classification scheme in use. Encode the complete subject descriptor according to the relevant scheme. Use the capitalisation and punctuation used in the original scheme. Where subject terms are taken from LCSH, the subfields of the subject heading should be separated by double dash (--) and spaces should be omitted.

If the subject of the eprint is a person or an organization, provide their name as a value string according to A note about the form of personal and organisational names used in value strings.
Value (Non-Literal)
Value URI Constraint:
Occurrence optional
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Using LCSH subjects:

Name as subject:

Abstract

Property http://purl.org/dc/terms/abstract
Literal? Yes
Definition A summary of the content of the resource.
Eprint-specific recommendation A summary of the important points of the eprint.

Identifier

Property http://purl.org/dc/elements/1.1/identifier
Min occurrence 1
Literal? Yes
Definition An unambiguous reference to the resource within a given context.
Eprint-specific recommendation A URI for the eprint.
Value (Literal)
Syntax Encoding Scheme:
Occurrence mandatory
Choose from http://purl.org/dc/terms/URI
For example:

Note that one of the URIs for the eprint should be encoded as the resource URI in the description of the eprint. If a Handle has been assigned to the eprint then this should be used as the resource URI, encoded using the http://hdl.handle.net/4263537/4069 form. Additional URIs should be provided using a dc:identifier statement. (See the A note about using identifiers below.)

Creator

Property http://purl.org/dc/elements/1.1/creator
Literal? No
Definition An entity primarily responsible for making the content of the resource.
Eprint-specific recommendation An author of the eprint.

Use this property to provide the author's name and/or the URI of the author and/or to link to a related description (with the description set) about the author.

Where a name is provided, see A note about the form of personal and organisational names used in value strings.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Funder

Property http://www.loc.gov/loc.terms/relators/FND
Literal? No
Definition A person or organization that furnished financial support for the production of the work.
Eprint-specific recommendation Use this property to provide the funder's name and/or the URI of the funder and/or to link to a related description (within the description set) about the funder.

Where a name is provided, see A note about the form of personal and organisational names used in value strings.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Grant Number

Property http://purl.org/eprint/terms/grantNumber
Literal? Yes
Definition An alpha-numeric string identifying the funding grant under which the eprint was written.
Eprint-specific recommendation Use a value string to provide the grant number.

For example:

Supervisor

Property http://www.loc.gov/loc.terms/relators/THS
Literal? No
Definition A person under whose supervision a degree candidate develops and presents a thesis, mémoire, or text of a dissertation.
Eprint-specific recommendation Use this property to provide the supervisor's name and/or the URI of the supervisor and/or to link to a related description (within the description set) about the supervisor.

Where a name is provided, see A note about the form of personal and organisational names used in value strings.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Affiliated Institution

Property http://purl.org/eprint/terms/affiliatedInstitution
Literal? No
Definition An organisation to which a creator of the eprint is affiliated.
Eprint-specific recommendation Use this property to provide the affiliated organisation's name and/or the URI of the affiliated institution and/or to link to a related description (with the description set) about the affiliated institution.

Where a name of the affiliated organisation is provided, see A note about the form of personal and organisational names used in value strings.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Has Adaptation

Property http://purl.org/eprint/terms/hasAdaptation
Literal? No
Definition A scholarly work that results from the described eprint being recast in a new form.
Eprint-specific recommendation Use this property to provide a value URI of an adaptation of the eprint.

In the context of this application profile, an example of an adaptation is the powerpoint slides (the adaptation) used to present a conference paper (the eprint) at a conference.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Is Expressed As

Property http://purl.org/eprint/terms/isExpressedAs
Literal? No
Definition A version of the described eprint.
Eprint-specific recommendation An expression of the described eprint. In FRBR terms, an eprint is a Work.

Use this property to provide the URI of an expression of the eprint and/or to link to a related description (with the description set) about the expression.
Value (Non-Literal) Description: expression
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Description of an Expression of the eprint

Entity type

Property http://purl.org/dc/elements/1.1/type
Min occurrence 1
Max occurrence 1
Literal? No
Definition The type nature or genre of the content of the resource.
Eprint-specific recommendation Each of the entity descriptions in the description sets conforming with this application profile will need to be explicitly typed. This is done using a dc:type statement with one of the following value URIs taken from the [WWW]Eprints EntityType Vocabulary Encoding Scheme corresponding to the entity being described.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Choose from: http://purl.org/eprint/entityType/Expression/
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/entityType/
Value String Constraint:
Max occurrence 0
For example:

Title

Property http://purl.org/dc/elements/1.1/title
Literal? Yes
Definition A name given to the resource.
Eprint-specific recommendation A title for the expression of the eprint. Only use this property in cases where the expression title is different from the title of the eprint at the scholarly work level. For example, use this property to capture the title of a translation of the eprint.

Preserve the original wording, order and spelling of the eprint title. In general, only capitalize proper nouns, though there may be exceptions to this rule particularly regarding Internet-related terms. Punctuation need not reflect the usage of the original. Subtitles should be separated from the title by 'space-colon-space'.

For example:

Description

Property http://purl.org/dc/elements/1.1/description
Literal? Yes
Definition An account of the content of the resource.
Eprint-specific recommendation A description of the expression of the eprint. Use this property to describe how the expression relates to the eprint as a scholarly work and/or other expressions.

For example:

Identifier

Property http://purl.org/dc/elements/1.1/identifier
Min occurrence 1
Literal? Yes
Definition An unambiguous reference to the resource within a given context.
Eprint-specific recommendation A URI for the described expression of the eprint.
Value (Literal)
Syntax Encoding Scheme:
Occurrence mandatory
Choose from http://purl.org/dc/terms/URI
For example:

Note that one of the URIs for the described expression of the eprint should be encoded as the resource URI in the description of the expression. If a DOI or Handle has been assigned to the expression of the eprint then this should be used as the resource URI, encoded using the http://dx.doi.org/10.1000/152 or http://hdl.handle.net/4263537/4069 form. Additional URIs should be provided using a dc:identifier statement. (See the A note about using identifiers below.)

Date Available

Property http://purl.org/dc/terms/available
Max occurrence 1
Literal? Yes
Definition Date (often a range) that the resource will become or did become available.
Eprint-specific recommendation The date that the described expression of the eprint was first made public.

Use a value string to provide the date, formatted according to the W3C Date Time Format (W3CDTF) specification.
Value (Literal)
Syntax Encoding Scheme:
Occurrence mandatory
Choose from http://purl.org/dc/terms/W3CDTF
For example:

Status

Property http://purl.org/eprint/terms/status
Literal? No
Definition The status of the resource.
Eprint-specific recommendation The status of the described expression of the eprint. Recommended best practice is to provide a value URI taken from the [WWW]Eprints Status Vocabulary Encoding Scheme: http://purl.org/eprint/status/PeerReviewed or http://purl.org/eprint/status/NonPeerReviewed.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Choose from: http://purl.org/eprint/status/PeerReviewed
http://purl.org/eprint/status/NonPeerReviewed
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/status/
Value String Constraint:
Max occurrence 0
For example:

Version Number or String

Property http://purl.org/eprint/terms/version
Literal? Yes
Definition A version number or version string associated with the resource.
Eprint-specific recommendation A version number or version string associated with the described expression of the eprint.

For example:

Language

Property http://purl.org/dc/elements/1.1/language
Literal? No
Definition A language of the intellectual content of the resource.
Eprint-specific recommendation A language in which the described expression of the eprint is written. Use multiple statements if the described expression of the eprint is written in multiple languages. Provide a value string containing a language tag, formatted according to RFC-3066.
Value (Non-Literal)
Value URI Constraint:
Occurrence disallowed
Choose from:

Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Choose from:
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: mandatory
Option: http://purl.org/dc/terms/RFC3066
Language Constraint:
Occurrence disallowed
For example:

Type

Property http://purl.org/dc/elements/1.1/type
Literal? No
Definition The nature or genre of the content of the resource.
Eprint-specific recommendation The type of the described expression of the eprint.

Recommended best practice is to provide a value URI for a class from the [WWW]Eprints Type Vocabulary Encoding Scheme.
Value (Non-Literal)
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/type/
Value String Constraint:
Max occurrence 0
For example:

Copyright Holder

Property http://purl.org/eprint/terms/copyrightHolder
Literal? No
Definition A person or organization owning copyright in the resource.
Eprint-specific recommendation A person or organization owning copyright in the eprint.

Use this property to provide the copyright holder's name and/or the URI of the copyright holder and/or to link to a related description (with the description set) about the copyright holder.

Where a name is provided, see A note about the form of personal and organisational names used in value strings.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Has Version

Property http://purl.org/dc/terms/hasVersion
Literal? No
Definition The described resource has a version, edition, or adaptation, namely, the referenced resource.
Eprint-specific recommendation Use this property to provide the URI of an alternative expression of the eprint and/or to link to a related description (with the description set) about the alternative expression.
Value (Non-Literal) Description: expression
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Has Translation

Property http://purl.org/eprint/terms/hasTranslation
Literal? No
Definition A translation of the described resource.
Eprint-specific recommendation Use this property to provide the URI of an expression that is a translation of the described expression of the eprint and/or to link to a related description (with the description set) about the translated expression.
Value (Non-Literal) Description: expression
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Bibliographic Citation

Property http://purl.org/dc/terms/bibliographicCitation
Literal? Yes
Definition A bibliographic reference for the resource.
Eprint-specific recommendation Use this property to provide the text citation that should be used to cite the described expression of the eprint and/or to provide an OpenURL ContextObject for the described expression of the eprint following the guidelines in the [WWW]Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata DCMI Recommendation. In general, both a human-readable citation and a machine-readable OpenURL ContextObject should be provided.
Value (Literal)
Syntax Encoding Scheme:
Occurrence optional
Choose from info:ofi/fmt:kev:mtx:
For example:

Note that the lines above have been wrapped for readability.

References

Property http://purl.org/dc/terms/references
Literal? No
Definition The described resource references, cites, or otherwise points to the referenced resource.
Eprint-specific recommendation Use this property to provide the URI of an expression of a different eprint, a textual citation for the expression and/or an OpenURL ContextObject. In general, where a human-readable citation is provided a machine-readable OpenURL ContextObject should also be provided.
Value (Non-Literal)
Value URI Constraint:
Occurrence optional
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 2
Syntax Encoding Syntax Constraint:
Occurrence: optional
Option: info:ofi/fmt:kev:mtx:
Language Constraint:
Occurrence disallowed
For example:

Editor

Property http://www.loc.gov/loc.terms/relators/EDT
Literal? No
Definition A person or organization who prepares for publication a work not primarily his/her own, such as by elucidating text, adding introductory or other critical matter, or technically directing an editorial staff.
Eprint-specific recommendation A person or organisation that prepares the described expression of the eprint for publication.

Use this property to provide the editor's name and/or the URI of the editor and/or to link to a related description (with the description set) about the editor.

Where a name is provided, see A note about the form of personal and organisational names used in value strings.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Is Manifested As

Property http://purl.org/eprint/terms/isManifestedAs
Literal? No
Definition A manifestation of the described version of the eprint.
Eprint-specific recommendation A manifestation of the described expression of the eprint. In FRBR terms, an eprint is a Work.

Use this property to provide the URI of a manifestation of the expression of the eprint and/or to link to a related description (with the description set) about the manifestation.
Value (Non-Literal) Description: manifestation
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Description of a Manifestation of an Expression of the eprint

Entity type

Property http://purl.org/dc/elements/1.1/type
Min occurrence 1
Max occurrence 1
Literal? No
Definition The type nature or genre of the content of the resource.
Eprint-specific recommendation Each of the entity descriptions in the description sets conforming with this application profile will need to be explicitly typed. This is done using a dc:type statement with one of the following value URIs taken from the [WWW]Eprints EntityType Vocabulary Encoding Scheme corresponding to the entity being described.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Choose from: http://purl.org/eprint/entityType/Manifestation/
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/entityType/
Value String Constraint:
Max occurrence 0
For example:

Format

Property http://purl.org/dc/elements/1.1/format
Literal? No
Definition The physical or digital manifestation of the resource.
Eprint-specific recommendation The media-type of the described manifestation of an expression of the eprint.

Recommended best practice is to select a value string from the IANA registered list of Internet Media Types (MIME types).
Value (Non-Literal)
Value URI Constraint:
Occurrence disallowed
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: mandatory
Option: http://purl.org/dc/terms/IMT
Language Constraint:
Occurrence disallowed
For example:

Date Modified

Property http://purl.org/dc/terms/modified
Literal? Yes
Definition Date on which the resource was changed.
Eprint-specific recommendation The last modified date of the described manifestation of an expression of the eprint.

Use a value string to provide the date, formatted according to the W3C Date Time Format (W3CDTF) specification.
Value (Literal)
Syntax Encoding Scheme:
Occurrence mandatory
Choose from http://purl.org/dc/terms/W3CDTF
For example:

Publisher

Property http://purl.org/dc/elements/1.1/publisher
Literal? No
Definition An entity responsible for making the resource available.
Eprint-specific recommendation The publisher of the described manifestation of an expression of the eprint, typically either the author's institution or a commercial publisher.

Use this property to provide the publisher's name and/or the URI of the publisher and/or to link to a related description (with the description set) about the publisher.
Value (Non-Literal) Description: agent
Vocabulary Encoding Scheme Constraint
Occurrence: optional
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: disallowed
Language Constraint:
Occurrence optional
For example:

Is Available As

Property http://purl.org/eprint/terms/isAvailableAs
Literal? No
Definition A resource that is an exemplar of the described manifestation of an expression of the eprint.
Eprint-specific recommendation A copy of the described manifestation of an expression of the eprint. In FRBR terms, an eprint is a Work and a copy is an Item.

Use this property to provide the URI of a copy of a manifestation of an expression of the eprint.
Value (Non-Literal) Description: copy
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Description of a Copy of a Manifestation of an Expression of the eprint

Entity type

Property http://purl.org/dc/elements/1.1/type
Min occurrence 1
Max occurrence 1
Literal? No
Definition The type nature or genre of the content of the resource.
Eprint-specific recommendation Each of the entity descriptions in the description sets conforming with this application profile will need to be explicitly typed. This is done using a dc:type statement with one of the following value URIs taken from the [WWW]Eprints EntityType Vocabulary Encoding Scheme corresponding to the entity being described.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Choose from: http://purl.org/eprint/entityType/Copy/
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/entityType/
Value String Constraint:
Max occurrence 0
For example:

Access Rights

Property http://purl.org/dc/terms/accessRights
Literal? No
Definition Information about who can access the resource or an indication of its security status.
Eprint-specific recommendation Information about who can access the described copy of a manifestation of an expression of the eprint. In FRBR terms, an eprint is a Work and a copy is an Item. Recommended best practice is to provide a value URI for a class from the [WWW]Eprints AccessRights Vocabulary Encoding Scheme.
Value (Non-Literal)
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/accessRights/
Value String Constraint:
Max occurrence 0
For example:

Licence

Property http://purl.org/dc/terms/license
Literal? No
Definition A legal document giving official permission to do something with the resource.
Eprint-specific recommendation The terms under which the described copy of a manifestation of an expression of the eprint is made available. Typically, the URI of a licence statement should be provided as a value URI.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Date Available

Property http://purl.org/dc/terms/available
Max occurrence 1
Literal? Yes
Definition Date (often a range) that the resource will become or did become available.
Eprint-specific recommendation The date that the described copy of a manifestation of an expression of the eprint will become or did become public.

Use a value string to provide the date, formatted according to the W3C Date Time Format (W3CDTF) specification.
Value (Literal)
Syntax Encoding Scheme:
Occurrence mandatory
Choose from http://purl.org/dc/terms/W3CDTF
For example:

Is Part Of

Property http://purl.org/dc/terms/isPartOf
Literal? No
Definition The described resource is a physical or logical part of the referenced resource.
Eprint-specific recommendation A collection, typically a bibliographic collection, of which the described copy is a member.

Use both a value URI and a value string to indicate the collection.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 1
Syntax Encoding Syntax Constraint:
Occurrence: optional
Language Constraint:
Occurrence optional
For example:

Description of an Agent

Entity type

Property http://purl.org/dc/elements/1.1/type
Min occurrence 1
Max occurrence 1
Literal? No
Definition The type nature or genre of the content of the resource.
Eprint-specific recommendation Each of the entity descriptions in the description sets conforming with this application profile will need to be explicitly typed. This is done using a dc:type statement with one of the following value URIs taken from the [WWW]Eprints EntityType Vocabulary Encoding Scheme corresponding to the entity being described.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Choose from: http://purl.org/eprint/entityType/Person/
http://purl.org/eprint/entityType/Organization/
Vocabulary Encoding Scheme Constraint
Occurrence: mandatory
Choose from: http://purl.org/eprint/entityType/
Value String Constraint:
Max occurrence 0
For example:

Name

Property http://xmlns.com/foaf/0.1/name
Literal? Yes
Definition A name for some thing.
Eprint-specific recommendation A name for the agent (person or organisation).

In general, use foaf:family_name and foaf:givenname for describing persons and foaf:name for describing organisations.

Where a name is provided, see A note about the form of personal and organisational names used in value strings.

For example:

Family Name

Property http://xmlns.com/foaf/0.1/family_name
Literal? Yes
Definition The family name of some person.
Eprint-specific recommendation The family name of a person.

In general, use foaf:family_name and foaf:givenname for describing persons and foaf:name for describing organisations.

For example:

Given Name

Property http://xmlns.com/foaf/0.1/givenname
Literal? Yes
Definition The given name of some person.
Eprint-specific recommendation The given name of a person.

In general, use foaf:family_name and foaf:givenname for describing persons and foaf:name for describing organisations.

For example:

Workplace Homepage

Property http://xmlns.com/foaf/0.1/workplaceHomepage
Literal? No
Definition A workplace homepage of some person; the homepage of an organization they work for.
Eprint-specific recommendation The homepage of the organisation for which the author of the eprint works.

Use this property to provide the URI of the organisational homepage as a value URI.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Mailbox

Property http://xmlns.com/foaf/0.1/mbox
Literal? No
Definition A personal mailbox, ie. an Internet mailbox associated with exactly one owner, the first owner of this mailbox. This is a 'static inverse functional property', in that there is (across time and change) at most one individual that ever has any particular value for foaf:mbox.
Eprint-specific recommendation A mailbox associated with a person, formatted as a 'mailto' URI.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Homepage

Property http://xmlns.com/foaf/0.1/homepage
Literal? No
Definition A homepage for some thing.
Eprint-specific recommendation Provide the URI of the agent's Web homepage as a value URI.
Value (Non-Literal)
Value URI Constraint:
Occurrence mandatory
Vocabulary Encoding Scheme Constraint
Occurrence: disallowed
Value String Constraint:
Max occurrence 0
For example:

Entity typing

Each of the entity descriptions in the description sets conforming with this application profile will need to be explicitly typed. This is done using a dc:type statement with one of the following value URIs taken from the [WWW]Eprints EntityType Vocabulary Encoding Scheme:

For example:

A note about the form of personal and organisational names used in value strings

Where personal or organisational names are provided as value strings, the following guidelines should be followed.

Personal names should be listed surname or family name first, followed by comma-space, then the "usual" or preferred form of forenames and/or initials followed by a full stop. If necessary, this may be followed by the full set of spelled-out forenames in round brackets. Use the same form of name for all eprints, irrespective of the form used on the item itself. ||

For example:

In the case of organizations where there is clearly a hierarchy present, list the parts of the hierarchy from largest to smallest, separated by full stops. If it is not clear whether there is a hierarchy present, or unclear which is the larger or smaller portion of the body, give the name as it appears in the eprint. ||

For example:

The inclusion of personal and corporate name headings from authority lists constructed according to AACR2, e.g. the Library of Congress Name Authority File (LCNA), is also acceptable.

A note about using identifiers

Each of the entities in the model may be assigned a URI, encoded as the resource URI in the description of that entity.

It should be noted, however, that assigning and encoding a URI is not mandatory for any of the entities. Although the lack of a URI for any entity means that the entity can not be referenced from within metadata records in other eprint systems, the assignment of URIs to entities should be performed with care (and, where possible, after first checking whether a URI has already been assigned to the entity elsewhere). Multiple URIs for a single entity are likely to cause problems for downstream eprint systems, since it may be difficult for them to determine algorithmically whether any two URIs identify the same entity.

Where the ScholarlyWork and Expression entities in a description set have additional URIs, these should be encoded in one or more dc:identifier statements. As noted in the relevant sections above, in cases where there are multiple URIs for any entity, one of the URIs should be used as the resource URI. Recommended best practice is to use a DOI or Handle as the resource URI, where these exist.

The URIs assigned to each of the entities should uniquely identify a single entity. There may be more than one URI per entity, but each URI should only identify one entity.

It is an implementation issue whether the URIs assigned to the ScholarlyWork and Expression entities dereference to a representation of that entity. However, it is anticipated that eprint systems are likely to be configured such that the URI for ScholarlyWork and/or Expression entities dereference to a 'jump-off page' for the eprint, as served by the archive.

In all cases where a dc:identifier statement is provided, use a syntax encoding scheme URI to indicate that a URI is being provided. ||

For example:

It is not yet clear whether current practice is to assign DOIs at the level of the Work or at the level of the Expression (as those terms are used in FRBR) or in a more fine-grained way. The current [WWW]Crossref documentation indicates that DOIs should be assigned to the 'work', however it is not clear that this usage of the word 'work' corresponds with its usage in FRBR - in fact, it is rather more likely that it corresponds with the use of the term Expression in FRBR.

There is also other evidence that publishers typically assign DOIs at the level of the FRBR Expression. For example, the [WWW]DOI Handbook discussion about 'granularity' concludes that in practice it is safer to assign separate DOIs to each language translation of a given article, i.e. to assign DOIs at the level of the Expression.

As a result, it is suggested that the following guidelines are followed when making use of DOIs in the context of this application profile:

In all cases, the 'http://dx.doi.org/10.100/12345' form of URI encoding should be used.

Note that publisher-assigned DOIs are highly likely to fall into cases 1 or 2.

A note about mapping the Scholarly Works Application Profile to Simple DC

http://www.ukoln.ac.uk/repositories/digirep/index/Mapping_the_Scholarly_Works_Application_Profile_to_Simple_DC Mapping the Scholarly Works Application Profile to Simple DC] is available as a separate document.

The mapping enables software to 'dumb-down' (i.e. transform) a description set that conforms with this application profile to a description set that conforms with simple DC. In this context, 'simple DC' means a description set that comprises a single description that only uses the 15 properties in the [WWW]Dublin Core Metadata Element Set.

It is worth noting that by using this mapping, a description set that complies with this application profile will be dumbed-down to form a description that complies with the [WWW]Using simple DC to describe eprints document produced by the [WWW]ePrints UK project.

It is also worth noting that the resulting simple DC description is about the eprint as a ScholarlyWork. While this is not the only approach to mapping this application profile to simple DC (for example, it would also be possible to map this application profile to a set of simple DC descriptions about each of the Copy entities) it fits well with the intended usage of this application profile in the [WWW]OAI Protocol for Metadata Harvesting. In this case, each [WWW]OAI item will have associated records that correspond to both the oai_dc format and an XML format based on this application profile.

The particular mapping discussed here and in the separate document does not preclude alternative mappings being generated in the future.

Examples

Example 1

Example 2