{"action":"closed","issue":{"url":"https://api.github.com/repos/ocpi/ocpi/issues/51","repository_url":"https://api.github.com/repos/ocpi/ocpi","labels_url":"https://api.github.com/repos/ocpi/ocpi/issues/51/labels{/name}","comments_url":"https://api.github.com/repos/ocpi/ocpi/issues/51/comments","events_url":"https://api.github.com/repos/ocpi/ocpi/issues/51/events","html_url":"https://github.com/ocpi/ocpi/issues/51","id":110455929,"number":51,"title":"Add remote start capability and capability structure","user":{"login":"simonschllng","id":5861026,"avatar_url":"https://avatars.githubusercontent.com/u/5861026?v=3","gravatar_id":"","url":"https://api.github.com/users/simonschllng","html_url":"https://github.com/simonschllng","followers_url":"https://api.github.com/users/simonschllng/followers","following_url":"https://api.github.com/users/simonschllng/following{/other_user}","gists_url":"https://api.github.com/users/simonschllng/gists{/gist_id}","starred_url":"https://api.github.com/users/simonschllng/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonschllng/subscriptions","organizations_url":"https://api.github.com/users/simonschllng/orgs","repos_url":"https://api.github.com/users/simonschllng/repos","events_url":"https://api.github.com/users/simonschllng/events{/privacy}","received_events_url":"https://api.github.com/users/simonschllng/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ocpi/ocpi/labels/2.1","name":"2.1","color":"f7c6c7"},{"url":"https://api.github.com/repos/ocpi/ocpi/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-08T13:51:53Z","updated_at":"2016-03-24T09:21:42Z","closed_at":"2016-03-24T09:21:42Z","body":"The [capability enum](https://github.com/ocpi/ocpi/blob/master/bo_locations_and_evses.md#capability-enum) has two values: `RESERVABLE` and `CHARGING_PROFILE_CAPABLE`. As the capability to remotely start a charging process is very similar, it should be added here.\r\n\r\nEach of these capabilities require to trigger them in the operator backoffice. Therefore a endpoint and a method is required. Thus, the capabilities could be combined with the endpoint information:\r\n\r\n#### Capabilities\r\n| Property  | Type        | Card. | Description                    |\r\n|-----------|-------------|-------|--------------------------------|\r\n| type     | CapabilityType  | 1     | The kind of capability.                               |\r\n| endpoint | Endpoint | ?      | The endpoint to make use of this capability                               |\r\n\r\n##### Example:\r\n\r\n```javascript\r\n{\r\n    //...\r\n    \r\n    \"capabilities\": [\r\n      {\r\n        \"type\": \"RESERVABLE\", \r\n        \"endpoint\": \r\n            {\r\n                \"identifier\": \"reservations\",\r\n                \"url\": \"https://example.com/ocpi/cpo/2.0/reservations/nlelae12345\"\r\n            }\r\n      },\r\n      {\r\n        \"type\": \"REMOTECONTROLABLE\", \r\n        \"endpoint\": \r\n            {\r\n                \"identifier\": \"remotecontrol\",\r\n                \"url\": \"https://example.com/ocpi/cpo/2.0/remotecontrol/nlelae12345\"\r\n            }\r\n      }\r\n    ],\r\n    \r\n    //...\r\n}\r\n```"}}