{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/wot-thing-description/issues/108","repository_url":"https://api.github.com/repos/w3c/wot-thing-description","labels_url":"https://api.github.com/repos/w3c/wot-thing-description/issues/108/labels{/name}","comments_url":"https://api.github.com/repos/w3c/wot-thing-description/issues/108/comments","events_url":"https://api.github.com/repos/w3c/wot-thing-description/issues/108/events","html_url":"https://github.com/w3c/wot-thing-description/issues/108","id":303807334,"number":108,"title":"Simplified TD: forms","user":{"login":"mkovatsc","id":664090,"avatar_url":"https://avatars0.githubusercontent.com/u/664090?v=4","gravatar_id":"","url":"https://api.github.com/users/mkovatsc","html_url":"https://github.com/mkovatsc","followers_url":"https://api.github.com/users/mkovatsc/followers","following_url":"https://api.github.com/users/mkovatsc/following{/other_user}","gists_url":"https://api.github.com/users/mkovatsc/gists{/gist_id}","starred_url":"https://api.github.com/users/mkovatsc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mkovatsc/subscriptions","organizations_url":"https://api.github.com/users/mkovatsc/orgs","repos_url":"https://api.github.com/users/mkovatsc/repos","events_url":"https://api.github.com/users/mkovatsc/events{/privacy}","received_events_url":"https://api.github.com/users/mkovatsc/received_events","type":"User","site_admin":false},"labels":[{"id":822538614,"url":"https://api.github.com/repos/w3c/wot-thing-description/labels/JSON","name":"JSON","color":"e86e22","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-03-09T11:15:23Z","updated_at":"2018-03-16T10:58:47Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Moderated focused discussion on the [Simplified TD proposal](https://w3c.github.io/wot-thing-description/proposals/simplified-td/) and `forms`. Please stay on topic and use https://github.com/w3c/wot/issues/393 for any general remarks.\r\n\r\nIn https://github.com/w3c/wot/issues/393 @benfrancis wrote:\r\n\r\n> * `\"rel\": [\"get\", \"set\"]` does not match my understanding of how link relations are intended to be used. They are supposed to \"describe how the current context is related to another resource\", not what protocol methods can be used with that resource.\r\n> * `http:SubProtocol` also feels like a bit of a hack\r\n> * As discussed in the meeting, I'm still not convinced by this use of \"forms\" as a generic mechanism for declaratively defining protocol bindings to any protocol inside a Thing Description. I think we should continue to incubate an alternative approach (inside the Interest Group) of using concrete protocol binding specifications for a small number of web protocols.\r\n> * If multiple links are needed for the same capability, an array of link relations could be used (`\"rel\":\"self\"` could be omitted and assumed as a default, but is included here to show a more common use of a link relation):\r\n```\r\n    \"level\" : {\r\n      \"name\": \"Level\",\r\n      \"@type\": \"LevelProperty\",\r\n      \"schema\": {\r\n        \"type\": \"number\",\r\n        \"minimum\": 0,\r\n        \"maximum\": 100\r\n      }      \r\n      \"links\" : [\r\n          {\r\n            \"rel\": \"self\",\r\n            \"href\": \"/things/lamp/properties/level\",\r\n            \"mediaType\": \"application/json\"\r\n          },\r\n          {\r\n            \"rel\": \"self\",\r\n            \"href\": \"coap://things.com/things/lamp/properties/level\",\r\n            \"mediaType\": \"application/cbor\"\r\n          }\r\n        ]\r\n      }\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/wot-thing-description/issues/comments/373679488","html_url":"https://github.com/w3c/wot-thing-description/issues/108#issuecomment-373679488","issue_url":"https://api.github.com/repos/w3c/wot-thing-description/issues/108","id":373679488,"user":{"login":"benfrancis","id":552417,"avatar_url":"https://avatars3.githubusercontent.com/u/552417?v=4","gravatar_id":"","url":"https://api.github.com/users/benfrancis","html_url":"https://github.com/benfrancis","followers_url":"https://api.github.com/users/benfrancis/followers","following_url":"https://api.github.com/users/benfrancis/following{/other_user}","gists_url":"https://api.github.com/users/benfrancis/gists{/gist_id}","starred_url":"https://api.github.com/users/benfrancis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benfrancis/subscriptions","organizations_url":"https://api.github.com/users/benfrancis/orgs","repos_url":"https://api.github.com/users/benfrancis/repos","events_url":"https://api.github.com/users/benfrancis/events{/privacy}","received_events_url":"https://api.github.com/users/benfrancis/received_events","type":"User","site_admin":false},"created_at":"2018-03-16T10:58:47Z","updated_at":"2018-03-16T10:58:47Z","author_association":"NONE","body":"@mkovatsc \r\n> The subProtocol is closing a gap in current links and forms. There is no way to express sub-protocols such as long-poll or SSE; today this is always hard-wired into the application, which is not applicable when you do not own and control both sides of the communication (cf. WebSocket purpose and problem for interoperability).\r\n\r\nQuick note: WebSockets do have a mechanism for negotiating a sub-protocol to use https://tools.ietf.org/html/rfc6455#page-12"}}
{"actor":{"display_login":"benfrancis"}}