dc-provenance

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Participants ======

Kai, Michael, Ömer

====== Minutes ======

  * [16:07] <kai_> Topic: Domain Model
  * [16:38] <kai_> Action: Michael adapts the model according to our discussion
  * [16:39] <kai_> Description and Statement separated, as in DCAM
  * [16:39] <kai_> Identification of DCAM classes
  * [16:39] <kai_> Cardinality 0..* for description set
  * [16:39] <kai_> ... to description, means, a description can exist without description set
  * [16:40] <kai_> cardinality annotation set annotation stays at 1, means we REQUIRE annotations to be in a set
  * [16:40] <kai_> solutions who can not do that (annotaions in same rdf-xml-file) will probably be allowed but discouraged
  * [16:41] <kai_> Classes: DCAM Description Set, DCAM Description, DCAM Statement, Annotation Set, Annotation
  * [16:41] <kai_> Annotation inherits from Description
  * [16:41] <kai_> Annotation and Drescription aggregate Statements
  * [16:48] <kai_> Action: Michael writes some documentation and sends a mail on the mailing list to announce the model as public draft
  * [16:49] <kai_> Ömer, Michael and Kai agree on the model as current public draft
  * [16:49] <kai_> Topic: OAI-PMH use case
  * [16:49] <kai_> http://wiki.bib.uni-mannheim.de/dc-provenance/doku.php?id=use_cases
  * [16:50] <kai_> Example: http://madoc.bib.uni-mannheim.de/madoc/oai2/oai2.php?verb=ListRecords&metadataPrefix=oai_dc&from=2011-01-01&until=2011-01-20
  * [16:58] <kai_> Action: Kai refines the OAI-PMH example
  * [16:59] <kai_> Topic: OAI-ORE
  * [16:59] <Oemer> https://docs.google.com/document/d/1SgJAwgjqtIOCFdB7VDxtQo0nHEoZghBq3RLpKWDzGFc/edit?hl=en&pli=1#
  * [17:00] <Oemer> https://docs.google.com/document/d/1SgJAwgjqtIOCFdB7VDxtQo0nHEoZghBq3RLpKWDzGFc/edit?hl=en&authkey=CPPK6vIF
  * [17:26] <kai_> Action: Ömer searches for an example for ORE and provenance