Location
|
Skype
|
Date
|
Thursday, the 5th of December 2013
|
Time
|
13:30 until 14:30
|
Participants
|
- Christian Wittkowski <christian.wittkowski@devroom.de>: CWI
- Tiziano Müller <tiziano.mueller@stepping-stone.ch>: TMU
- Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
|
Non participants
|
- Christian Affolter <christian.affolter@stepping-stone.ch>: CAF
- Pat Kläy <pat.klaey@stepping-stone.ch>: PKL
- Christoph Scheurer <christoph.scheurer@stepping-stone.ch>: CSC
- David Vollmer <david.vollmer@stepping-stone.ch>: DVO
- Pascal Jufer <pascal.jufer@stepping-stone.ch>: PJU
|
Agenda
|
- Approval REST API
- Each resource collection returns additional information like pagination, total and current count. A maximum amount of return values is defined on the server. This value can be lowered by the calling application. The pagination is only mandatory, when the maximum amount of return values is reached.
- Do we return empty values (like shippingAddress) or not?
- isActive is missing in the current examples.
- The logic of the deletion process is currently located on the client side. On the server we only return an error, it the item to be deleted still has dependencies.
- We'll define a search REST API, so that we can return results according to the mockup.
- Decision JavaScript Framework
- What is missing for the tender?
- Next steps
|