Difference between revisions of "ESciDoc Application Profiles"

From MPDLMediaWiki
Jump to navigation Jump to search
(Moved the publication describing content to a separate page: ESciDoc_Application_Profile_Publication)
Line 7: Line 7:
== Application Profile ==  
== 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.
The eSciDoc Application Profiles (AP) document 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.


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.
In the first step, the APs are meant for documenting the existing xml schemas only. These documents should be the basis for all future communication about the metadata profiles in use, e.g. PubMan. 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>
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"
== eSciDoc Application Profiles ==
|width="100pt"| Term URI
* [[ESciDoc_Application_Profile_Publication]]
|width="500pt"| http://purl.org/dc/terms/
* [[ESciDoc_Application_Profile_Person]]
|-
| 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/rslp/terms
|-
| Name
| rslp:
|-
| Label
| Research Support Libraries Programme
|}
 
<br />
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/escidoc/metadata/terms
|-
| Name
| escidoc:
|-
| Label
| eSciDoc terms
|}
 
 
 
 
 
----
 
 
===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
|-
| 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://purl.org/dc/terms/alternative
|-
| Name
| alternative
|-
| Label
| Alternative Title
|-
| Defined by:
| -
|-
| DC Definition
| An alternative name for the resource.
|-
| DC Comment
| The distinction between titles and alternative titles is application-specific.
|-
| eSciDoc Definition
| -
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| http://purl.org/dc/terms/title
|-
| 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/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<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
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
|http://purl.org/escidoc/metadata/terms/types/ [[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
|}
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/language
|-
| Name
| language
|-
| Label
| Language
|-
| Defined by:
| -
|-
| DC 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
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| RFC 4646
|-
| 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/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
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| ISBN, ISSN, DOI, arXiv, ...
|-
| 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/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
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
|
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 1; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| Author, which we want to use dc:creator for, is also defined as a MARCREL (see refinements below), but then as a refinement from dc:contributor.<br />
Painter does not exist as MARCREL.
|}
 
 
Example: http://schemas.library.nhs.uk/Term/DC/contributor.html
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/contributor
|-
| Name
| contributor
|-
| Label
| Contributor
|-
| 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: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:ART] Artist
http://www.loc.gov/loc.terms/relators/ART
|-
| Refined by
| [marcrel:PHT] Photographer
http://www.loc.gov/loc.terms/relators/PHT
|-
| Refined by
| [marcrel:CMM] Commentator
http://www.loc.gov/loc.terms/relators/CMM
|-
| Refined by
| [marcrel:TRC] Transcriber
http://www.loc.gov/loc.terms/relators/TRC
|-
| Refined by
| [marcrel:TRL] Translator
http://www.loc.gov/loc.terms/relators/TRL
|-
| Refined by
| [marcrel:SAD] Scientific Advisor
http://www.loc.gov/loc.terms/relators/SAD
|-
| Refined by
| [marcrel:TRL] Contributor
http://www.loc.gov/loc.terms/relators/CTB
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Mandatory
|-
| Condition
| -
|-
| Datatype
| string
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| Shall we add eSciDoc relators "Archivist", "Preservator","Referee" ?
|}
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/escidoc/metadata/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/escidoc/metadata/terms/issuedonline
|-
| Name
| issuedonline
|-
| Label
| Date Issued Online
|-
| Defined by:
| -
|-
| DC Definition
| -
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Date of online publication of the item.
|-
| 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://purl.org/escidoc/metadata/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://purl.org/escidoc/metadata/terms/event
|-
| Name
| event
|-
| Label
| Event
|-
| Defined by:
| -
|-
| DC Definition
| -
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Some items are related to an event, e.g. a conference or a lecture series.
|-
| eSciDoc Comment
| -
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| Encoding Scheme For
| -
|-
| Has Encoding Scheme
| -
|-
| Obligation
| Optional
|-
| Condition
| -
|-
| Datatype
| -
|-
| Occurrence
| Min: 0; Max: Unbounded;
|-
| Best practice
| -
|-
| Open Questions
| C-DOC CRM standard event element?
|}
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/escidoc/metadata/terms/academicdegree
|-
| Name
| academicdegree
|-
| Label
| Academic Degree
|-
| Defined by:
| -
|-
| DC Definition
| -
|-
| DC Comment
| -
|-
| eSciDoc Definition
| The type of academic degree earned by writing the resource.
|-
| eSciDoc Comment
| List contains: master, diploma, magister, staatsexamen, phd, habilitation
|-
| Type of term
| Property
|-
| Refines
| -
|-
| Refined by
| -
|-
| 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
|}
 
 
 
 
 
{| border="1"
|width="100pt"| Term URI
|width="500pt"| http://purl.org/dc/terms/abstract
|-
| Name
| abstract
|-
| Label
| Abstract
|-
| Defined by:
| -
|-
| DC Definition
| A summary of the resource.
|-
| DC Comment
| -
|-
| eSciDoc Definition
| Abstract or short description of 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: 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:
| -
|-
| 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
| Which subject classification scheme are we following? LCC, DDC,...?
|}
 
 
 
 
{| 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://purl.org/dc/terms/Location
|-
| Name
| location
|-
| Label
| Location
|-
| Defined by:
|
|-
| DC Definition
| A spatial region or named place.
|-
| 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
| -
|}
 
== Related eSciDoc Application Profiles ==
* [[ESciDoc_Application_Profile_Organization]]
* [[ESciDoc_Application_Profile_Organization]]
* [[ESciDoc_Application_Profile_Event]]
* [[ESciDoc_Application_Profile_Event]]
* [[ESciDoc_Application_Profile_Person]]
* [[ESciDoc_Application_Profile_File]]
* [[ESciDoc_Application_Profile_File]]


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


== References ==
== References ==

Revision as of 09:52, 4 April 2008

  • work in progress

Open issues[edit]

I moved the open issues to the discussion page -- Andreas Gros 08:19, 20 March 2008 (CET)


Application Profile[edit]

The eSciDoc Application Profiles (AP) document 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.

In the first step, the APs are meant for documenting the existing xml schemas only. These documents should be the basis for all future communication about the metadata profiles in use, e.g. PubMan. 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[1]


eSciDoc Application Profiles[edit]

Related eSciDoc Encoding Schemes[edit]



References[edit]

  1. ↑ CWA14855: Dublin Core Application Profile guidelines, see http://www.cen.eu/cenorm/businessdomains/businessdomains/isss/cwa/cwa14855.asp

Central European Time

Enhanced Scientific Documentation

Application Profile

Publication Management

Comitée européen de normalisation

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