{"action":"created","issue":{"url":"https://api.github.com/repos/valueflows/exchange/issues/16","repository_url":"https://api.github.com/repos/valueflows/exchange","labels_url":"https://api.github.com/repos/valueflows/exchange/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/valueflows/exchange/issues/16/comments","events_url":"https://api.github.com/repos/valueflows/exchange/issues/16/events","html_url":"https://github.com/valueflows/exchange/issues/16","id":151206482,"number":16,"title":"Data structure for Transfer","user":{"login":"fosterlynn","id":3776081,"avatar_url":"https://avatars.githubusercontent.com/u/3776081?v=3","gravatar_id":"","url":"https://api.github.com/users/fosterlynn","html_url":"https://github.com/fosterlynn","followers_url":"https://api.github.com/users/fosterlynn/followers","following_url":"https://api.github.com/users/fosterlynn/following{/other_user}","gists_url":"https://api.github.com/users/fosterlynn/gists{/gist_id}","starred_url":"https://api.github.com/users/fosterlynn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fosterlynn/subscriptions","organizations_url":"https://api.github.com/users/fosterlynn/orgs","repos_url":"https://api.github.com/users/fosterlynn/repos","events_url":"https://api.github.com/users/fosterlynn/events{/privacy}","received_events_url":"https://api.github.com/users/fosterlynn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2016-04-26T18:28:01Z","updated_at":"2016-04-29T23:00:44Z","closed_at":null,"body":"What should our data structure look like?\r\n\r\nHere is more or less where I ended up in NRP recently, simplified to be able to start a discussion.  Understanding of course that is one input.  I'll just put it out there with the data as is, understanding we need to make it LOD friendly, discuss subclassing, etc.\r\n\r\nTransfer\r\n    - name\r\n    - transfer type\r\n    - notes\r\n    - give and/or receive flows, depending on your scope of knowledge\r\n\r\nGive flow\r\n    - event date\r\n    - from agent \r\n    - to agent \r\n    - resource type\r\n    - resource \r\n    - description\r\n    - quantity\r\n    - unit of quantity\r\n\r\nReceive flow\r\n    - event date\r\n    - from agent \r\n    - to agent \r\n    - resource type\r\n    - resource \r\n    - description\r\n    - quantity\r\n    - unit of quantity\r\n\r\nIt could be normalized to something like the following.  Although I think we want Value Flow (aka Economic Event) to be able to be used in Transfers and Processes, so that may push it back towards the above.\r\n\r\nTransfer\r\n    - name\r\n    - transfer type (user defined)\r\n    - notes\r\n    - give and/or receive flows, depending on your scope of knowledge\r\n    - from agent\r\n    - to agent\r\n    - resource type\r\n    - quantity\r\n    - unit of quantity\r\n\r\nGive flow\r\n    - event date\r\n    - resource \r\n    - description\r\n\r\nReceive flow\r\n    - event date\r\n    - resource \r\n    - description\r\n\r\n[removed context agent]"},"comment":{"url":"https://api.github.com/repos/valueflows/exchange/issues/comments/215903151","html_url":"https://github.com/valueflows/exchange/issues/16#issuecomment-215903151","issue_url":"https://api.github.com/repos/valueflows/exchange/issues/16","id":215903151,"user":{"login":"elf-pavlik","id":876431,"avatar_url":"https://avatars.githubusercontent.com/u/876431?v=3","gravatar_id":"","url":"https://api.github.com/users/elf-pavlik","html_url":"https://github.com/elf-pavlik","followers_url":"https://api.github.com/users/elf-pavlik/followers","following_url":"https://api.github.com/users/elf-pavlik/following{/other_user}","gists_url":"https://api.github.com/users/elf-pavlik/gists{/gist_id}","starred_url":"https://api.github.com/users/elf-pavlik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/elf-pavlik/subscriptions","organizations_url":"https://api.github.com/users/elf-pavlik/orgs","repos_url":"https://api.github.com/users/elf-pavlik/repos","events_url":"https://api.github.com/users/elf-pavlik/events{/privacy}","received_events_url":"https://api.github.com/users/elf-pavlik/received_events","type":"User","site_admin":false},"created_at":"2016-04-29T23:00:44Z","updated_at":"2016-04-29T23:00:44Z","body":"I understand that in case of provided example of Transfer, you would use context to in a way label/tag in case you would like to filter by it in a future? Since we talk about easily extensible model, we can always add tags/labels or any extra information we care about. I think we should mostly focus on necessary minimum needed to express something.\r\n\r\nDoes anyone see in this example more required information for the transfer other than: **from**: (agent), **to**: (agent), **what**: (rights)\r\n\r\nSo far I understand that @fosterlynn lynn and I take different approach to how to express the **what**. Maybe we could focus on that since we all seem to agree on **from** & **to** (agents)."}}