Difference between revisions of "ESciDoc Application Profiles"

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


== Open issues ==
* work in progress (draft)


=== PURLs / Namespaces  ===
== Aim and Scope ==  
Natasa reserved the domain http://purl.org/escidoc.  
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.


==== Substructure ====
To be able to move forward we have to define a '''substructure''' for the domain. We agreed on following conventions for th path: all lower case, without delimiters


Suggested structure:
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>
* http://purl.org/escidoc/metadata/terms/ -- for the list of eSciDoc-specific terms
* http://purl.org/escidoc/metadata/terms/types/ -- for our own genre encoding scheme entries (e.g. + talkatevent)
* http://purl.org/escidoc/metadata/terms/reviewmethod/ -- review method encoding scheme entries (e.g. + noreview)
* http://purl.org/escidoc/metadata/terms/degree/ -- degree encoding scheme entries (e.g. +phd)
* http://purl.org/escidoc/metadata/terms/invitationstatus/ -- invitation status (e.g. invited) for describing an event
* http://purl.org/escidoc/metadata/terms/creatorrole/ -- encoding scheme for roles of contributors (e.g. author, photographer,...)
* http://purl.org/escidoc/metadata/profiles -- for the list of our application profiles


: Andi, I thought that "degree" would be a eSciDoc-specific term, so I would rather use http://purl.org/escidoc/metadata/terms/degree than http://purl.org/escidoc/metadata/degree... but again, it looks like we are facing terminology problems --[[User:Inga|Inga]] 12:48, 10 March 2008 (CET)
==eSciDoc PubMan - Functional Requirements==
:: Inga, you're right -- [[User:Andi|Andreas Gros]] 08:46, 13 March 2008 (CET)
::: Am I right that http://purl.org/escidoc/metadata/terms/creatorrole/ would only include encoding scheme entries which are used by eSciDoc in addition to those selected from MARC relators? --[[User:Inga|Inga]] 16:44, 13 March 2008 (CET)
:::: Yes, that's right [[User:Andi|Andreas Gros]] 09:45, 14 March 2008 (CET)


The standard procedure is to indicate that something is an encoding scheme with a forward slash at the end:
[[PubMan_Functionalities]]
* http://purl.org/escidoc/metadata/terms/types/
* http://purl.org/escidoc/metadata/terms/degree/
and refer to the property itself, e.g. degree, without the slash:
* http://purl.org/escidoc/metadata/terms/degree


:Andi, i did not got the last paragraph exactly probably. I think with "/" or without "/" is a very very small difference. This means that somehow we are really heavily "linking" the possible values (encoding schemas) to be specific to the metadata elements themselves. Why we put metadata elements (only without "/" in under the "terms"?) Are all of our metadata under "terms" namespace (those that are escidoc specific)? Or to be more precise: Is there a big reason not to have
==eSciDoc PubMan - Domain Model==
: "http://purl.org/escidoc/metadata/elements/degree" and
: "http://purl.org/escidoc/metadata/terms/degree" -> that point to allowed values?
: Maybe is only my confusion, but just to cross check again. --[[User:Natasab|Natasa]] 13:26, 13 March 2008 (CET)
:: This URL (http://purl.org/escidoc/metadata/terms/degree/) is only an identifier that is listed in an application profile together with a descriptive text (and links to the list of terms that appear on the page http://escidoc.org/metadata/terms/degree/''index.xxx'' (for example)). Therefore, I think that it is no problem that the '''terms''' belonging to the encoding scheme ''degree'' appear under  http://purl.org/escidoc/metadata/'''terms'''/degree/phd, http://purl.org/escidoc/metadata/'''terms'''/degree/staatsexamen, etc. that link to entries on the page mentioned above (http://escidoc.org/metadata/terms/degree/''index.xxx''). -- [[User:Andi|Andreas Gros]] 09:52, 14 March 2008 (CET)


==== Location ====
Furthermore, the PURLs have to '''link/resolve''' to somewhere (see discussion on https://zim01.gwdg.de/trac/wiki/MDSSpec/Namespaces). Following this discussion [[User:Andi|Andreas Gros]] suggests to use:
* for profiles: http://www.escidoc.org/metadata/profiles/2008/03/xx/
* for terms:    http://www.escidoc.org/metadata/terms/2008/03/xx/
* and likewise for types, reviewmethod, etc. like above
* and link the most recent version to the corresponding default URL:
* for profiles: http://www.escidoc.org/metadata/profiles/
* for terms:    http://www.escidoc.org/metadata/terms/
During the FIZ-SUB-MPDL-VC-Meeting we agreed on switching from escidoc.de to escidoc.org because of the increasingly international context eSciDoc is used in and linked to.


: Would it be http://purl.org/escidoc/metadata/terms/2008/03/xx/reviewmethod/ or http://purl.org/escidoc/metadata/terms/reviewmethod/2008/03/xx/? --[[User:Inga|Inga]] 16:53, 13 March 2008 (CET)
[[File:Domain Model.png]]


=== Elements ===
== eSciDoc Description Set Profile (Classes) ==


==== dc:creator versus dc:contributor ====
=== Publication ===
 
{|style="border:1px solid #1b90b5; "
What is our understanding of the property "creator"? Do we actually mean "contributor" with different roles? Do we use creator for "the main or leading author"?
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
 
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/publication
Recommendation from meeting with Natasa, Ulla, Malte, Andi, Inga: Replace dc:creator by dc:contributor.
:Just to remark: dc:contributor - An entity responsible for making contributions to the resource. dc:creator - An entity primarily responsible for making the resource. [[User:Frank|Frank]] 08:51, 11 March 2008 (CET)
:: Currently, the pubman metadata schema not complies with the distinction between "primarily responsible" and "contributed" made by dc. We only have entities (persons/organizations) which participated in content generation and their specific role (e.g. author, editor, etc.). It was argued that all pubman creators with type "author" are ''dc:creators'' and pubman creators of any other type are ''dc:contributors''. Two contra arguments:
::* for proceedings and edited books, a creator of type "editor" is probably the entity primarily responsible for making the resource
::* for journal articles with more than a handful of authors it's quite reasonable that not all of them has been primarily responsible for the publication (see [http://edoc.mpg.de/307411 edoc example]). But the person entering the record in PubMan does not necessarily know which creators are ''dc:creators'' in the core sense (as we understood it now) and which are not. In addition, we  have no use case which requires the distinction introduced by Dublin Core<br>BTW: As you can see in the edoc example provided above, the authors are not listed alphabetically, but the order encodes their importance for this paper, see http://www.sciencedaily.com/releases/2007/11/071105103938.htm. Please note that we will consider mapping the first creator to ''dc:creator'' for transformations to dc simple. --[[User:Inga|Inga]] 20:19, 11 March 2008 (CET)
::: Traugott made the point, that we must not over-interpret the dc comment on ''primarily responsible''. The standard use case is that each author of a paper is a ''dc:creator'', no matter how important they were in creating the article. Each creator can be given a corresponding ''creatorrole''. The cases in which contributors are used should follow best-practises, like:
::: *http://dublincore.org/documents/usageguide/elements.shtml
::: *http://www.lib.ncsu.edu/cataloging/metadata/NCSUcore1.html
::: Most importantly, using ''dc:contributor'' as a replacement for ''dc:creator'' would decouple eSciDoc from most external search-engines because the common property to be looked up when searching for an author is ''dc:creator'' and not ''dc:contributor''.
:::: It fine for me to use dc:creator with an creator role (this is what we are currently practicing ;). Does anybody expect us to provide a more detailed mapping (e.g. an illustrator of an article is dc:contributor but no dc:creator)? --[[User:Inga|Inga]] 10:28, 13 March 2008 (CET)
 
==== dc:subject ====
Vocabulary:
* [http://www.oclc.org/dewey/about/ Dewey Decimal Classification (DDC)].
** An overview on the first three levels is available in [http://en.wikipedia.org/wiki/List_of_Dewey_Decimal_classes Wikipedia], OCLC offers the [http://www.oclc.org/dewey/resources/summaries/default.htm DDC 22 Summaries] as pdf file
** DDC requires a licence. The pricing can be found at: http://www.oclc.org/support/forms/pdf/dfwpro.pdf
* [http://www.loc.gov/aba/cataloging/classification/ Library of Congress Classification (LCC)]
 
'''Discussion''':
: Traugott strongly suggests to use DDC, because it is the only system adapted to online usage and which is maintained and enhanced continuously. It is also fine-grained enough to allow the classification of a large number of documents, so that not too many documents end up in the same class.
 
==== missing & more ====
 
Are there predefined properties for:
*Person->Pseudonym,
*Person->Alternative_Name
*Organization->Address,
*: [[EduPerson| eduPerson]] defines a property called postalAddress. Perhaps thats interesting for you? --[[User:Kristina|Kristina]] 09:05, 13 February 2008 (CET)
*Event->Place,
*Event->Invitation_Status ?
 
'''Further questions, see element list below'''
 
=== Encoding Schemes and Data Types ===
 
* '''ReviewMethod''': Eprints calls it "status" (http://purl.org/eprint/status/PeerReviewed and http://purl.org/eprint/status/NonPeerReviewed). Our PubMan set includes the following review methods: ''no review, internal'', and ''peer''. As our ''peer'' matches the meaning of ''PeerReviewed'' of Eprints, the following substructure suggests itself: use http://purl.org/eprint/status/PeerReviewed for ''peer'', and use
**  http://purl.org/escidoc/metadata/reviewmethod/internal
**  http://purl.org/escidoc/metadata/reviewmethod/noreview
* '''Degree''': I have not found any good encoding scheme for academic degrees. The PubMan set contains this list of degrees: ''master, diploma, magister, staatsexamen, phd, habilitation''. What about using the following domain for the scheme/non-predefined terms:
** http://purl.org/escidoc/metadata/terms/degree/staatsexamen ...
:: However, ''degree'' is a rather ambiguous term, wouldn't it be better to use ''academic_degree'' instead?
:: [[User:Andi|Andreas Gros]] sent an E-Mail to the BMBF to ask for a list of standardized terms of academic degrees used internationally and within Germany
 
* '''Publication identifier''': which data type to use?
**either datatype "string" with a corresponding encoding scheme for the plain-text entries. Taking this option would mean that we can store just the ISBN/ISSN/DOI/...-number in this property, but we would need an export mechanism for the external world to access this information.
**or datatype "URI" where the identifier is encoded into a URI, e.g.: http://...&ISSN=... Using this option would mean that we are more interoperable with the outside world as others would access such URIs directly, but for internal usage we would have to decode the information again.
:::Konstantin (GBV) mentioned not to store http-resolver-part with PIDs because the PID then is bound to a specific resolver but to establish some kind of handler that is able to transform a PID to the appropriate URL. So the http-resolver-part is not a part of the PID itself but is part of the resolving system which comes with the PID. [[User:Frank|Frank]] 09:31, 11 March 2008 (CET)
 
=== Further Tasks ===
 
* Answer open questions
* Polishing of AP, e.g. adding best practice examples, define structure and headings of AP?
* Which consequences need to be derived from the AP to existing escidoc publication xml schemas? (e.g. usage of dc:creator, dc:source and dc:type; re-use foaf elements; integrate links to terms?)
* Functional changes under discussion for r3, see https://zim01.gwdg.de/trac/wiki/MDSSpec/Revision
* Requirements regarding copyrights, see http://colab.mpdl.mpg.de/mediawiki/EDoc_to_PubMan_migration#Copyright_Information
* Do we need an application model as a basis for this application profile?
* Recommendation for identifier usage required
* Check person-pseudonym: Inga
 
* AP for file required: Andi
* Decision on subject vocabulary (DDC) - check this with Traugott: Andi - DONE, see above
* Input for contributor roles used on edoc: Ulla & Vlad
* Compare with relators provided by LoC, see http://www.loc.gov/loc.terms/relators/
 
=== Process ===
# finish AP
# register PURLs
# revise pubman xsd to reference definitions (ours and externals)
----
 
== Application Profile ==
 
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 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. 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://www.cen.eu/cenorm/businessdomains/businessdomains/isss/cwa/cwa14855.asp</ref>
 
===Namespaces===
 
{| 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://www.w3.org/2006/vcard/ns#
|-
| Name
| vCard:
|-
| Label
| An Ontology for vCards
|}
 
<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://purl.org/escidoc/metadata/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
| bgcolor=#CEE3F6 | '''Label'''
| -
| publication
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''DC Definition'''
| http://purl.org/dc/terms/alternative
| A book, article, or other documentary resource.
|-
|-
| Encoding Scheme For
| bgcolor=#CEE3F6 | '''DC Comment'''
| -
| -
|-
|-
| Has Encoding Scheme
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| -
| A publication, e.g. book, article, inproceedings.
|-
|-
| Obligation
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| Mandatory
|-
| Condition
| -
| -
|-
|-
| Datatype
| bgcolor=#CEE3F6 | '''Type of term'''
| string
| Class
|-
|-
| Occurrence
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| Min: 1; Max: 1
| http://purl.org/dc/terms/BibliographicResource
|-
|-
| Best practice
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Open Questions
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|}
|}


 
=== File ===
{| 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/file
|-
| Name
| alternative
|-
| Label
| Alternative Title
|-
| Defined by:
| -
|-
| DC Definition
| An alternative name for the resource.
|-
|-
| DC Comment
| bgcolor=#CEE3F6 | '''Label'''
| The distinction between titles and alternative titles is application-specific.
| file
|-
|-
| eSciDoc Definition
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| -
| A digital resource.
|-
|-
| 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/title
|-
| Refined by
| -
| -
|-
|-
| Encoding 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
| -
|}
|}


 
=== Organization ===
 
{|style="border:1px solid #1b90b5; "
{| border="1"
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
|width="100pt"| Term URI
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/organization
|width="500pt"| http://purl.org/dc/terms/type
|-
|-
| Name
| bgcolor=#CEE3F6 | '''Label'''
| type
| organization
|-
|-
| Label
| bgcolor=#CEE3F6 | '''DC Definition'''
| Genre
| A resource that acts or has the power to act.
|-
|-
| Defined by:
| bgcolor=#CEE3F6 | '''DC Comment'''
| -
| -
|-
|-
| DC Definition
| bgcolor=#CEE3F6 | '''eSciDoc 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<ref name="dcmitype">DCMI Type Vocabulary [DCMITYPE], see http://dublincore.org/documents/dcmi-type-vocabulary/"</ref>. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
|-
| 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'''
| -
| -
|-
|-
| Encoding Scheme For
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Has Encoding Scheme
|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
| Maximum occurrence might be changed in the future
|}
|}


 
=== Person ===
{| border="1"
{|style="border:1px solid #1b90b5; "
|width="100pt"| Term URI
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
|width="500pt"| http://purl.org/dc/terms/language
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/person
|-
|-
| Name
| bgcolor=#CEE3F6 | '''Label'''
| language
| person
|-
|-
| 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.
| Detailed information of the person.
|-
| DC Comment
| Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| RFC 4646
|-
| Obligation
| Optional
|-
|-
| Condition
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| Datatype
| bgcolor=#CEE3F6 | '''Type of term'''
| string
| 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'''
| -
| -  
|}
|}


 
=== 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/identifier
|-
| Name
| identifier
|-
| Label
| Identifier
|-
|-
| Defined by:
| bgcolor=#CEE3F6 | '''Label'''
| -
|-
| 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
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| List a number of Schemes (URI), ISBN, ISSN, DOI, ...
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| URI
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| Data type "URI" not agreed upon, Traugott sends more information, compare with SWAP AP
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/creator
|-
| Name
| 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
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| -
|}
 
 
Example: http://schemas.library.nhs.uk/Term/DC/contributor.html
 
{| 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
| [marcrel:AUT] Author
http://www.loc.gov/loc.terms/relators/AUT
|-
| Refined by
| [marcrel:EDT] Editor
http://www.loc.gov/loc.terms/relators/EDT
|-
| Refined by
| [marcrel:ILL] Illustrator
http://www.loc.gov/loc.terms/relators/ILL
|-
| Refined by
| [marcrel:TRL] Translator
http://www.loc.gov/loc.terms/relators/TRL
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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/dateAccepted
|-
| Name
| dateAccepted
|-
| Label
| Date Accepted
|-
| Defined by:
| -
|-
| DC Definition
| Date of acceptance of the resource.
|-
| DC Comment
| Examples of resources to which a Date Accepted may be relevant are a thesis (accepted by a university department) or an article (accepted by a journal).
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/date
|-
| Refined by
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| -
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Best practice'''
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| -
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
| -
|-
|-
| Open Questions
| bgcolor=#CEE3F6 | '''Remarks'''
| 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
| List contains: master, diploma, magister, staatsexamen, phd, habilitation
|-
|-
| Type of term
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| Property
| http://purl.org/dc/terms/BibliographicResource
|-
|-
| Refines
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Encoding 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'''
| -
| -  
|-
| Encoding 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/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
| -
|-
| Refined by
| -
|-
| Encoding 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/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
| -
|-
| Encoding 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
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| Location is a class with further properties in MODS, so possibly not a good choice. An alternative would be to use the "address" property of the Z39.50 Application Profile for Geospatial Metadata.
|}
 
== 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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.w3.org/2006/vcard/ns/org
|-
| Name
| org
|-
| Label
| Organization
|-
| Defined by:
| -
|-
| vCard Definition
| An organization associated with a person
|-
| vCard Comment
|
|-
| eSciDoc Definition
| The organizational unit the person was affiliated to when creating the item.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -The domain of the vCard:org property is the vCard:VCard class.<br /> -The range of the v:org property is the v:Organization class.
|-
| 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
| -
|-
| Encoding 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 Organization ==
 
 
{| 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
| -
|-
| Encoding 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
| -
|-
| Encoding 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? Maybe use http://www.w3.org/2006/03/hcard
|}
 
 
{| 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
| -
|-
| Encoding 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 truly 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
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| -
|}
|}


 
=== Project-Info ===
 
{|style="border:1px solid #1b90b5; "
{| border="1"
|width="150pt" bgcolor=#CEE3F6| '''Term URI'''
|width="100pt"| Term URI
|width="500pt"| http://purl.org/escidoc/metadata/profiles/0.1/project-info
|width="500pt"| http://purl.org/dc/terms/alternative
|-
| Name
| alternative
|-
| Label
| Alternative Title
|-
|-
| Defined by:
| bgcolor=#CEE3F6 | '''Label'''
| -
| Project information
|-
|-
| DC Definition
| bgcolor=#CEE3F6 | '''eSciDoc Definition'''
| An alternative name for the resource.
| The Project information contains information about funding project the publication is related to.
|-
|-
| DC Comment
| bgcolor=#CEE3F6 | '''eSciDoc Comment'''
| -
| -
|-
|-
| eSciDoc Definition
| bgcolor=#CEE3F6 | '''Type of term'''
| -
| Class
|-
|-
| eSciDoc Comment
| bgcolor=#CEE3F6 | '''NarrowerThan'''
| The event may have one or several alternative forms of the title (e.g. an abbreviated title).
|-
| Type of term
| Property
|-
| Refines
| -
| -
|-
|-
| Refined by
| bgcolor=#CEE3F6 | '''Best practice'''
| -
| -
|-
|-
| Encoding Scheme For
| bgcolor=#CEE3F6 | '''Remarks'''
| -
| -  
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded
|-
| Best practice
| -
|-
| Open Questions
| -
|}
|}


==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]]


{| border="1"
== Related eSciDoc Encoding Schemes ==
|width="100pt"| Term URI
* [[ESciDoc_Encoding_Schemes]]
|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
| -
|-
| Encoding 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
| -
|-
| Encoding 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/spatial
|-
| Name
| spatial
|-
| Label
| Place
|-
| Defined by:
| -
|-
| DC Definition
| Spatial characteristics of the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Place of an event.
|-
| eSciDoc Comment
|
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/coverage
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
|
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: 1
|-
| Best practice
| -
|-
| Open Questions
| As "spatial" refines "coverage" its usage for a location can be debated
|}
 
 
 
{| 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
| -
|-
| Encoding 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
|}


== References ==
== References ==
Line 2,744: Line 276:




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

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"