Minutes from today meeting

31 Jan 2017

- Alex made some progress on the demonstrator. Alex will get the
demonstrator nearly done in the next month
- Alternative implementation from Frederik, can share some code with
Alex implementation
- Both implementations will have different backends (Redis, Triple Store)
- maxDepth:
- default will be 0
- maxDepth: will be property on the service level
- appendsToEnd: is the collection a stack or a queue
- it is possible to add an element at any place in the list (adding in
the middle)
- item matching: differentiation between data property and functions on them
- roles: makes sense to have, but difficult to set a default
- properties are making up models like set, array etc.
- left over for the next session: Future extensions
- first draft of a text should be available at next plenary
Dr. Thomas Zastrow
Max Planck Computing and Data Facility (MPCDF)
Gießenbachstr. 2, D-85748 Garching bei München, Germany
Tel +49-89-3299-1457

  • Frederik Baumgardt's picture

    Author: Frederik Baumgardt

    Date: 31 Jan, 2017

    Thank you, Thomas! Adding two more bullet points:
    - We figured out that maxDepth is actually relevant to both Service and Collection:
    - In a service it describes constraints on the traversal operations
    - A default here might be 0 => no server-side traversal
    - In a collection it describes constraints on the data structure
    - A default value here might be -1 => no limits on recursiveness
    - In discussing the ‘role’ mapping there were different opinions about its generality and complexity:
    - we may want to leave out the default value
    - thus role becomes a simple and general tagging mechanism
    - implementation requirements would be similar to index/dateAdded
    - things like default values and controlled vocabulary would be left to the client
    Next meeting is February 14th. See you there,

    Frederik Baumgardt
    Data & Software Engineer
    Perseids Project, Dept. of Classics
    Tufts University

submit a comment