https://ontology.unifiedcyberontology.org/uco/action/Technique
A technique is a class of actions joined by some common characteristics. The class uco-action:Technique is a metaclass. A Technique instance is an owl:Class that is a subclass of uco-action:Action. - This shape will find violations after RDFS or OWL-RL inferencing, but might not find some violations without inferencing. - This property shape confirms an instance of Technique is a class that is an eventual subclass of Action. The Action class itself is not a Technique.
Instances of action:Technique can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class action:Technique | |||
| action:techniqueID | owl:DatatypeProperty | An identifier for a technique within some cataloguing system. At the general level of UCO, techniqueID is left optional and minimally-described aside from needing to be Literal-valued. Specializations of Technique should also consider specializing a corresponding subproperty of techniqueID to enable support of global review of technique identifiers. | owl:Thing |
| From class owl:Thing | |||
| core:informalType | owl:DatatypeProperty | Informal Type serves as a parent property for string-valued properties meant to describe a type without implementing a class design. This property hierarchy supports a balancing point between semantic specificity and operational agility. The known benefits of describing types rather than implementing them include swift extensibility of some existing, or possibly non-existing, subclass hierarchy in UCO without requiring training in ontological development, taxonomic specification, or OWL, SHACL, or RDF maintenance logistics. The known detractions of using string-literals for type descriptions include that used vocabularies may require careful maintenance among data-sharing parties; that vocabularies require independent logistics (external to UCO) for providing definitions (i.e., dictionary-style semantics) to string-literals chosen; and that string-literals cannot by themselves encode hierarchical structure or entailments, such as the informal device type string 'ExamplePhone 8 P4321' entailing 'ExamplePhone 8', 'ExamplePhone', or 'ExamplePhone models discontinued in 2020'. Usage of Informal Type to house strings should be weighed against usage of classes when classes are available, and should periodically be reviewed for potential additions to UCO's class hierarchy or downstream extensions thereof. | owl:Thing |
| types:threadNextItem | owl:ObjectProperty | The link to a next item in a thread. | owl:Thing |
| types:threadPreviousItem | owl:ObjectProperty | A direct link to a previous item in a thread. | owl:Thing |
By the associated SHACL property shapes, instances of action:Technique can have the following properties:
PROPERTY |
PROPERTY TYPE |
DESCRIPTION |
MIN COUNT |
MAX COUNT |
LOCAL RANGE |
GLOBAL RANGE |
|
|---|---|---|---|---|---|---|---|
| action:Technique | |||||||
| action:techniqueID | owl:DatatypeProperty |
An identifier for a technique within some cataloguing system. At the general level of UCO, techniqueID is left optional and minimally-described aside from needing to be Literal-valued. Specializations of Technique should also consider specializing a corresponding subproperty of techniqueID to enable support of global review of technique identifiers.
|
owl:Thing | ||||
@prefix action: <https://ontology.unifiedcyberontology.org/uco/action/> .
@prefix core: <https://ontology.unifiedcyberontology.org/uco/core/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
action:Technique a owl:Class,
sh:NodeShape ;
rdfs:label "Technique"@en ;
rdfs:comment "A technique is a class of actions joined by some common characteristics. The class uco-action:Technique is a metaclass. A Technique instance is an owl:Class that is a subclass of uco-action:Action."@en ;
rdfs:subClassOf core:UcoType ;
sh:property [ rdfs:comment "This property shape confirms an instance of Technique is a class that is an eventual subclass of Action. The Action class itself is not a Technique."@en ;
sh:hasValue action:Action ;
sh:path [ sh:oneOrMorePath rdfs:subClassOf ] ],
[ rdfs:comment "This shape will find violations after RDFS or OWL-RL inferencing, but might not find some violations without inferencing."@en ;
sh:nodeKind sh:Literal ;
sh:path action:techniqueID ] ;
sh:targetClass action:Technique .