{"action":"created","issue":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/545","labels_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/545/labels{/name}","comments_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/545/comments","events_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/545/events","html_url":"https://github.com/schemaorg/schemaorg/issues/545","id":80967956,"number":545,"title":"Need a way to express room number in Event location","user":{"login":"vholland","id":4692272,"avatar_url":"https://avatars.githubusercontent.com/u/4692272?v=3","gravatar_id":"","url":"https://api.github.com/users/vholland","html_url":"https://github.com/vholland","followers_url":"https://api.github.com/users/vholland/followers","following_url":"https://api.github.com/users/vholland/following{/other_user}","gists_url":"https://api.github.com/users/vholland/gists{/gist_id}","starred_url":"https://api.github.com/users/vholland/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vholland/subscriptions","organizations_url":"https://api.github.com/users/vholland/orgs","repos_url":"https://api.github.com/users/vholland/repos","events_url":"https://api.github.com/users/vholland/events{/privacy}","received_events_url":"https://api.github.com/users/vholland/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/schemaorg/schemaorg/labels/cluster:%20Date/Time/Event%20and%20opening%20hour%20vocab%20issues","name":"cluster: Date/Time/Event and opening hour vocab issues","color":"fef2c0"},{"url":"https://api.github.com/repos/schemaorg/schemaorg/labels/schema.org%20vocab","name":"schema.org vocab","color":"fbca04"}],"state":"open","locked":false,"assignee":{"login":"vholland","id":4692272,"avatar_url":"https://avatars.githubusercontent.com/u/4692272?v=3","gravatar_id":"","url":"https://api.github.com/users/vholland","html_url":"https://github.com/vholland","followers_url":"https://api.github.com/users/vholland/followers","following_url":"https://api.github.com/users/vholland/following{/other_user}","gists_url":"https://api.github.com/users/vholland/gists{/gist_id}","starred_url":"https://api.github.com/users/vholland/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vholland/subscriptions","organizations_url":"https://api.github.com/users/vholland/orgs","repos_url":"https://api.github.com/users/vholland/repos","events_url":"https://api.github.com/users/vholland/events{/privacy}","received_events_url":"https://api.github.com/users/vholland/received_events","type":"User","site_admin":false},"milestone":null,"comments":15,"created_at":"2015-05-26T13:43:48Z","updated_at":"2015-06-05T22:08:21Z","closed_at":null,"body":"For many events, the location includes a room name. Schema.org should support a way to specify the room.\r\n\r\nIn some cases, rooms have numeric names containing floor and room number. For example, [MIT's 26-100](https://whereis.mit.edu/?go=26).\r\n\r\nIn other cases, the room name has no location information embedded in it. For example, Stanford's [Berg Hall](https://events.stanford.edu/events/496/49631/) within the Li Ka Shing Center. Schema.org would need separate properties if we want to get to the level of floor number, etc.\r\n"},"comment":{"url":"https://api.github.com/repos/schemaorg/schemaorg/issues/comments/109455546","html_url":"https://github.com/schemaorg/schemaorg/issues/545#issuecomment-109455546","issue_url":"https://api.github.com/repos/schemaorg/schemaorg/issues/545","id":109455546,"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},"created_at":"2015-06-05T22:08:21Z","updated_at":"2015-06-05T22:08:21Z","body":"I actually think we will need all three - schema:Room (any room), schema:HotelRoom (a room for temporary lodging), and schema:MeetingRoom. But let's wait for my accommodation proposal. It should also cover this issue.\n\nMartin\n\n-----------------------------------\nmartin hepp  http://www.heppnetz.de\nmhepp@computer.org          @mfhepp\n\n\n\n\n\n\n\n> On 05 Jun 2015, at 21:45, Aaron Bradley <notifications@github.com> wrote:\n> \n> +1 to suggestion from @mfhepp.\n> \n> Re \"simple case of schema:Room\" wouldn't it be possible to create that, and\n> the required property \"roomNumber\" without needing to enumerate more\n> specific sub-types?\n> \n> On Fri, Jun 5, 2015 at 7:32 AM, vholland <notifications@github.com> wrote:\n> \n> > @mfhepp <https://github.com/mfhepp> It sounds promising. It would be nice\n> > to support the simple case of schema:Room, so we don't have to enumerate\n> > all of the possible room types.\n> >\n> > —\n> > Reply to this email directly or view it on GitHub\n> > <https://github.com/schemaorg/schemaorg/issues/545#issuecomment-109311711>\n> > .\n> >\n> —\n> Reply to this email directly or view it on GitHub.\n> \n\n"}}