{"action":"created","issue":{"url":"https://api.github.com/repos/BuildingSMART/IFC4-CV/issues/16","repository_url":"https://api.github.com/repos/BuildingSMART/IFC4-CV","labels_url":"https://api.github.com/repos/BuildingSMART/IFC4-CV/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/BuildingSMART/IFC4-CV/issues/16/comments","events_url":"https://api.github.com/repos/BuildingSMART/IFC4-CV/issues/16/events","html_url":"https://github.com/BuildingSMART/IFC4-CV/issues/16","id":36184586,"number":16,"title":"Support for a One-to-Many (non-type) of 'Group'.  ","user":{"login":"theoryshaw","id":507113,"avatar_url":"https://avatars.githubusercontent.com/u/507113?v=3","gravatar_id":"","url":"https://api.github.com/users/theoryshaw","html_url":"https://github.com/theoryshaw","followers_url":"https://api.github.com/users/theoryshaw/followers","following_url":"https://api.github.com/users/theoryshaw/following{/other_user}","gists_url":"https://api.github.com/users/theoryshaw/gists{/gist_id}","starred_url":"https://api.github.com/users/theoryshaw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theoryshaw/subscriptions","organizations_url":"https://api.github.com/users/theoryshaw/orgs","repos_url":"https://api.github.com/users/theoryshaw/repos","events_url":"https://api.github.com/users/theoryshaw/events{/privacy}","received_events_url":"https://api.github.com/users/theoryshaw/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2014-06-20T17:00:51Z","updated_at":"2016-10-11T14:54:47Z","closed_at":"2014-07-02T18:46:40Z","body":"For IFC **Design Transfer View**, is it possible to support one-to-many (non-type) Groups?\r\n\r\n*i use the word 'Groups', as a stand-in for the concept described below.  A better term might be designated*\r\n\r\nexample...\r\n\r\n* A BIM file, from Vendor X, contains 10 instances of #Group Z. (Group Z is composed of a wall, a column, and a piece of furniture, for example) →\r\n* This BIM file is exported, via IFC, and in turn imported into Vendor Y's BIM file. →\r\n* Within vendor Y's program, a user changes/modifies the definition of #group Z. This change is, in turn, propagated throughout the 10 instances of #Group Z , within vendor Y's file.\r\n"},"comment":{"url":"https://api.github.com/repos/BuildingSMART/IFC4-CV/issues/comments/252941551","html_url":"https://github.com/BuildingSMART/IFC4-CV/issues/16#issuecomment-252941551","issue_url":"https://api.github.com/repos/BuildingSMART/IFC4-CV/issues/16","id":252941551,"user":{"login":"theoryshaw","id":507113,"avatar_url":"https://avatars.githubusercontent.com/u/507113?v=3","gravatar_id":"","url":"https://api.github.com/users/theoryshaw","html_url":"https://github.com/theoryshaw","followers_url":"https://api.github.com/users/theoryshaw/followers","following_url":"https://api.github.com/users/theoryshaw/following{/other_user}","gists_url":"https://api.github.com/users/theoryshaw/gists{/gist_id}","starred_url":"https://api.github.com/users/theoryshaw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theoryshaw/subscriptions","organizations_url":"https://api.github.com/users/theoryshaw/orgs","repos_url":"https://api.github.com/users/theoryshaw/repos","events_url":"https://api.github.com/users/theoryshaw/events{/privacy}","received_events_url":"https://api.github.com/users/theoryshaw/received_events","type":"User","site_admin":false},"created_at":"2016-10-11T14:54:46Z","updated_at":"2016-10-11T14:54:46Z","body":"Apropos to this discussion: https://www.researchgate.net/publication/305770614_Modeling_of_repetitive_IFC_Building_Elements_using_the_Flyweight_Design_Pattern_Approach\r\nThought I'd share."}}
{"actor":{"display_login":"theoryshaw"}}