{"action":"opened","issue":{"url":"https://api.github.com/repos/valueflows/valueflows/issues/371","repository_url":"https://api.github.com/repos/valueflows/valueflows","labels_url":"https://api.github.com/repos/valueflows/valueflows/issues/371/labels{/name}","comments_url":"https://api.github.com/repos/valueflows/valueflows/issues/371/comments","events_url":"https://api.github.com/repos/valueflows/valueflows/issues/371/events","html_url":"https://github.com/valueflows/valueflows/issues/371","id":391961936,"node_id":"MDU6SXNzdWUzOTE5NjE5MzY=","number":371,"title":"how parent/child relationshops between resource types relate to resource instances?","user":{"login":"elf-pavlik","id":876431,"node_id":"MDQ6VXNlcjg3NjQzMQ==","avatar_url":"https://avatars0.githubusercontent.com/u/876431?v=4","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},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-12-18T01:44:43Z","updated_at":"2018-12-18T01:44:43Z","closed_at":"2018-12-18T01:44:43Z","author_association":"MEMBER","body":"Let's say we have a parent resource type, with two children types\n- _prodont:Mango_\n  - _prodont:Ataulfo_(mango)_\n  - _prodont:Tommy_Atkins_(mango)_\n\nWhen some recipe references _prodont:Mango_, In my plan I could narrow it to one of the children types or also leave it broader and just in observation reference resource with on of the child types.\n\nSimilar when casting intents, especially instances of _vf:Request_, to satisfy the recipe with broad _prodont:Mango_ I would just ask for any resource of that broader type. In _vf:Transfer_ I would most likely reference resource of one of the children types, which later I would use in my process.\n\nIt also seem to apply to product models, if we have two products which have common parent resource type:\n- _prodont:Olive_oil_\n  - _itacatealimentos:olive-oil-0.75L-in-wine-bottle_\n  - _carbonell:olive-oil-1L-in-metal-can_\n\nIn the same process, to satisfy _prodont:Olive_oil_ requirements. I could even mix resources of different product models and use that mix on input.\n\nRelated to #44, when we merge lots from two different product types, which share common resource type parent, we can use that common parent as _vf:resourceType_ of that merged resource, since non of the specific product types will apply any more.\n"}}
{"actor":{"display_login":"elf-pavlik"}}