Differences

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

--- vocabulary [2011/08/24 05:22] – michael
+++ vocabulary [2011/11/02 20:44] (current) – [Properties] daniel
@@ Line 6: / Line 6: @@
 ^ Requirement ^ Existing Classes ^ Definition ^ Notes ^ Use Cases ^ Discussion Summary ^
-| **C1:** Annotation Set  | -- | An aggregation of statements about the provenance of description sets  |          |   |      |
+| **C1:** Annotation Set  | --- | An aggregation of statements about the provenance of description sets  |          |   |      |
 ==== Properties ====
-^ Requirement      ^ Existing Classes      ^ Definition          ^ Property Range ^ Notes ^  Use Cases  ^  Discussion Summary ^
+^ Requirement ^ Existing Properties ^ Definition ^ Property Range ^ Notes ^ Use Cases ^ Discussion Summary ^
-| **C1:** Annotation Set   | --     | An aggregation of statements about the provenance of description sets  | Row 1 Col 3        | Row 1 Col 3        | Row 1 Col 3  |      Row 1 Col 1 |
+| **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)  | | |
    * 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]