Differences

This shows you the differences between two versions of the page.

--- vocabulary [2011/01/12 16:59] – kai
+++ vocabulary [2011/11/02 20:44] (current) – [Properties] daniel
@@ Line 1: / Line 1: @@
-====== Vocabulary ======
+====== Provenance Metadata Element Set ======
+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.
+==== Classes ====
+^ Requirement ^ Existing Classes ^ Definition ^ Notes ^ Use Cases ^ Discussion Summary ^
+| **C1:** Annotation Set  | --- | An aggregation of statements about the provenance of description sets  |          |   |      |
+==== Properties ====
+^ 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)  | | |
-The basic vocabulary is just Dublin Core (Proposal, please tell us your concerns, if you have any). On this page, we collect properties that could be additionally integrated in the application profile. Rationale for them can be found in [[Use Cases]].
    * dcprov:creationType (automatically,intellectual) (from UC Automatic Indexing)
    * dcprov:weight (confidence value, rank, ... for automatic systems) (from UC Automatic Indexing)
+   * (Proposed) License: to refer to the licensing of the description set.
+   * **Properties from Web of Trust Vocabulary (WOT)**:
+        * wot:signer: A property linking a public key signature event to the public key that was used to sign
+        * wot:sigDate: The date of a public key signature event. May be useful to determine if the provenance metadata assertions have expired or not (imagine that they are vallid but just for a period of time).
+        * wot:hasKey: Property to link a user to a PGP/GPG public key for describing him.
+   * **Properties from PREMIS vocabulary (designed for long term preservation)**:
+        * signature: PREMIS allows describing the signature an object is signed with.
+        * signatureEncoding: The encoding used for the values of signatureValue, keyInformation. E.g. Base64
+        * signer: The individual, institution, or authority (Agent) responsible for generating the signature. Could also be carried in keyInformation.
+        * signatureMethod: A designation for the encryption and hash algorithms used for signature generation. E.g. DSA-SHA1
+        * signatureValue: a value generated from the application of a private key to a message digest.
+        * keyInformation: Information about the signer’s public key needed to validate the digital signature.
+   * **Properties from PML:**
+        * pmlj:hasInferenceEngine useful to determine who was responsible for the creation of the metadata.
+   * **Properties from SWAN**
+        * previousVersion: similar to the dcterms: isVersionOf. Useful to determine if 2 sets of metadata statements are version of another set.
+        * createdBy: similar to dc:creator.
+        * contributors: similar to dc:contributor.
+        * publishedBy: similar to dc:publisher
+        * submittedBy: responsible for the submission of the set of provenance statements.
+        * authoredBy: similar to creator.
+        * curatedBy: very important and relevant to trust. A conflict between a set of provenance statements about a resource may be resolved because of the curator.
+   * **Properties from Changeset:**
+        * cs:createdDate: similar to dc:date (or issue date)
+        * cs:creatorName: similar to dc:creator.
+   * **Properties from the Semantic Web Publishing Vocabulary (SWP):**
+        * swp:signature: similar to the wot:hasKey property. Can be used for authentification.
+        * swp:signatureMethod: equal to the premis:signatureMethod
+        * swp:certificate: similar to the premis: certificate.
+        * swp:assertedBy : similar to dc:creator.
+References: [http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings#Mappings link]