ESciDoc Committer Meeting 2010-04-27
Date: 27.04.2010 Start time: 15:15
Location: Karlsruhe, München phone: +49-89-38602-223
Participants MPDL: Natasa Bulatovic, Michael Franke
Participants FIZ: Dr. Michael Hoppe, Frank Schwichtenberg, Steffen Wagner, Matthias Razum, Harald Kappus
Previous committer meeting
Next committer meetings
Topics[edit]
Version History[edit]
- resource identifier types see discussion on identifier types
- user defined comments in versions
- discuss proposal where/how to set the version comment
- See PREMIS2 Version history specification and related discussion
This is about a type and a value of the idenfifier for "linkingAgent" (the user that triggers the event), linkingObject (the object the event ocured for), and the event itself.
For agent and object we see two possibilities:
- type: escidoc system identifier (a URI should be found), value: 'escidoc:123'
- type: URL, value: '/ir/item/escidoc:123'
Remarks: Case 1 will not fullfil the premis requirement designation of the domain in which the [...] identifier is unique except the identifier type identifies the specific installation/instance of the eSciDoc Infrastructure. For case 2 a base URI must be provided or the value must be an absolute URI instead of an absolute-path and the URI may change in the authority part by configuration of the eSciDoc Infrastructure (cf. RFC 2396, 3. URI Syntactic Components, 5. Relative URI References).
For the event identifier type and value there is the possibility to use the XML ID of the event (xpath: premis:event/@xmlID) or to create a PID when writing a new event. The latter seems to be to much effort for that case. Frank 14:39, 15 April 2010 (UTC)
Version history proposal[edit]
- maybe go back again to the definitions --Natasa 10:39, 27 April 2010 (UTC)
- The proposal below seems to be adressed - at least partly - at discussion on identifier types. Frank 12:53, 27 April 2010 (UTC)
- A LinkingAgentIdentifierType - a designation of the domain in which linkingAgentidentifier is unique (value should be taken from Controlled Vocabulary)
- A LinkingObjectIdentifierType - a designation of the domain in which linkingObjectidentifier is unique (value should be taken from Controlled Vocabulary)
Now, the point was what kind of identifier types do we have? If a value should be taken from a controlled vocabulary, that would mean that the eSciDoc can define these values. An example:
- linking Agent Identifier Type may be specified similar like event types via PURL (see http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Version_History_Event_Type), for example:
Identifier types and values for Objects and Agents (rather than "escidoc:internal" as it is at present)
- http://purl.org/escidoc/infrastructure/identifier-type/user
- http://purl.org/escidoc/infrastructure/identifier-type/resource, or - see below
- (according to the definition of the domain in which linking object identifier is unique all are valid, the last three are actually different subsets)
- values are actual values of the identifiers
In the description of these identifier types one can describe the semantics of the identifier type.
Identifier types and values for Events
- Identifier type can be same as xsd:dateTime
- idenitfier value can be a timestamp
Stable release 1.2[edit]
- information, input from both teams
others[edit]
- eSciDoc-Colab Page setup
- Alignment of tools and processes (e.g., Maven)
- Improved and harmonized communication of eSciDoc
- eSciDoc Blog
- service names and classification
- documentation of services
- installation guides
- eSciDoc Lab: Colab page gathering experimental modules
- Exchange of staff members for specific developments or share development