{"action":"created","issue":{"url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI/issues/360","repository_url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI","labels_url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI/issues/360/labels{/name}","comments_url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI/issues/360/comments","events_url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI/issues/360/events","html_url":"https://github.com/OpenNetworkingFoundation/TAPI/issues/360","id":366224102,"node_id":"MDU6SXNzdWUzNjYyMjQxMDI=","number":360,"title":"OpenAPI versus RESTCONF/YANG API","user":{"login":"italobusi","id":12461741,"node_id":"MDQ6VXNlcjEyNDYxNzQx","avatar_url":"https://avatars0.githubusercontent.com/u/12461741?v=4","gravatar_id":"","url":"https://api.github.com/users/italobusi","html_url":"https://github.com/italobusi","followers_url":"https://api.github.com/users/italobusi/followers","following_url":"https://api.github.com/users/italobusi/following{/other_user}","gists_url":"https://api.github.com/users/italobusi/gists{/gist_id}","starred_url":"https://api.github.com/users/italobusi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/italobusi/subscriptions","organizations_url":"https://api.github.com/users/italobusi/orgs","repos_url":"https://api.github.com/users/italobusi/repos","events_url":"https://api.github.com/users/italobusi/events{/privacy}","received_events_url":"https://api.github.com/users/italobusi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2018-10-03T08:19:25Z","updated_at":"2018-10-04T16:48:46Z","closed_at":null,"author_association":"NONE","body":"As discussed in previous TAPI calls the relationship between OpenAPI and RESTCONF/YANG APIs is not fully clear: more clarification is needed also to write correct statements in the TAPI 2.1 release note (see open issue #359)"},"comment":{"url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI/issues/comments/427090451","html_url":"https://github.com/OpenNetworkingFoundation/TAPI/issues/360#issuecomment-427090451","issue_url":"https://api.github.com/repos/OpenNetworkingFoundation/TAPI/issues/360","id":427090451,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNzA5MDQ1MQ==","user":{"login":"italobusi","id":12461741,"node_id":"MDQ6VXNlcjEyNDYxNzQx","avatar_url":"https://avatars0.githubusercontent.com/u/12461741?v=4","gravatar_id":"","url":"https://api.github.com/users/italobusi","html_url":"https://github.com/italobusi","followers_url":"https://api.github.com/users/italobusi/followers","following_url":"https://api.github.com/users/italobusi/following{/other_user}","gists_url":"https://api.github.com/users/italobusi/gists{/gist_id}","starred_url":"https://api.github.com/users/italobusi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/italobusi/subscriptions","organizations_url":"https://api.github.com/users/italobusi/orgs","repos_url":"https://api.github.com/users/italobusi/repos","events_url":"https://api.github.com/users/italobusi/events{/privacy}","received_events_url":"https://api.github.com/users/italobusi/received_events","type":"User","site_admin":false},"created_at":"2018-10-04T16:48:45Z","updated_at":"2018-10-04T16:48:45Z","author_association":"NONE","body":"Based on this discussion, I think that a more factual statement would be:\r\n\r\n> Implementations may use any flavor of REST APIs as long as they are based on the released TAPI R2.1 YANG models\r\n> \r\n> For interoperability purposes, Implementation Agreement between concerned parties should explicitly specify which flavor of REST API has to be implemented, such as:\r\n> - Standard RESTCONF protocol (RFC8040)\r\n> - TAPI OAS (OpenAPI spec) released as part of an official TAPI release\r\n> - Any other REST API described as part of the Implementation Agreement\r\n> \r\n\r\nAny concerns with this proposal?"}}
{"actor":{"display_login":"italobusi"}}