Difference between revisions of "ESciDoc Application Profiles"

From MPDLMediaWiki
Jump to navigation Jump to search
(Grammatik Korrektur)
 
(181 intermediate revisions by 12 users not shown)
Line 1: Line 1:
* work in progress
{{ESciDoc Solutions}}


== Open issues ==
* work in progress (draft)
* Is the Application Profile specified for single solutions? (In the following you find PubMan Metadata)
** If yes, it would be a good idea to have specific namespaces for solution-specific metadata
** What would be the benefit of solution specific namespaces? Maybe elements start as solution-specific and get introduced to other solutions later?
* Do we need an application model as a basis for this application profile?
* URLs for Encoding Schemes are missing
* Complex Types like
** Date: We do have more date types, e.g. acceptance, publication, publication-online
* Other & minor issues
** Is Location confined to libraries?<br>Legacy requirement from SWB. This element is only expected to be filled for rare documents like manuscripts. If we want to concentrate on PubMan, we might consider deletion
** Encoding Scheme for identifier?
** How is the list of element sorted?
** Question: Do we need to document refinements which are inherited from external sources? Example: For "alternative" we currently repeat the information  ("Refines http://purl.org/dc/elements/1.1/title") from dcterms, the same is not done for "tableofcontents" (refines http://purl.org/dc/elements/1.1/description)
** OccElementurrence value for abstracts does not follow standard usage? ("Unlimited")


== Application Profile ==  
== Aim and Scope ==  
The eSciDoc Application Profiles (AP) documents the descriptive elements used by eSciDoc to describe its content entities, e.g. publications, organizations, etc. Additional information about objects (properties for items and its components) and structural relations between objects are also existing, but currently not considered in these APs. The APs are nowhere near to being complete yet.


This is the beginning of the Application Profile (AP) for eSciDoc and describes the descriptive metadata record stored for each publication (= the intellectual entity represented by an item object in eSciDoc). Additional information about objects (properties for items and its components) and structural relations between objects are also existing, but currently not considered in this AP. The AP is nowhere near to being complete yet.


In the first step, the AP is meant for documenting the existing xml schemas only. The document should be the basis for all future communication about the pubman metadata profile in use (and potentially replace the page [[PubMan Metadata Sets]]?). Anyway, we also expect that this approach will help us clarifying how to implement the requirements, thus the work will have certain impacts on the xml schemas.
The format of the table below follows the CEN Workshop Agreement 14855 for Dublin Core Application Profile Guidelines<ref name="cen14855">CWA14855: Dublin Core Application Profile guidelines, see http://dublincore.org/usage/documents/profile-guidelines/</ref>


===Namespaces===
==eSciDoc PubMan - Functional Requirements==


[[PubMan_Functionalities]]


==eSciDoc PubMan - Domain Model==


{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/
|-
| Name
| dcterms:
|-
| Label
| Dublin Core terms
|}
<br />
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/agmes/1.1/
|-
| Name
| ags:
|-
| Label
| Agricultural Metadata Element Set
|}
<br />
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms
|-
| Name
| escidoc:
|-
| Label
| eSciDoc terms
|}
<br />
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/idtypes
|-
| Name
| eidt:
|-
| Label
| eSciDoc ID types
|}
----
===Syntax Encoding Scheme===
{| border="1"
|colspan="2"|String data type definition
|-
|width="100pt"| Name
|width="500pt"| <string>
|-
| Label
| Character string
|-
| Definition
| A string of ASCII characters. No formatting tags may be included. The following characters must be encoded for XML: '&' - '&amp;'; '<' - '&lt;'; '>' - '&gt;'. A limited list of non-ASCII characters may be included encoded as character entities.
|}
{| border="1"
| colspan="2"|Date data type definition
|-
|width="100pt"| Name
|width="500pt"| <date>
|-
| Label
| Date
|-
| Defined By
| http://www.w3.org/TR/NOTE-datetime
|-
| Definition
|
Character string representing a date to the complete date level of the [http://www.w3.org/TR/NOTE-datetime W3CDTF] profile of ISO 8601
|}
{| border="1"
| colspan="2"|URI data type definition
|-
|width="100pt"| Name
|width="500pt"| <URI>
|-
| Label
| URI
|-
| Defined By
|http://www.ietf.org/rfc/rfc2396.txt
|-
| Definition
| Character string for a URI
|}
===Describing a publication===
====Elements and element refinements====
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/title
|-
| Name
| title
|-
| Label
| Title
|-
| Defined by:
| -
|-
| DC Definition
| A name given to the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| http://purl.org/dc/terms/alternative
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}


[[File:Domain Model.png]]


== eSciDoc Description Set Profile (Classes) ==


 
=== Publication ===
{| border="1"
{|style="border:1px solid #1b90b5; "
|width="100pt"| Term URI
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
|width="500pt"| http://purl.org/dc/terms/alternative
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/publication
|-
|-
| Name
| bgcolor=#CEE3F6 | '''Label'''
| alternative
| publication
|-
|-
| Label
| bgcolor=#CEE3F6 | '''DC Definition'''
| Alternative Title
| A book, article, or other documentary resource.
|-
|-
| Defined by:
| bgcolor=#CEE3F6 | '''DC Comment'''
| -
| -
|-
|-
| DC Definition
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| An alternative name for the resource.
| A publication, e.g. book, article, inproceedings.
|-
| DC Comment
| The distinction between titles and alternative titles is application-specific.
|-
| eSciDoc Definition
| -
|-
|-
| eSciDoc Comment
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''Type of term'''
| Property
| Class
|-
| Refines
| http://purl.org/dc/terms/title
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| -
| http://purl.org/dc/terms/BibliographicResource
|-
|-
| Enconding Scheme For
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Has Encoding Scheme
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min:0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
|}


 
=== File ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
 
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/file
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/type
|-
| Name
| type
|-
| Label
| Genre
|-
| Defined by:
| -
|-
| DC Definition
| The nature or genre of the resource.
|-
| DC Comment
| Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
|-
| eSciDoc Definition
| -
|-
|-
| eSciDoc Comment
| bgcolor=#CEE3F6 | '''Label'''
| -
| file
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| Property
| A digital resource.
|-
|-
| Refines
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Type of term'''
| -
| Class
|-
|-
| Enconding Scheme For
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| -
| -
|-
|-
| Has Encoding Scheme
| bgcolor=#CEE3F6 | '''Best practice'''
|http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/genre [[ESciDoc PublicationType Encoding Scheme]]
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1;
|-
| Best practice
| -
| -
|-
|-
| Open Questions
| bgcolor=#CEE3F6 | '''Remarks'''
| Maximum occurrence might be changed in the future
| -
|}
|}


 
=== Organization ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
{| border="1"
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/organization
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/language
|-
|-
| Name
| bgcolor=#CEE3F6 | '''Label'''
| language
| organization
|-
|-
| Label
| bgcolor=#CEE3F6 | '''DC Definition'''
| Language
| A resource that acts or has the power to act.
|-
|-
| Defined by:
| bgcolor=#CEE3F6 | '''DC Comment'''
| -
| -
|-
|-
| DC Definition
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| A language of the resource.
|-
| DC Comment
| Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
|-
| eSciDoc Definition
| -
| -
|-
|-
| eSciDoc Comment
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''Type of term'''
| Property
| Class
|-
|-
| Refines
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| -
| http://purl.org/dc/terms/Agent
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Enconding Scheme For
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Has Encoding Scheme
| RFC 4646
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min:0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
|}


 
=== Person ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
{| border="1"
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/person
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/identifier
|-
| Name
| identifier
|-
| Label
| Identifier
|-
| Defined by:
| -
|-
| DC Definition
| An unambiguous reference to the resource within a given context.
|-
| DC Comment
| Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
|-
| eSciDoc Definition
| An external identifier for the resource.
|-
| eSciDoc Comment
| -
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''Label'''
| Property
| person
|-
|-
| Refines
| bgcolor=#CEE3F6 | '''DC Definition'''
| -
| A resource that acts or has the power to act.
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''DC Comment'''
| -
| -
|-
|-
| Enconding Scheme For
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| -
| Detailed information of the person.
|-
|-
| Has Encoding Scheme
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| List a number of Schemes (URI), ISBN, ISSN, DOI, ...
|-
| Obligation
| Optional
|-
| Condition
| -
| -
|-
|-
| Datatype
| bgcolor=#CEE3F6 | '''Type of term'''
| URI
| Class
|-
|-
| Occurrence
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| Min: 0; Max: Unbounded
| http://purl.org/dc/terms/Agent
|-
|-
| Best practice
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Open Questions
| bgcolor=#CEE3F6 | '''Remarks'''
| Data type "URI" not agreed upon, Traugott sends more information, compare with SWAP AP
| -
|}
|}


 
=== Event ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
{| border="1"
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/event
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/creator
|-
|-
| Name
| bgcolor=#CEE3F6 | '''Label'''
| creator
|-
| Label
| Creator
|-
| Defined by:
| -
|-
| DC Definition
| An entity primarily responsible for making the resource.
|-
| DC Comment
| Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/contributer
|-
| Name
| contributer
|-
| Label
| Creator
|-
| Defined by:
| -
|-
| DC Definition
| An entity responsible for making contributions to the resource.
|-
| DC Comment
| Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/publishinginfo
|-
| Name
| publishinginfo
|-
| Label
| Publishing Info
|-
| Defined by:
| -
|-
| DC Definition
| An entity responsible for making the resource available.
|-
| DC Comment
| Examples of a Publisher include a person, an organization, or a service.
|-
| eSciDoc Definition
| The institution which published the item and additional information, e.g. the publisher name and place of a book, or the university where a theses has been created.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/publisher
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/created
|-
| Name
| created
|-
| Label
| Date Created
|-
| Defined by:
| -
|-
| DC Definition
| Date of creation of the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The date when the publication was created.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://www.w3.org/TR/NOTE-datetime
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| date
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"|  http://purl.org/dc/terms/dateSubmitted
|-
| Name
| dateSubmitted
|-
| Label
| Date Submitted
|-
| Defined by:
| -
|-
| DC Definition
| Date of submission of the resource.
|-
| DC Comment
| Examples of resources to which a Date Submitted may be relevant are a thesis (submitted to a university department) or an article (submitted to a journal).
|-
| eSciDoc Definition
|
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://www.w3.org/TR/NOTE-datetime
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| date
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"|  http://purl.org/dc/terms/modified
|-
| Name
| modified
|-
| Label
| Date Modified
|-
| Defined by:
| -
|-
| DC Definition
| Date on which the resource was changed.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://www.w3.org/TR/NOTE-datetime
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| date
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/issued
|-
| Name
| issued
|-
| Label
| Date Issued
|-
| Defined by:
| -
|-
| DC Definition
| Date of formal issuance (e.g., publication) of the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
|
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://www.w3.org/TR/NOTE-datetime
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| date
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/eprints/status
|-
| Name
| status
|-
| Label
| Review Method
|-
| Defined by:
| -
|-
| DC Definition
| -
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The type of the scientific review process for the described item.
|-
| eSciDoc Comment
| List contains: internal, peer, no review
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/reviewMethod [[ESciDoc_Encoding_Schemes#ReviewMethod_Encoding_Scheme|ReviewMethod Encoding Scheme]]
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| In encoding scheme include eprints "peerReviewed"
|}
 
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/isPartOf
|-
| Name
| isPartOf
|-
| Label
| is Part Of
|-
| Defined by:
| -
|-
| DC Definition
| A related resource in which the described resource is physically or logically included.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The bundle in which the item has been published, e.g. a journal, a book, a series or a database.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/extent
|-
| Name
| extent
|-
| Label
| Total number of pages
|-
| Defined by:
| -
|-
| DC Definition
| The size or duration of the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/format
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/bibliographicCitation
|-
| Name
| bibliographicCitation
|-
| Label
| -
|-
| Defined by:
| -
|-
| DC Definition
| A bibliographic reference for the resource.
|-
| DC Comment
| Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible.
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/identifier
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| OpenURL, Text
|-
| Obligation
| MA
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/event
|-
| Name
| event
| event
|-
|-
| Label
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| Event
|-
| Defined by:
| -
|-
| DC Definition
| -
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Some items are related to an event, e.g. a conference or a lecture series.
| Some items are related to an event, e.g. a conference or a lecture series.
|-
|-
| eSciDoc Comment
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''Type of term'''
| Property
| Class
|-
| Refines
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| -
| -
|-
|-
| Enconding Scheme For
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Has Encoding Scheme
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| -
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| C-DOC CRM standard event element?
|}
|}


 
=== Source ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
{| border="1"
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/source
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/degree
|-
|-
| Name
| bgcolor=#CEE3F6 | '''Label'''
| degree
| source
|-
|-
| Label
| bgcolor=#CEE3F6 | '''DC Definition'''
| Degree
| A book, article, or other documentary resource.
|-
|-
| Defined by:
| bgcolor=#CEE3F6 | '''DC Comment'''
| -
| -
|-
|-
| DC Definition
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| -
| The bundle in which the item has been published, e.g. a journal, a book, a series or a database.
|-
|-
| DC Comment
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| eSciDoc Definition
| bgcolor=#CEE3F6 | '''Type of term'''
| The type of degree which is received with this type of publication.
| Class
|-
|-
| eSciDoc Comment
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| List contains: master, diploma, magister, staatsexamen, phd, habilitation
| http://purl.org/dc/terms/BibliographicResource
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''Best practice'''
| Property
|-
| Refines
| -
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
|  [[ESciDoc_Encoding_Schemes#Degree_Encoding_Scheme|Degree Encoding Scheme]]
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| Clarify definition so that degree appears as a characteristic of the publication
|}
|}


 
=== Legal Case ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
 
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/legal-case
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/abstract
|-
| Name
| abstract
|-
| Label
| Abstract
|-
| Defined by:
| http://purl.org/dc/terms/
|-
|-
| DC Definition
| bgcolor=#CEE3F6 | '''Label'''
| A summary of the resource.
| legal case
|-
|-
| DC Comment
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| -
| -
|-
|-
| eSciDoc Definition
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| Abstract or short description of the item.
|-
| eSciDoc Comment
| -
| -
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''Type of term'''
| Property
| Class
|-
|-
| Refines
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
|}


 
=== Project-Info ===
 
{|style="border:1px solid #1b90b5; "
 
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
{| border="1"
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/project-info
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/subject
|-
| Name
| subject
|-
| Label
| Subject
|-
| Defined by:
| http://purl.org/dc/terms/
|-
| DC Definition
| The topic of the resource.
|-
| DC Comment
| Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element.
|-
| eSciDoc Definition
| Free keywords.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
|-
| Refines
| bgcolor=#CEE3F6 | '''Label'''
| -
| Project information
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| -
| The Project information contains information about funding project the publication is related to.
|-
|-
| Enconding Scheme For
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| Has Encoding Scheme
| bgcolor=#CEE3F6 | '''Type of term'''
| -
| Class
|-
|-
| Obligation
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| Optional
|-
| Condition
| -
| -
|-
|-
| Datatype
| bgcolor=#CEE3F6 | '''Best practice'''
| string
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
| -
|-
|-
| Open Questions
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|}
|}


==eSciDoc PubMan Description Templates (Statements) ==


* [[ESciDoc_Application_Profile_Publication|Description Template Publication]]
* [[ESciDoc_Application_Profile_Source|Description Template Source]]
* [[ESciDoc_Application_Profile_Person|Description Template Person]]
* [[ESciDoc_Application_Profile_Organization|Description Template Organization]]
* [[ESciDoc_Application_Profile_File|Description Template File]]
* [[ESciDoc_Application_Profile_Event|Description Template Event]]
* [[ESciDoc_Application_Profile_LegalCase|Description Template Legal Case]]
* [[ESciDoc_Application_Profile_Yearbook|Description Template Yearbook]]
* [[ESciDoc_Application_Profile_project-info|Description Template project-info]]


== Related eSciDoc Encoding Schemes ==
* [[ESciDoc_Encoding_Schemes]]


{| border="1"
== References ==
|width="100pt"| Term URI
<references/>
|width="500pt"| http://purl.org/dc/terms/tableOfContents
|-
| Name
| tableofcontents
|-
| Label
| Table of Contents
|-
| Defined by:
| -
|-
| DC Definition
| A list of subunits of the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Table of contents of the described item.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://www.loc.gov/mods/location
|-
| Name
| location
|-
| Label
| Location
|-
| Defined by:
|
|-
| DC Definition
| -
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The name of the library where the item is currently located.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
== Application Profile for Entity Person ==
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://xmlns.com/foaf/0.1/name
|-
| Name
| name
|-
| Label
| Complete Name
|-
| Defined by:
| -
|-
| FOAF Definition
| A name for some thing.
|-
| FOAF Comment
|
|-
| eSciDoc Definition
| The complete name of a person, usually a concatenation of given names and family name.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://xmlns.com/foaf/0.1/family_name
|-
| Name
| family_name
|-
| Label
| Family Name
|-
| Defined by:
| -
|-
| FOAF Definition
| The family_name of some person.
|-
| FOAF Comment
|
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://xmlns.com/foaf/0.1/givenname
|-
| Name
| givenname
|-
| Label
| Given Name
|-
| Defined by:
| -
|-
| FOAF Definition
| The given name of some person.
|-
| FOAF Comment
|
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://xmlns.com/foaf/0.1/nick
|-
| Name
| nick
|-
| Label
| Pseudonym
|-
| Defined by:
| -
|-
| FOAF Definition
| A short informal nickname characterising an agent (includes login identifiers, IRC and other chat nicknames).
|-
| FOAF Comment
|
|-
| eSciDoc Definition
| The pen or stage name of a person.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| For "Pseudonym" we should probably use an eSciDoc term
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/alternative_name
|-
| Name
| alternative_name
|-
| Label
| Alternative Name
|-
| Defined by:
| -
|-
| FOAF Definition
| -
|-
| FOAF Comment
| -
|-
| eSciDoc Definition
| Any alternative name used for the person.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://xmlns.com/foaf/0.1/title
|-
| Name
| title
|-
| Label
| Title
|-
| Defined by:
| -
|-
| FOAF Definition
| Title (Mr, Mrs, Ms, Dr. etc)
|-
| FOAF Comment
| -
|-
| eSciDoc Definition
| The title or peerage of a person in one string.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
 
 
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://www.bs.dk/standards/namespace/ac/affiliation
|-
| Name
| affiliation
|-
| Label
| Organisation
|-
| Defined by:
| -
|-
| AC Definition
| The organization with which the named person was associated when involved with the resource
|-
| AC Comment
| Often the "affiliation institution" will be the formally responsible entity
|-
| eSciDoc Definition
| The organizational unit the person was affiliated to when creating the item.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1;
|-
| Best practice
| -
|-
| Open Questions
| To prevent ambiguities shouldn't the label be "Affiliation" instead of "Organization"?
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/identifier
|-
| Name
| identifier
|-
| Label
| Identifier
|-
| Defined by:
| -
|-
| DC Definition
| An unambiguous reference to the resource within a given context.
|-
| DC Comment
| Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
|-
| eSciDoc Definition
| Identifier in the Personennamendatei, provided by the Deutsche Nationalbibliothek.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| Only IdType “PND” is allowed.
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
== Application Profile of an Organisation ==
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://xmlns.com/foaf/0.1/name
|-
| Name
| name
|-
| Label
| Name
|-
| Defined by:
| -
|-
| FOAF Definition
| A name for some thing.
|-
| FOAF Comment
| -
|-
| eSciDoc Definition
| The name of the organization as used in the item.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/address
|-
| Name
| address
|-
| Label
| Address
|-
| Defined by:
| -
|-
| DC Definition
|
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The address of the organization as used in the item.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| To avoid ambiguities, the property should be named and labeled differently, e.g. "organization_address". Perhaps there is already a defined term around?
|}
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/identifier
|-
| Name
| identifier
|-
| Label
|Identifier
|-
| Defined by:
| -
|-
| DC Definition
| An unambiguous reference to the resource within a given context.
|-
| DC Comment
| Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
|-
| eSciDoc Definition
| The id of the corresponding organizational unit in the system.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| Is this a systems metadata entry, or a truely descriptive element? Should it be linked to an Authority File?
|}
 
 
 
== Application Profile of an Event ==
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/title
|-
| Name
| title
|-
| Label
| Title
|-
| Defined by:
| -
|-
| DC Definition
| A name given to the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The title of the event.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/alternative
|-
| Name
| alternative
|-
| Label
| Alternative Title
|-
| Defined by:
| -
|-
| DC Definition
| An alternative name for the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| The event may have one or several alternative forms of the title (e.g. an abbreviated title).
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/agmes/1.1/dateStart
|-
| Name
| dateStart
|-
| Label
| Start Date
|-
| Defined by:
| -
|-
| AG-event Definition
| Date on which the event will start.
|-
| AG-event Comment
| -
|-
| eSciDoc Definition
| Start date of an event.
|-
| eSciDoc Comment
|
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://www.w3.org/TR/NOTE-datetime
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| date
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/agmes/1.1/dateEnd
|-
| Name
| dateEnd
|-
| Label
| End Date
|-
| Defined by:
| -
|-
| AG-event Definition
| Date on which the event will end.
|-
| AG-event Comment
| -
|-
| eSciDoc Definition
| End date of an event.
|-
| eSciDoc Comment
|
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| http://www.w3.org/TR/NOTE-datetime
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| date
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| place
|-
| Name
| place
|-
| Label
| Place
|-
| Defined by:
| -
|-
| DC Definition
|
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Place of an event.
|-
| eSciDoc Comment
|
|-
| Type of term
| Property
|-
| Refines
|
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
|
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| Have not found an adequate predefined property
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://escidoc.mpg.de/metadataprofile/schema/0.1/terms/invitation_status
|-
| Name
| invitation_status
|-
| Label
| Invitation Status
|-
| Defined by:
| -
|-
| DC Definition
|
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The information whether or not the creator was explicitly invited.
|-
| eSciDoc Comment
|
|-
| Type of term
| Property
|-
| Refines
|
|-
| Refined by
| -
|-
| Enconding Scheme For
| -
|-
| Has Encoding Scheme
| yes or no
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| Have not found an adequate predefined property
|}
 
 
 
 
 
 




[[Category:eSciDoc]]
[[Category:ESciDoc_Application_Profiles| ]]
[[Category:Metadata]]
[[Category:PubMan_Functional_Specification|Application_Profile]]

Latest revision as of 06:50, 1 July 2016

eSciDoc Solutions

PubMan:
Overview · Functionalities
Interfaces · Support

Faces:
Overview · Functionalities
Scope · Support

ViRR:
Overview · Functionalities
Scope · Support

imeji
Digitization Lifecycle

edit


  • work in progress (draft)

Aim and Scope[edit]

The eSciDoc Application Profiles (AP) documents the descriptive elements used by eSciDoc to describe its content entities, e.g. publications, organizations, etc. Additional information about objects (properties for items and its components) and structural relations between objects are also existing, but currently not considered in these APs. The APs are nowhere near to being complete yet.


The format of the table below follows the CEN Workshop Agreement 14855 for Dublin Core Application Profile Guidelines[1]

eSciDoc PubMan - Functional Requirements[edit]

PubMan_Functionalities

eSciDoc PubMan - Domain Model[edit]

Domain Model.png

eSciDoc Description Set Profile (Classes)[edit]

Publication[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/publication
Label publication
DC Definition A book, article, or other documentary resource.
DC Comment -
eSciDoc Definition A publication, e.g. book, article, inproceedings.
eSciDoc Comment -
Type of term Class
NarrowerThan http://purl.org/dc/terms/BibliographicResource
Best practice -
Remarks -

File[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/file
Label file
eSciDoc Definition A digital resource.
eSciDoc Comment -
Type of term Class
NarrowerThan -
Best practice -
Remarks -

Organization[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/organization
Label organization
DC Definition A resource that acts or has the power to act.
DC Comment -
eSciDoc Definition -
eSciDoc Comment -
Type of term Class
NarrowerThan http://purl.org/dc/terms/Agent
Best practice -
Remarks -

Person[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/person
Label person
DC Definition A resource that acts or has the power to act.
DC Comment -
eSciDoc Definition Detailed information of the person.
eSciDoc Comment -
Type of term Class
NarrowerThan http://purl.org/dc/terms/Agent
Best practice -
Remarks -

Event[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/event
Label event
eSciDoc Definition Some items are related to an event, e.g. a conference or a lecture series.
eSciDoc Comment -
Type of term Class
NarrowerThan -
Best practice -
Remarks -

Source[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/source
Label source
DC Definition A book, article, or other documentary resource.
DC Comment -
eSciDoc Definition The bundle in which the item has been published, e.g. a journal, a book, a series or a database.
eSciDoc Comment -
Type of term Class
NarrowerThan http://purl.org/dc/terms/BibliographicResource
Best practice -
Remarks -

Legal Case[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/legal-case
Label legal case
eSciDoc Definition -
eSciDoc Comment -
Type of term Class
Best practice -
Remarks -

Project-Info[edit]

Term URI http://purl.org/escidoc/metadata/profiles/0.1/project-info
Label Project information
eSciDoc Definition The Project information contains information about funding project the publication is related to.
eSciDoc Comment -
Type of term Class
NarrowerThan -
Best practice -
Remarks -

eSciDoc PubMan Description Templates (Statements)[edit]

Related eSciDoc Encoding Schemes[edit]

References[edit]

  1. ↑ CWA14855: Dublin Core Application Profile guidelines, see http://dublincore.org/usage/documents/profile-guidelines/

Enhanced Scientific Documentation

Application Profile

Comitée européen de normalisation

Publication Management

Uniform Resource Identifier

Dublin Core

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=ESciDoc_Application_Profiles&oldid=103971"