Simplify class identifiers

[akijakya]

The way classes are used in OASF is a lot different than what purpose they served in OCSF, from which this project has been forked from. Instead of just one kind of class (event classes) that is in the case of OCSF, we have three class families, out of which skills and domains are like tags, they are for agent records to indicate whether they have them or not. features are more descriptive in their data field.

Example skill (domains are structurally the same)

{
    "category_name": "Natural Language Processing",
    "class_uid": 10101,
    "category_uid": 1,
    "class_name": "Contextual Comprehension",
    "annotations": {...}
}

Example feature

{
    "data": {...},
    "name": "schema.oasf.agntcy.org/features/observability",
    "version": "v1.1.1",
    "annotations": {...}
}

Problem

• there is a lot of "noise" in a skill class object, seems like a lot of field to describe a simple thing
  • also the category_uid can be inferred from the class_uid which starts with the category number
• if only the required field is given, which is the class_uid, it doesn't tell the human observer of the agent record, which skill is meant by the number
• skill/domain and feature classes have little in common, it doesn't feel coherent

Proposal

I propose we could use a name field in skills and domains instead of uid similar to how a feature class looks like. That would make a human observer of an agent record understand better which skills are listed even if just the required minimal information is given (which is the class_uid currently). A minimalistic approach would only use the name attribute, although the category name, and the human readable names could be kept as optional fields:

{
    "name": "schema.oasf.agntcy.org/skills/contextual_comprehension", #required, working link
    "category_name": "natural_language_processing", #optional
    "annotations": {...} #optional
}

Although it does not make a working link, we could modify OASF code to work with the category in the URL as well, so we don't need the category_name either:

{
    "name": "schema.oasf.agntcy.org/skills/natural_language_processing/contextual_comprehension", #required, currently not a working link
    "annotations": {...} #optional
}

If we don't want to allow to use skills/domains from elsewhere than OASF (like in the case of features), the name could be simplified to the reference name of the class, and the category's reference name could be kept as a separate attribute:

{
    "name": "contextual_comprehension", #required
    "category_name": "natural_language_processing", #optional
    "annotations": {...} #optional
}

[akijakya]

Skill and domain classes were simplified in #137