Difference between revisions of "2014-02-12 Telephone Conference DEVROOM / stepping stone GmbH"

From stoney cloud
Jump to: navigation, search
[unchecked revision][unchecked revision]
(Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH)
(Transcript)
Line 57: Line 57:
  
 
| width="40px"  | 1
 
| width="40px"  | 1
| width="800px"  | No location attribute used.
+
| width="800px"  | In principal, the REST API should know the scope of variables. For example: billingAddress should be able to contain location. No location attribute is currently used, but it could be used in the future.
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 65: Line 65:
  
 
| width="40px"  | 1
 
| width="40px"  | 1
| width="800px"  |  
+
| width="800px"  | q and sort are GET parameters and have got nothing to do with the JSON payload. Therefore we don't see a current of future issue.
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All

Revision as of 10:28, 12 February 2014

Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH

Location Skype
Date Wednesday, the 12th of Feburary 2014
Time 11:30 until 12: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
  • David Vollmer <david.vollmer@stepping-stone.ch>: DVO
  • Pascal Jufer <pascal.jufer@stepping-stone.ch>: PJU
Agenda

Open Questions:

Transcript

No. Text What? Who? When?
1 In principal, the REST API should know the scope of variables. For example: billingAddress should be able to contain location. No location attribute is currently used, but it could be used in the future. Info All 2014-02-12
1 q and sort are GET parameters and have got nothing to do with the JSON payload. Therefore we don't see a current of future issue. Info All 2014-02-12
1 Info All 2014-02-12
1 Info All 2014-02-12
1 Info All 2014-02-12