[unchecked revision]

Revision as of 15:03, 27 November 2013

Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH

Location	Skype
Date	Wednesday, the 27th of November 2013
Time	14:00 until 15:00
Participants	Christian Wittkowski <christian.wittkowski@devroom.de>: CWI Christian Affolter <christian.affolter@stepping-stone.ch>: CAF Tiziano Müller <tiziano.mueller@stepping-stone.ch>: TMU Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
Non participants	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	Decision REST API RestFullYii? Own development? Other projects/links: http://www.yiiframework.com/wiki/175/how-to-create-a-rest-api/ https://github.com/paysio/yii-rest-api Mapping of attributes Collections (lists)

No.	Text	What?	Who?	When?
1	We have decided on our own development. Please have a look at https://github.com/paysio/yii-rest-api as an example. They have implemented REST in the proper way, including http auth. If you want to, build upon the example.	Info	All	2013-11-27
2	We'll update the Application Programming Interface (API) and mark the mandatory requirements. The documentation will be split into multiple documents. We'll finalize the specification until Wednesday evening, the 4th of December 2013. We should have a conference call on Thursday afternoon, the 5th of December 2013.	To Do	CAF/TMU/MEI	2013-12-05
3	Mapping of attributes: The API objects will be defined manually for each resource type. The mapping will be human readable. The mapping will be finalized together with the Application Programming Interface (API) specification. We want to encapsulate the LDAP and want to be able to collect multiple leafs into one object.	Info	All	2013-12-04
4	Collections (lists): A default set of return values is defined by the specification. Per collection resource a default collation is defined by the specification, see Filtering, sorting and searching Optional: In a later stage, the desired attributes can be requested via query parameter.	Info	All	2013-11-27
5		Info	All	2013-11-27

@@ Line 77: / Line 77: @@
 | width="40px"   | 3
-| width="800px"  |
+| width="800px"  | Mapping of attributes:
+* The API objects will be defined manually for each resource type.
+* The mapping will be human readable.
+* The mapping will be finalized together with the [[Application Programming Interface (API)]] specification.
+* We want to encapsulate the LDAP and want to be able to collect multiple leafs into one object.
 | width="70px"   | Info
 | width="70px"   | All
-| width="70px"   | 2013-11-27
+| width="70px"   | 2013-12-04
 |-
 | width="40px"   | 4
-| width="800px"  |
+| width="800px"  | Collections (lists):
+* A default set of return values is defined by the specification.
+* Per collection resource a default collation is defined by the specification, see [[Application_Programming_Interface_(API)#Filtering.2C_sorting_and_searching |  Filtering, sorting and searching]]
+* Optional: In a later stage, the desired attributes can be requested via query parameter.
 | width="70px"   | Info
 | width="70px"   | All
@@ Line 98: / Line 105: @@
 |}
 [[Category:2013]]