Talk:ESciDoc Version History Event Type

In respect to the premis examples:

create -> creation
update -> modification

How detailed?
- e.g. just an eventType for update or seperate ones for updateProperties, updateMdRecords, etc.
  - Possibly misleading: calling update may just modify Properties which is an equivalent operation to updateProperties. Frank 10:09, 2 February 2010 (UTC)
  - From TelCo: Maybe necessary to track exactly which service method was called.
- Differentiate between resources (updateItem, updateContainer, etc.)?
  - Unnecessary because the event is related to an Item or Container or ... Semantically no difference (e.g. resource is updated). But the range of what is possibly modified changes. What actually changes is not tracked even when differentiate resource-type. Just blows up the list of eventTypes. Frank 09:54, 2 February 2010 (UTC)
    - Agreed on TelCo.
Create an informal list of eventTypes.
- MPDL proposes to list the service methods.
  - See below. Frank 09:56, 2 February 2010 (UTC)
Strings or URIs?
- How to publish the vocabulary?
- From TelCo: URI seems to be good; can be escidoc PURL managed by MPDL.
How and when implemented?

A decision should be made next Committer Meeting.

All available service methods modifying a resource:

create
delete (?)
update
submit
release
revise
withdraw
assignObjectPid
assignVersionPid
assignContentPid
lock
unlock

What about (possibly) future methods modifying sub-resources? E.g.:

createComponent
createMdRecord
updateComponent
updateMdRecord
moveToContext

Navigation menu