Ontology Version: 3.1.0
  1. Home
  2. Entities
  3. Classes
  4. cacontology-coord:OperationalLiaison

cacontology-coord:OperationalLiaison leaf node

URI

https://cacontology.projectvic.org/investigation-coordination#OperationalLiaison

Label

Operational Liaison

Description

Operational liaison officer coordinating operational activities and tactical coordination.

Superclasses (5)

Usage

Instances of cacontology-coord:OperationalLiaison can have the following properties:

PROPERTYTYPEDESCRIPTIONRANGE

Property Shapes

By the associated SHACL property shapes, instances of cacontology-coord:OperationalLiaison can have the following properties:

PROPERTY PROPERTY TYPE DESCRIPTION MIN MAX VALUE TYPE OTHER CONSTRAINTS GLOBAL RANGE
cacontology-coord:LiaisonOfficer
cacontology-coord:assignmentDuration owl:DatatypeProperty Duration of liaison assignment in days.
sh:message Liaison assignment duration must be between 1 and 2190 days (6 years).
 1 1 xsd:decimal
sh:minInclusive 1.0
sh:maxInclusive 2190.0
xsd:decimal
cacontology-coord:clearanceLevel owl:DatatypeProperty Security clearance level of the liaison officer (none, public_trust, confidential, secret, top_secret, sci_access).
sh:message Clearance level must be from the allowed list.
 0 1 xsd:string
sh:in none, public_trust, confidential, secret, top_secret, sci_access
xsd:string
cacontology-coord:communicationAuthority owl:DatatypeProperty Level of communication authority (full_authority, limited_authority, information_only, coordination_only, advisory_only).
sh:message Liaison officer must specify communication authority from the allowed list.
 1 1 xsd:string
sh:in full_authority, limited_authority, information_only, coordination_only, advisory_only
xsd:string
cacontology-coord:hasDataCompleteness owl:DatatypeProperty Data completeness measurement (0.0 to 1.0) - gUFO quality aspect.
sh:message Data completeness must be between 0.0 and 1.0 (gUFO quality aspect)
 0 1 xsd:double
sh:minInclusive 0.0
sh:maxInclusive 1.0
xsd:double
cacontology-coord:hasDataConsistency owl:DatatypeProperty Data consistency measurement (0.0 to 1.0) - gUFO quality aspect.
sh:message Data consistency must be between 0.0 and 1.0 (gUFO quality aspect)
 0 1 xsd:double
sh:minInclusive 0.0
sh:maxInclusive 1.0
xsd:double
cacontology-coord:hasDataQuality owl:DatatypeProperty Data quality assessment (poor, fair, good, excellent, validated) - gUFO quality aspect.
sh:message Data quality level must be from allowed list (gUFO quality aspect)
 0 1 xsd:string
sh:in poor, fair, good, excellent, validated
xsd:string
cacontology-coord:hasLiaisonEffectiveness owl:DatatypeProperty Liaison effectiveness level (poor, adequate, good, excellent, exceptional) - gUFO quality aspect.
sh:message Liaison effectiveness level must be from allowed list (gUFO quality aspect)
 0 1 xsd:string
sh:in poor, adequate, good, excellent, exceptional
xsd:string
cacontology-coord:hasResponsiveness owl:DatatypeProperty Response capability level (slow, moderate, good, rapid, immediate) - gUFO quality aspect.
sh:message Responsiveness level must be from allowed list (gUFO quality aspect)
 0 1 xsd:string
sh:in slow, moderate, good, rapid, immediate
xsd:string
cacontology-coord:hasTrustLevel owl:DatatypeProperty Trust relationship measurement (0.0 to 1.0) - gUFO quality aspect.
sh:message Trust level must be between 0.0 and 1.0 (gUFO quality aspect)
 0 1 xsd:double
sh:minInclusive 0.0
sh:maxInclusive 1.0
xsd:double
cacontology-coord:hasValidationLevel owl:DatatypeProperty Validation thoroughness (none, basic, standard, comprehensive, full_verification) - gUFO quality aspect.
sh:message Validation level must be from allowed list (gUFO quality aspect)
 0 1 xsd:string
sh:in none, basic, standard, comprehensive, full_verification
xsd:string
cacontology-coord:liaisonRole owl:DatatypeProperty Role of the liaison officer (primary_liaison, secondary_liaison, technical_liaison, legal_liaison, intelligence_liaison, operational_liaison).
sh:message Liaison officer must specify liaison role from the allowed list.
 1 1 xsd:string
sh:in primary_liaison, secondary_liaison, technical_liaison, legal_liaison, intelligence_liaison, operational_liaison
xsd:string
gufo:hasBeginPointInXSDDateTimeStamp --
sh:message Entity may have temporal beginning (gUFO temporal boundary); Liaison assignment may have start time (gUFO temporal boundary)
 0 1 xsd:dateTime --
gufo:hasEndPointInXSDDateTimeStamp --
sh:message Entity may have temporal ending (gUFO temporal boundary); Liaison assignment may have end time (gUFO temporal boundary)
 0 1 xsd:dateTime --
rdfs:comment --
sh:message Comment should be between 10 and 1000 characters when provided.
 0 1 xsd:string
sh:minLength 10
sh:maxLength 1000
--
rdfs:label --
sh:message Label should be between 5 and 200 characters when provided.
 0 1 xsd:string
sh:minLength 5
sh:maxLength 200
--
uco-core:createdTime --
sh:message Creation time should be specified when available.
 0 1 xsd:dateTime --
uco-core:modifiedTime --
sh:message Modification time should be specified when available.
 0 1 xsd:dateTime --
cac-core:Role
cacontology-infrastructure:hasRoleBeginPoint owl:DatatypeProperty Temporal begin point for technical roles (gUFO temporal property).
sh:message Technical role may have begin point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-infrastructure:hasRoleEndPoint owl:DatatypeProperty Temporal end point for technical roles (gUFO temporal property).
sh:message Technical role may have end point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-multi:hasAuthorityLevel --
sh:message Authority level must be from allowed values (gUFO quality aspect).
 0 1 xsd:string
sh:in minimal, limited, moderate, high, complete
--
cacontology-multi:hasResponsiveness --
sh:message Responsiveness must be from allowed values (gUFO quality aspect).
 0 1 xsd:string
sh:in poor, slow, adequate, good, excellent
--
cacontology-multi:hasRoleBeginPoint owl:DatatypeProperty Temporal begin point for coordination role.
sh:message Coordination role may have begin point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-multi:hasRoleEffectiveness --
sh:message Role effectiveness must be between 0.0 and 1.0 (gUFO quality aspect).
 0 1 xsd:double
sh:minInclusive 0.0
sh:maxInclusive 1.0
--
cacontology-multi:hasRoleEndPoint owl:DatatypeProperty Temporal end point for coordination role.
sh:message Coordination role may have end point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-partnerships:hasRoleBeginPoint owl:DatatypeProperty Temporal begin point for partner role.
sh:message Partner role may have begin point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-partnerships:hasRoleEndPoint owl:DatatypeProperty Temporal end point for partner role.
sh:message Partner role may have end point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-physical:hasRoleBeginPoint owl:DatatypeProperty Temporal begin point for forensic roles (gUFO temporal property).
sh:message Forensic role may have begin point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-physical:hasRoleEndPoint owl:DatatypeProperty Temporal end point for forensic roles (gUFO temporal property).
sh:message Forensic role may have end point timestamp.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-production:hasRoleBeginPoint owl:DatatypeProperty Temporal begin point for production role.
sh:message Production role may have at most one begin point.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology-production:hasRoleEndPoint owl:DatatypeProperty Temporal end point for production role.
sh:message Production role may have an end point.
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology:hasRoleBeginPoint owl:DatatypeProperty Temporal begin point for CAC role.
sh:message Role can have at most one begin point
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology:hasRoleEndPoint owl:DatatypeProperty Temporal end point for CAC role.
sh:message Role can have at most one end point
 0 1 xsd:dateTimeStamp xsd:dateTimeStamp
cacontology:participatesInInvestigation --
sh:message Role must participate in at least one investigation
 0 * cacontology:CACInvestigation --
rdf:type --
sh:message gUFO Roles must be OWL classes.
 1 *
sh:hasValue owl:Class
--
rdfs:label -- label
 1 * xsd:string --

Implementation

@prefix cacontology-coord: <https://cacontology.projectvic.org/investigation-coordination#> .
@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-coord:OperationalLiaison a gufo:Role,
        owl:Class ;
    rdfs:label "Operational Liaison"@en ;
    rdfs:comment "Operational liaison officer coordinating operational activities and tactical coordination."@en ;
    rdfs:subClassOf cacontology-coord:LiaisonOfficer .