{"action":"created","issue":{"url":"https://api.github.com/repos/openvocab/holodex/issues/1","labels_url":"https://api.github.com/repos/openvocab/holodex/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/openvocab/holodex/issues/1/comments","events_url":"https://api.github.com/repos/openvocab/holodex/issues/1/events","html_url":"https://github.com/openvocab/holodex/issues/1","id":59729775,"number":1,"title":"roles","user":{"login":"ahdinosaur","id":719605,"avatar_url":"https://avatars.githubusercontent.com/u/719605?v=3","gravatar_id":"","url":"https://api.github.com/users/ahdinosaur","html_url":"https://github.com/ahdinosaur","followers_url":"https://api.github.com/users/ahdinosaur/followers","following_url":"https://api.github.com/users/ahdinosaur/following{/other_user}","gists_url":"https://api.github.com/users/ahdinosaur/gists{/gist_id}","starred_url":"https://api.github.com/users/ahdinosaur/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ahdinosaur/subscriptions","organizations_url":"https://api.github.com/users/ahdinosaur/orgs","repos_url":"https://api.github.com/users/ahdinosaur/repos","events_url":"https://api.github.com/users/ahdinosaur/events{/privacy}","received_events_url":"https://api.github.com/users/ahdinosaur/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/openvocab/holodex/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":24,"created_at":"2015-03-04T00:13:51Z","updated_at":"2015-03-17T19:09:57Z","closed_at":null,"body":"in my opinion, one major selling point of holodex is a system to describe and delegate roles within a network. a great example of an existing system with similar aims is [GlassFrog](https://glassfrog.holacracy.org/organizations/5).\r\n\r\nthe concept of a role is overloaded, so in order to architect a beautiful system we need to break it down into its constituent pieces. i'll approach this with a simple example of an actual role: as the \"Desk Collector\" in [Enspiral Craftworks](http://craftworks.enspiral.com), i have the responsibilities of \"every month, collect intention to contribute money to collective desk account, then check people have actually put money into desk account (friendly nags if necessary)\". this role organically grew into being last month as we needed to collectively pay-what-we-want for our desks at [Enspiral Space](http://enspiralspace.co.nz) and i volunteered to be the touch point, which in the process lead me to define the role into something beyond me than can be passed on from person to person within Enspiral Craftworks.\r\n\r\nwe have our first piece to describe roles already which we are calling relationships, namely a connection between multiple agents optionally under the context of other agents. examples of these relationships so far include group <-> member, parent <-> child, steward <-> stewardee, friendships, mentor <-> mentee, followers, customer <-> supplier, etc. as of now, it fails to denote a mechanism for including better information concerning the role played by a given relationship, namely the purpose, domains, responsibilities, etc. we could add this to our `RelationshipType` definition, but i wonder if maybe we are using an inadaquate term, or maybe i'm conflating relationships (aka associations) with another concept.\r\n\r\nanother piece of the puzzle is combining multiple [\"roles\"](http://www.w3.org/TR/vocab-org/#org:Role) into a single [\"post\"](http://www.w3.org/TR/vocab-org/#class-post) that exists independently of the person filing the \"roles\". the \"Desk Collector\" in Enspiral Craftworks is one such \"post\", where we pass it along from person to person while the core \"role\" stays the same. it's not enough to pass along a single relationship because it's entirely possible that one \"post\" may contain multiple \"roles\". the solution for this i've considered is to follow the practice of other concepts in the [Value Network vocabulary](https://github.com/openvocab/ovn) and create a virtual entity that parallels the actual entity, namely a virtual agent entity that parallels actual agent entities. in this way, actual agents (me) can assume many virtual agents (\"Desk Collector\"), much in the same way that i can put on many hats, masks, coats, etc depending on the situation and context. i'm partial to this virtual parallel because then in many ways we can treat these virtual agents the same as actual agents, which feels right.\r\n\r\ni'm gonna think more about this, in particular i think there may be something to virtual agents in combination with capacities instead of relationships, e.g. \"the Desk Collector has these capacities (responsibilities described) and depends on these capacities (being an Enspiral Craftworks member)\", but i need to iron out some more examples in data format.\r\n\r\n/cc @bhaugen @fosterlynn "},"comment":{"url":"https://api.github.com/repos/openvocab/holodex/issues/comments/82539890","html_url":"https://github.com/openvocab/holodex/issues/1#issuecomment-82539890","issue_url":"https://api.github.com/repos/openvocab/holodex/issues/1","id":82539890,"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},"created_at":"2015-03-17T19:09:57Z","updated_at":"2015-03-17T19:09:57Z","body":"@ahdinosaur  Here's one riffing off of your latest.....\r\n![agent2](https://cloud.githubusercontent.com/assets/3776081/6695440/39b4ec18-ccaf-11e4-8c44-c6e037a40c1d.png)\r\n \r\n"}}