application_profile
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| application_profile [2011/05/17 20:27] – [Mapping to other terms/vocabularies] daniel | application_profile [2011/08/24 06:35] (current) – [Usage guidelines] daniel | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | Based on the Libraries AP: http:// | ||
| + | |||
| ====== Objectives and scope ====== | ====== Objectives and scope ====== | ||
| Line 10: | Line 12: | ||
| * Users: who want to distinguish from the provenance published by several sources and analyze it. | * Users: who want to distinguish from the provenance published by several sources and analyze it. | ||
| ====== Functional Requirements ====== | ====== Functional Requirements ====== | ||
| + | Base the examples in http:// | ||
| ====== Entity-Relational Model ====== | ====== Entity-Relational Model ====== | ||
| Summarize the work done in | Summarize the work done in | ||
| Line 21: | Line 24: | ||
| In the future we wil have to write down the relation between the domain model and the PIL. | In the future we wil have to write down the relation between the domain model and the PIL. | ||
| ====== Usage guidelines ====== | ====== 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 ====== | ====== Encoding syntax guidelines ====== | ||
| + | (This is optional) TBD | ||
| ====== Examples ====== | ====== Examples ====== | ||
| + | Either summarize/ | ||
application_profile.1305664038.txt.gz · Last modified: 2011/05/17 20:27 by daniel