https://cacontology.projectvic.org/extremist-enterprises#MembershipTier
Membership tier within enterprise hierarchy determining access and privileges.
Instances of cacontology-enterprises:MembershipTier can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|
By the associated SHACL property shapes, instances of cacontology-enterprises:MembershipTier can have the following properties:
| PROPERTY | PROPERTY TYPE | DESCRIPTION | MIN | MAX | VALUE TYPE | OTHER CONSTRAINTS | GLOBAL RANGE |
|---|---|---|---|---|---|---|---|
| cacontology-enterprises:MembershipTier | |||||||
| cacontology-enterprises:accessLevel | owl:DatatypeProperty | Level of access to enterprise resources and channels. sh:message Access level must be valid level. |
0 | 1 | xsd:string |
sh:in
restricted, basic, enhanced, privileged, full
|
xsd:string |
| cacontology-enterprises:membershipLevel | owl:DatatypeProperty | Member level within enterprise hierarchy (novice, member, advanced, inner_core, leader). sh:message Membership level must be valid tier. |
0 | 1 | xsd:string |
sh:in
novice, member, advanced, inner_core, leader
|
xsd:string |
| cac-core:Phase | |||||||
| cac-core:precedes | owl:ObjectProperty | Asserts that one exploitation phase or event directly precedes another in the documented offense timeline. Used to build temporally ordered traversal graphs for state machine analysis of case lifecycles. The subject phase occurs before the object phase in the same investigation. sh:message Each cac-core:precedes object must be typed as a Phase instance (or subclass). |
0 | * | cac-core:Phase | cac-core:Phase | |
| cacontology-infrastructure:hasPhaseBeginPoint | owl:DatatypeProperty | Temporal begin point for infrastructure phases (gUFO temporal property). sh:message Infrastructure phase may have begin point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-infrastructure:hasPhaseEndPoint | owl:DatatypeProperty | Temporal end point for infrastructure phases (gUFO temporal property). sh:message Infrastructure phase may have end point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-multi:hasCoordinationPhaseBeginPoint | owl:DatatypeProperty | Temporal begin point for coordination phase. sh:message Coordination phase may have begin point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-multi:hasCoordinationPhaseEndPoint | owl:DatatypeProperty | Temporal end point for coordination phase. sh:message Coordination phase may have end point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-partnerships:hasPhaseBeginPoint | owl:DatatypeProperty | Temporal begin point for partnership phase. sh:message Partnership phase may have begin point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-partnerships:hasPhaseEndPoint | owl:DatatypeProperty | Temporal end point for partnership phase. sh:message Partnership phase may have end point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-physical:hasPhaseBeginPoint | owl:DatatypeProperty | Temporal begin point for evidence phases (gUFO temporal property). sh:message Evidence phase may have begin point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-physical:hasPhaseEndPoint | owl:DatatypeProperty | Temporal end point for evidence phases (gUFO temporal property). sh:message Evidence phase may have end point timestamp. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-production:hasProductionPhaseBeginPoint | owl:DatatypeProperty | Temporal begin point for production phase. sh:message Production phase may have at most one begin point. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-production:hasProductionPhaseEndPoint | owl:DatatypeProperty | Temporal end point for production phase. sh:message Production phase may have an end point. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-temporal:hasLegalDeadline | owl:DatatypeProperty | Legal deadline by which investigation phase must be completed (e.g., statute of limitations, warrant expiration). sh:message hasLegalDeadline, when provided, must be a single xsd:dateTimeStamp value. |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology-temporal:hasMaximumDuration | owl:DatatypeProperty | Maximum allowable duration for investigation phase based on legal or policy constraints. sh:message hasMaximumDuration, when provided, must be a single xsd:duration value. |
0 | 1 | xsd:duration | xsd:duration | |
| cacontology-temporal:hasMinimumDuration | owl:DatatypeProperty | Minimum required duration for investigation phase based on legal or procedural requirements. sh:message hasMinimumDuration, when provided, must be a single xsd:duration value. |
0 | 1 | xsd:duration | xsd:duration | |
| cacontology-temporal:hasTypicalDuration | owl:DatatypeProperty | Typical expected duration for investigation phase based on historical patterns. sh:message hasTypicalDuration, when provided, must be a single xsd:duration value. |
0 | 1 | xsd:duration | xsd:duration | |
| cacontology-temporal:phaseCompletionRate | owl:DatatypeProperty | Percentage of phase objectives completed within time period (0.0-1.0). sh:message phaseCompletionRate, when provided, must be an xsd:decimal between 0.0 and 1.0. |
0 | 1 | xsd:decimal |
sh:minInclusive
0.0
sh:maxInclusive
1.0
|
xsd:decimal |
| cacontology-temporal:phaseEfficiency | owl:DatatypeProperty | Efficiency ratio of phase (actual duration / typical duration). sh:message phaseEfficiency, when provided, must be a non-negative xsd:decimal value. |
0 | 1 | xsd:decimal |
sh:minInclusive
0.0
|
xsd:decimal |
| cacontology-temporal:urgencyLevel | owl:DatatypeProperty | Urgency level of investigation phase (1-5 scale, 5=critical/immediate). sh:message urgencyLevel, when provided, must be an integer between 1 and 5 (1=lowest, 5=highest). |
0 | 1 | xsd:integer |
sh:minInclusive
1
sh:maxInclusive
5
|
xsd:integer |
| cacontology:hasPhaseBeginPoint | owl:DatatypeProperty | Temporal begin point for investigation phase. sh:message Phase can have at most one begin point |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
| cacontology:hasPhaseEndPoint | owl:DatatypeProperty | Temporal end point for investigation phase. sh:message Phase can have at most one end point |
0 | 1 | xsd:dateTimeStamp | xsd:dateTimeStamp | |
gufo:hasBeginPointInXSDDateTimeStamp |
-- | begin time Optional temporal begin point for the phase. |
0 | 1 | xsd:dateTimeStamp | -- | |
gufo:hasEndPointInXSDDateTimeStamp |
-- | end time Optional temporal end point for the phase. |
0 | 1 | xsd:dateTimeStamp | -- | |
rdf:type |
-- | sh:message Phase instances must have at least one rdf:type declaration. |
1 | * | -- | ||
rdfs:label |
-- | label |
1 | * | xsd:string | -- | |
| cacontology-enterprises:EnterpriseHierarchy | |||||||
| cacontology-enterprises:hierarchyComplexity | owl:DatatypeProperty | Complexity level of enterprise hierarchy (simple, moderate, complex, highly_complex). sh:message Hierarchy complexity must be valid level. |
0 | 1 | xsd:string |
sh:in
simple, moderate, complex, highly_complex
|
xsd:string |
| gufo:FunctionalComplex | |||||||
(gufo:isComponentOf | cacontology-enterprises:hasNetworkComponent | cacontology-enterprises:hasMember) |
-- | sh:message gUFO Functional Complexes must have at least one component or member. |
1 | * | -- | ||
rdf:type |
-- | 1 | * |
sh:hasValue
gufo:FunctionalComplex
|
-- | ||
@prefix cac-core: <https://cacontology.projectvic.org/core#> .
@prefix cacontology-enterprises: <https://cacontology.projectvic.org/extremist-enterprises#> .
@prefix gufo: <http://purl.org/nemo/gufo#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
cacontology-enterprises:MembershipTier a gufo:Phase,
owl:Class ;
rdfs:label "Membership Tier"@en ;
rdfs:comment "Membership tier within enterprise hierarchy determining access and privileges."@en ;
rdfs:subClassOf cac-core:Phase,
cacontology-enterprises:EnterpriseHierarchy .