skills

[elf-pavlik]

I would like to start brainstorming how to express skills. Most processes (all not fully automated ones) will require involvement of an Agent with particular set of skills. So far I tend to use Cognitive Characteristics Ontology for describing skills. I also noticed recent creation of CV 2.0 - Global Resume Community Group. I guess we will need to look at skills from both agent and process perspective.

[bhaugen]

We (and the NRP vocab) consider skills to be Resource Types. They could be described by, and are certainly related to, those other vocabularies. But they also, as you wrote, are related to agents and processes.

Work is a resource to us, and is usually a required input to a process that creates something.

So, for example if you were coming from an IPO perspective, on the recipe layer, a Process Type may require inputs of work as well as other resources of other types. Those work inputs might require different skills, which would be specified by different Resource Types.

Sensorica may require Electronic Engineering, Optical Engineering, Mechanical Engineering, and 3D Design skills as inputs to the same process.

We have an Agent Resource Type relationship which not only means that this agent can provide that skill, but it also keeps a summary of Economic Events where the agent has performed that skill, and can be connected to all of those events if an authorized person wants to look deeper into their history.

Likewise those economic events are connected to the processes that they went into, and onward to the resources that were created by those processes, and potentially to exchanges that gave those resources to some other agent, who may have returned some other resources as compensation. So those returned resources may be shared with the agents who did the work by means of a value equation.

(That might have been more than you wanted to know. Or not.)

[elf-pavlik]

We have an Agent Resource Type relationship which not only means that this agent can provide that skill, but it also keeps a summary of Economic Events where the agent has performed that skill, and can be connected to all of those events if an authorized person wants to look deeper into their history.

Interesting, this sounds in a way similar to what I recently replied to @rhiaro about need for direct relations, qualified relations and activities and using them together to express knowledge like you just mention.

https://lists.w3.org/Archives/Public/public-social-interest/2015Aug/0026.html

I do NOT replace Activity object with Relation object. Let's say I
visted Berlin 20 times so far. I would have a direct relation, qualifed
relation and 20 activities:

{
  "@graph": [
    {
      "@id": "https://wwelves.org/perpeual-tripper",
      "@type": "Person",
      "displayName": "elf Pavlik",
      "visits": [
        "http://dbpedia.org/page/Berlin"
      ],
      "relation": [
        "https://graph.wwelves.org/e1e677ab-8427-40a6-a177-ef7b48254633"
      ]
    },
    {
      "@id":
"https://graph.wwelves.org/e1e677ab-8427-40a6-a177-ef7b48254633",
      "@type": "Relation",
      "subject": "https://wwelves.org/perpeual-tripper",
      "object": "http://dbpedia.org/page/Berlin",
      "property": "visits",
      "activity": []
    }
  ]
}

where activity array will have 20 elements with: "@type": "Activity"

[bhaugen]

Afterthought: the history of an agent's performance in using a skill in productive work can be a more-accurate measure of their reputation and qualifications than subjective ratings or academic credentials.

[elf-pavlik]

the history of an agent's performance in using a skill in productive work can be a more-accurate measure of their reputation and qualifications than subjective ratings or academic credentials.

👍

More than seeing someone's certificate in proficiency with JavaScript, I would prefer to see open source code and history of git commits. http://git2prov.org/

[elf-pavlik]

So, for example if you were coming from an IPO perspective, on the recipe layer, a Process Type may require inputs of work as well as other resources of other types. Those work inputs might require different skills, which would be specified by different Resource Types.

Sensorica may require Electronic Engineering, Optical Engineering, Mechanical Engineering, and 3D Design skills as inputs to the same process.

How do you relate resource type of equipment '3d printer' to resource type of work 'operating 3d printer' or resource type of service 'repairing 3d printer'?

[fosterlynn]

How do you relate resource type of equipment '3d printer' to resource type of work 'operating 3d printer' or resource type of service 'repairing 3d printer'?

We don't have any relationships between those resource types. Not that one couldn't.

There are some access rules that are not validated in the software, like only trained or certified people are allowed to operate the 3d printer. Those are in the agent-resource relationship and text, as an easy beginning implementation of access rules.

[almereyda]

We have moved the ValueFlows organization from GitHub to https://lab.allmende.io/valueflows.

This issue has been closed here, and all further discussion on this issue can be done at

https://lab.allmende.io/valueflows/agent/-/issues/8.

If you have not done so, you are very welcome to register at https://lab.allmende.io and join the ValueFlows organization there.