Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a ceasn:abilityEmbodied property #583

Closed
stuartasutton opened this issue Nov 21, 2018 · 9 comments

Comments

Projects
None yet
4 participants
@stuartasutton
Copy link
Contributor

commented Nov 21, 2018

Currently, we have a ceasn:skillEmbodied property with a domain of ceasn:Competency that makes it possible for a specific competency to have a ceasn:competencyCategory of something like "Task" and then assert that that task has a ceasn:skillEmbodied of something like "Judgment and decision making." Current work on the Navy Task Classification indicates that we could benefit from a companion ceasn:abilityEmbodied property.

@siuc-nate

This comment has been minimized.

Copy link

commented Nov 21, 2018

Aren't both of those fundamentally covered by the notion of a Competency to begin with? Would it also then follow that we need ceasn:knowledgeEmbodied, ceasn:behaviorEmbodied, ceasn:attitudeEmbodied, and so on?

@stuartasutton

This comment has been minimized.

Copy link
Contributor Author

commented Nov 21, 2018

No. Not where the skill or ability embodied are relevant to a specific competency node. We have no way to handle that with any precision. Plus, I see no reason to relitigate the existence of ceasn:skillEmbodied. A lot of work went into that back when it was added to ASN. And, no, it does not follow that by adding a ceasn:abilityEmbodied we'd need to create an extended array of other properties absent some compelling need.

@Lomilar

This comment has been minimized.

Copy link
Contributor

commented Dec 6, 2018

Skill embodied appears to be a method of tagging competencies with descriptive psycho and physical classifiers, like: Cognitive based skill, Psychomotor based skill, Empathy based skill, Visual skill, etc.

If that interpretation is correct, the word sense of 'skill' in skillEmbodied is different from 'skill' as denoted in KSAs (being the ability to recall knowledge, perform a skill, or exhibit an ability)

Let me know if I am off base. Was I starting from scratch, the ability to perform psychomotor type tasks would be a soft competency (like the ability to see or the ability to recall information) and there would be a requires relation established, but this isn't the worst way to do this. I'm not sure of all the implications either way.

@stuartasutton

This comment has been minimized.

Copy link
Contributor Author

commented Dec 7, 2018

@Lomilar, not quite sure what you are driving at with the couple of sentences. If I understand you correctly, the only difference between what I (and the ASN) are saying is that you switch the skillEmbodied property for requires. The object is modeled as either a competency or concept scheme either way.

@Lomilar

This comment has been minimized.

Copy link
Contributor

commented Dec 10, 2018

Correct, we don't yet perceive the nuance that distinguishes requiring a psychomotor ability from embodying a psychomotor skill, for instance.

@siuc-nate siuc-nate transferred this issue from CredentialEngine/CompetencyFrameworks Mar 6, 2019

@stuartasutton

This comment has been minimized.

Copy link
Contributor Author

commented Mar 18, 2019

For the ceasn:abilityEmbodied, I am proposing the following addition to cesan:

URI: ceasn:abilityEmbodied
Label: Ability Embodied
Comment: Enduring attributes of the individual that influence performance are embodied either directly or indirectly in this competency.
Domain Includes: ceasn:Competency
RangeIncludes: xsd:anyURI
Usage Note: The abilityEmbodied property may referenced a defined ability in an ontology such as O*NET or an existing competency defined in a competency framework.

Also, modify ceasn:skillEmbodied comment and add the following Usage Note:

Comment: Ability to apply knowledge and use know-how to complete tasks and solve problems including types or categories of developed proficiency or dexterity in mental operations and physical processes is embodied either directly or indirectly in this competency.
Usage Note: The skillEmbodied property may referenced a defined skill in an ontology such as O*NET or an existing competency defined in a competency framework.

@jkitchensSIUC jkitchensSIUC added this to the March 15, 2019 milestone Mar 19, 2019

@siuc-nate

This comment has been minimized.

Copy link

commented Apr 10, 2019

Also, modify ceasn:skillEmbodied comment

I assume you mean the current definition?:
From: "Cognitive, affective, and psychomotor skills directly or indirectly embodied in this competency."
To: "Ability to apply knowledge and use know-how to complete tasks and solve problems including types or categories of developed proficiency or dexterity in mental operations and physical processes is embodied either directly or indirectly in this competency."

@stuartasutton

This comment has been minimized.

Copy link
Contributor Author

commented Apr 10, 2019

Yes.

@siuc-nate

This comment has been minimized.

Copy link

commented Apr 10, 2019

These changes have been made in pending CTDL-ASN and noted in the history tracking.

@siuc-nate siuc-nate closed this Apr 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.