Differences

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

--- application_profile [2011/05/17 19:37] – created daniel
+++ application_profile [2011/08/24 06:35] (current) – [Usage guidelines] daniel
@@ Line 1: / Line 1: @@
-====== Application profile ======
+Based on the Libraries AP: http://dublincore.org/librarieswiki/RevisionDraft
+====== Objectives and scope ======
+The main objectives of this application profile are:
+  * Provide the means to represent meta(meta-*)data provenance.
+  * Provide the means to distinguish between provenance information and metadata provenance.
+  * Simple solution and easy to adopt
+====== Target users ======
+The main users for this application profile will be:
+  * Content providers: Who publish provenance information and want to attach additional provenance metadata for it.
+  * Users: who want to distinguish from the provenance published by several sources and analyze it.
+====== Functional Requirements ======
+Base the examples in http://dublincore.org/librarieswiki/FunctionalRequirements
+====== Entity-Relational Model ======
+Summarize the work done in
+http://wiki.bib.uni-mannheim.de/dc-provenance/doku.php?id=domain_model
+Also, update it with the work done in the paper.
+====== Mapping to other terms/vocabularies ======
+Summarize some of the work done in
+http://wiki.bib.uni-mannheim.de/dc-provenance/doku.php?id=use_cases
+along with the updates done in the paper.
+In the future we wil have to write down the relation between the domain model and the PIL.
+====== Usage guidelines ======
+How should a content provider publish metadata provenance with our domain model?
+The Pubby example is a nice starting point: [[UsageGuidelines|Usage Guidelines]]
+====== Encoding syntax guidelines ======
+(This is optional) TBD
+====== Examples ======
+Either summarize/refer to the use cases or point to the rdf example provided by Kai in the paper.