{"action":"created","issue":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/915","repository_url":"https://api.github.com/repos/schemaorg/schemaorg","labels_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/915/labels{/name}","comments_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/915/comments","events_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/915/events","html_url":"https://github.com/schemaorg/schemaorg/issues/915","id":120284992,"number":915,"title":"Vocabulary for hotels, vacation homes, camping sites, etc.","user":{"login":"mfhepp","id":671238,"avatar_url":"https://avatars.githubusercontent.com/u/671238?v=3","gravatar_id":"","url":"https://api.github.com/users/mfhepp","html_url":"https://github.com/mfhepp","followers_url":"https://api.github.com/users/mfhepp/followers","following_url":"https://api.github.com/users/mfhepp/following{/other_user}","gists_url":"https://api.github.com/users/mfhepp/gists{/gist_id}","starred_url":"https://api.github.com/users/mfhepp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mfhepp/subscriptions","organizations_url":"https://api.github.com/users/mfhepp/orgs","repos_url":"https://api.github.com/users/mfhepp/repos","events_url":"https://api.github.com/users/mfhepp/events{/privacy}","received_events_url":"https://api.github.com/users/mfhepp/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2015-12-03T22:26:19Z","updated_at":"2016-04-04T17:11:06Z","closed_at":null,"body":"We need a vocabulary for expressing hotel information, namely about the lodging business, room categories, and rates."},"comment":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/comments/205398189","html_url":"https://github.com/schemaorg/schemaorg/issues/915#issuecomment-205398189","issue_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/915","id":205398189,"user":{"login":"danbri","id":170265,"avatar_url":"https://avatars.githubusercontent.com/u/170265?v=3","gravatar_id":"","url":"https://api.github.com/users/danbri","html_url":"https://github.com/danbri","followers_url":"https://api.github.com/users/danbri/followers","following_url":"https://api.github.com/users/danbri/following{/other_user}","gists_url":"https://api.github.com/users/danbri/gists{/gist_id}","starred_url":"https://api.github.com/users/danbri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danbri/subscriptions","organizations_url":"https://api.github.com/users/danbri/orgs","repos_url":"https://api.github.com/users/danbri/repos","events_url":"https://api.github.com/users/danbri/events{/privacy}","received_events_url":"https://api.github.com/users/danbri/received_events","type":"User","site_admin":false},"created_at":"2016-04-04T17:11:06Z","updated_at":"2016-04-04T17:11:06Z","body":"@mfhepp - would it make sense to ship sdo-deimos as v2.3 and continue with this for the next release? \r\n\r\nI would like to get our release cycle back down to 6 weeks or less. Longer cycles end up in a self-fulfilling dynamic where we delay to include things (like this) and the \"risk of missing the window\" feels bigger because of concern that the next release will be similarly delayed. How close are we here to getting #915 closed and fully implemented?"}}