| width="80px" | '''Time'''
| width="800px" | 13:30 until 1415:3000
|- valign="top"
| width="800px" |
* 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 [[:Image:Search.png | mockup]]. The return values should be a collection containing type, uid, overview information and a REST url. With this information, the application should be able to build a new page with the proper url and retrieve the data with the help of the REST url.
** The [[Application_Programming_Interface_(API)#REST_API_documentation | REST API documentation]] will be split into multiple documents, corresponding with the module names (core, ...).
* Decision JavaScript Framework
* What is missing for the tender?
* Next steps
|-
| width="40px" | 1
| width="800px" | Each resource collection:* Will be updated.| width="70px" | InfoTo Do| width="70px" | AllTMU/MEI
| width="70px" | 2013-12-05
|-
| width="40px" | 2
| width="800px" | Do we return empty values (like shippingAddress) or not?* Empty values are not displayed (all possible vaules must appear in the documentation).| width="70px" | InfoDecision
| width="70px" | All
| width="70px" | 2013-12-05
| width="40px" | 3
| width="800px" | isActive is missing in the current examples. * Will be updated.| width="70px" | InfoTo Do| width="70px" | AllTMU/MEI
| width="70px" | 2013-12-05
|-
| width="40px" | 4
| width="800px" | 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.* The application is responsible for the deletion of the dependencies.
| width="70px" | Info
| width="70px" | All
| width="40px" | 5
| width="800px" | New Functionality in the REST api:* We need a call, the can return either the number of dependencies or directly a list of all the dependencies (resource url).* Will we need a call, that helps the JavaScript Framework to create the breadcrumbs (people, services)?| width="70px" | To Do| width="70px" | TMU/MEI| width="70px" | 2013-12-05|- | width="40px" | 6| width="800px" | Search REST API:* Documentation will be updated to reflect the changes.| width="70px" | To Do| width="70px" | TMU/MEI| width="70px" | 2013-12-05|- | width="40px" | 7| width="800px" | The REST API documentation will be split:* Reseller and Customer and People are more or less the same.* The difference is in the mapping.| width="70px" | To Do| width="70px" | TMU/MEI| width="70px" | 2013-12-05|- | width="40px" | 8| width="800px" | The REST API documentation will be extended:* Mapping table.* Mandatory/optional table.| width="70px" | To Do| width="70px" | TMU/MEI| width="70px" | 2013-12-05|- | width="40px" | 9| width="800px" | Decision JavaScript Framework:* AngularJS.| width="70px" | Decision| width="70px" | All| width="70px" | 2013-12-05|- | width="40px" | 10| width="800px" | What is missing for the tender?* Extent 1:** REST api stoney core** REST api stoney core test** Frontend: Reseller* Extent 2:** Frontend: Customer, People* Extent 3:** REST api stoney vm** REST api stoney test** Frontend: vm's
| width="70px" | Info
| width="70px" | All
| width="70px" | 2013-12-05
|-
| width="40px" | 11
| width="800px" | Test Environment:
* Test Data will be delivered by SST
* SST can deliver a complete VM (including Web Server and LDAP Server)
| width="70px" | Info
| width="70px" | All
| width="70px" | 2013-12-05
|-
| width="40px" | 12
| width="800px" | Testing Tools?
* On multiple Levels
** PHP Unit Tests (really necessary? will we gain anything?)
** REST API Tests (Postman?, SoapUI?)
** Web Interface Tests (Selenium?)
| width="70px" | To Do
| width="70px" | All
| width="70px" | 2013-12-11
|-
| width="40px" | 13
| width="800px" | Next steps:
* Finalize specification.
| width="70px" | To Do
| width="70px" | TMU/CAF/MEI
| width="70px" | 2013-12-11
|-
| width="40px" | 14
| width="800px" | Mockups:
* We talked about a third button in the listing views, which would give us more functionality (was discussed in Munich).
| width="70px" | To Do
| width="70px" | MEI
| width="70px" | 2013-12-11
|-
| width="40px" | 15
| width="800px" | Tender for Extent 1
| width="70px" | To Do
| width="70px" | CWI
| width="70px" | 2013-12-16
|-
|}
[[Category:2013]]