To describe metadata provenance, all of Dublin Core can be used as long as descriptions are part of an annotation set. On this page, we collect properties that we would like to highlight in the application profile. Rationale for them can be found in Use Cases. In the final draft, we will define several levels of compliance in order to establish a baseline interoperability or harmonization of metadata provenance annotation sets.
| Requirement | Existing Classes | Definition | Notes | Use Cases | Discussion Summary |
|---|---|---|---|---|---|
| C1: Annotation Set | — | An aggregation of statements about the provenance of description sets |
| Requirement | Existing Properties | Definition | Property Range | Notes | Use Cases | Discussion Summary |
|---|---|---|---|---|---|---|
| P1: Data creator | dct:creator | Creator of the description set / data contained in the description set (?) | Person or process | Could range be just something like opm:agent? | ||
| P2: Issue date | — | Date of formal issuance of the data | dateTime | Not sure if we need a more concrete publication property here, or a more differentiated view with several dates (see Atom dates discussion) | ||
| P3: Expiration | — | Indicates the age when the description set is considered to go stale and should be refreshed / no longer be cached | Duration or dateTime | Expiration could be given as an offset/duration) based on an issue dateTime (“P120D”, the data goes stale after 120 days from the issue date), or as a concrete dateTime. | ||
| P4: Publisher | dc:publisher | Publisher of the description set/data described by the annotation set | Entity responsible for publication | Knowing if the publisher of the data is the same entity as the one who created might be useful in some cases (authority of the data) |
References: [http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings#Mappings link]