No.
|
Text
|
What?
|
Who?
|
When?
|
---|
1
|
We have decided on our own development.
Questions:
- MIT Licence a problem for us?
|
To Do
|
CWI
|
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.
|
To Do
|
CAF/TMU/MEI
|
2013-12-05
|
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
|
Development:
- Please check in all code daily (more often is allowed).
- The code does not need to function, it is important, that it is there and can be reviewed.
|
Info
|
All
|
2013-11-27
|
6
|
Specification:
- Each form is first displayed as an empty form via JavaScript and then filled out with the next JavaScript call.
- Could for certain cases PHP calls used to fill the forms directly (internally)?
- Or should we phase out the PHP calls step for step?
|
Info
|
CWI
|
2013-11-27
|
7
|
Core / Modules:
- The stoney core contains the base functionality.
- The URL contains the module name and then the version:
|
Info
|
All
|
2013-11-27
|
7
|
|
Info
|
All
|
2013-11-27
|