fixed app profile

docs/literature/application_profile.rst

@@ -4,33 +4,36 @@ Application Profile Overview
 This documentation uses the following namespace abbreviation:
 
 * ``dc``: http://purl.org/dc/elements/1.1/
+* ``datacite``: http://datacite.org/schema/kernel-4
+* ``rdf`` : http://www.w3.org/1999/02/22-rdf-syntax-ns#
+* ``aire``: http://openaire.eu/schema/v4
 
-======================================== ============== =========================================
-OpenAIRE-Field                           OAI-DC Element Refinement by vocabulary
-======================================== ============== =========================================
+======================================== ============================ =========================================
+OpenAIRE-Field                           OAI-DC Element               Refinement by vocabulary
+======================================== ============================ =========================================
 :ref:`dc:title`                          dc:title
-:ref:`dc:creator`                        dc:creator
-:ref:`dc:relation_projectid`             dc:relation    ``info:eu-repo/grantAgreement/``
-:ref:`dc:rights_accesslevel`             dc:rights      ``info:eu-repo/semantics/``
-:ref:`dc:rights_licensecondition`        dc:rights
-:ref:`dc:date_embargo`                   dc:date        ``info:eu-repo/date/embargoEnd/``
-:ref:`dc:relation_alternativeidentfier`  dc:relation    ``info:eu-repo/semantics/altIdentifier/``
-:ref:`dc:relation_publicationreference`  dc:relation    ``info:eu-repo/semantics/reference/``
-:ref:`dc:relation_datasetreference`      dc:relation    ``info:eu-repo/semantics/dataset/``
-:ref:`dc:subject`                        dc:subject
-:ref:`dc:description`                    dc:description
+:ref:`dci:creator`                       datacitec:creator
+:ref:`dci:contributor`                   datacite:contributor         DataCite contributor type
+:ref:`dci:fundingReference`              datacite:fundingReference    DataCite funderIdentifier type
+:ref:`dci:alternativeidentfier`          datacite:alternateIdentifier   
+:ref:`dci:relatedIdentifier`             datacite:relatedIdentifier   DataCite relatedIdentifier type
+:ref:`dci:date_embargo`                  datacite:date                DataCite dateType
+:ref:`dc:language`                       dc:language                  IETF BCP 47, ISO 639-1,2,3
 :ref:`dc:publisher`                      dc:publisher
-:ref:`dc:contributor`                    dc:contributor
 :ref:`dc:date`                           dc:date
-:ref:`dc:type`                           dc:type        ``info:eu-repo/semantics/``
-:ref:`dc:type_publicationversion`        dc:type        ``info:eu-repo/semantics/``
+:ref:`dc:type`                           dc:type                      COAR Resource Type Vocabulary
+:ref:`dc:description`                    dc:description
 :ref:`dc:format`                         dc:format
 :ref:`dc:identifier`                     dc:identfier
+:ref:`dc:rights_accesslevel`             dc:rights                    (COAR)
 :ref:`dc:source`                         dc:source
-:ref:`dc:language`                       dc:language
+:ref:`dc:subject`                        dc:subject
+:ref:`dc:rights_licensecondition`        dc:rights
+:ref:`dc:relation_datasetreference`      dc:relation    
+:ref:`dc:type_publicationversion`        dc:type        
 :ref:`dc:relation`                       dc:relation
 :ref:`dc:coverage`                       dc:coverage
 :ref:`dc:audience`                       dc:audience
-======================================== ============== =========================================
+======================================== ============================ =========================================
 
 

docs/literature/field_creator.rst

@@ -1,6 +1,6 @@
 .. _dci:creator:
 
-2. creator (M)
+2. Creator (M)
 ==============
 
 The authors of the publication in priority order. May be a corporate/institutional or personal name.

docs/literature/field_embargoenddate.rst

@@ -1,35 +1,54 @@
-.. _dc:date_embargo:
+.. _dci:date_embargo:
 
-Embargo End Date (MA)
-^^^^^^^^^^^^^^^^^^^^^
+7. Embargo Period Date (M)
+==========================
 
-DC Field
-~~~~~~~~
-``dc:date``
 
-Usage
-~~~~~
-*Mandatory when applicable*
+DCMI Definition
+~~~~~~~~~~~~~~~
+A date associated with an event in the life cycle of the resource. Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and follows the ``YYYY-MM-DD`` format.
 
 Usage Instruction
 ~~~~~~~~~~~~~~~~~
-When :ref:`dc:rights_accesslevel` is set to
+The date should be formatted according to the W3C encoding rules for dates and times:
+
+**Complete date:**
+
+``YYYY-MM-DD`` (e.g. 1997-07-16)
+
+where:
+
+* ``YYYY`` [four-digit year] is ''mandatory''
+* ``MM`` [two-digit month (01=January, etc.)] is ''optional''
+* ``DD`` [two-digit day of month (01 through 31)] is ''optional''
+
+**One date field – Date of Publication:**
+
+Often repository systems have more then one date fields that serve different purposes. Date of creation, publication, modified, promotion, etc. Unqualified DC is unable to express all these dates, and for the end-user perspective it is confusing to receive more dates from the service provider. The service provider should make a choice what date- field to pick. Preferably in the end-users perspective the most logical and meaningful date will be the date of publication. To reduce the ambiguity of having a number of date fields without qualifiers, we recommend to reduce the number of fields and present the most meaningful date to the service provider. In most cases this is the date of the publication. In other cases this is the date of promotion of a PhD degree.
+
+**No date of publication available:**
+
+If no date of publication is available, use any other date available. It is better to use one date than no date at all.
+
+**Datestamp additions:**
 
-* ``info:eu-repo/semantics/embargoedAccess``
+Additions like “Zulu time” should NOT be part of the metadata.
 
-the end date of the embargo period must be provided. The corresponding term is defined by
+**Fuzzy dates:**
 
-* ``info:eu-repo/date/embargoEnd/<YYYY-MM-DD>``
+For fuzzy dates use a logical year that most represents that period, e.g. ``1650`` instead of ``17th century``.
 
-Encoding of this date should be in the form ``YYYY-MM-DD`` conforming to ISO 8601.
+To express more about that temporal period, one can use the ``dc:coverage`` field. A temporal period can be expressed in a standard way when precisely defined (see :ref:`dc:coverage`) or when “fuzzy” or uncertain by free text expressions. A service provider is able to sort dates based on date standards like W3CDTF. Since there is no standard for fuzzy dates for terms like “Renaissance” or “17th Century”, they will simply not appear on date-based query results.
 
 Since
 ~~~~~
-OpenAIRE Guidelines v1
+DRIVER Guidelines v2
 
 Example
 ~~~~~~~
 .. code-block:: xml
    :linenos:
 
-   <dc:date>info:eu-repo/date/embargoEnd/2015-12-31</dc:date>
+   <dc:date>2000-12-25</dc:date>
+   <dc:date>1978-02</dc:date>
+   <dc:date>1650</dc:date>

docs/literature/index.rst

@@ -23,7 +23,7 @@ OpenAIRE Guidelines for Literature Repositories
    field_projectid
    field_alternativeidentifier
    field_publicationreference
-   field_date
+   field_embargoenddate
    field_language
    field_publisher
    field_publicationdate
@@ -35,7 +35,6 @@ OpenAIRE Guidelines for Literature Repositories
    field_source
    field_subject
    field_licensecondition
-   field_embargoenddate
    field_datasetreference
    field_publicationversion
    field_relation