Ontology Version: 3.1.0

cacontology-tactical:ArrestOperation leaf node


URI

https://cacontology.projectvic.org/tactical#ArrestOperation

Label

Arrest Operation

Description

Law enforcement operation to apprehend and take suspect into custody. Extends investigation:InvestigativeAction for proper CASE ontology integration.

Usage

Instances of cacontology-tactical:ArrestOperation can have the following properties:

PROPERTYTYPEDESCRIPTIONRANGE

Property Shapes

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

PROPERTY PROPERTY TYPE DESCRIPTION MIN MAX VALUE TYPE OTHER CONSTRAINTS GLOBAL RANGE
cacontology-tactical:ArrestOperation
cacontology-tactical:arrestType owl:DatatypeProperty Type of arrest (warrant_arrest, probable_cause_arrest, consensual_arrest, traffic_stop_arrest, field_arrest, coordinated_arrest).
sh:message Arrest operation must specify arrest type from the allowed list.
1 1 xsd:string
sh:in warrant_arrest, probable_cause_arrest, consensual_arrest, traffic_stop_arrest, field_arrest, coordinated_arrest, sting_operation, undercover_takedown, multi_target_sweep, surveillance_arrest
xsd:string
cacontology-tactical:resistanceExpected owl:DatatypeProperty Whether resistance was expected during arrest.
sh:message Arrest operation must specify if resistance is expected.
1 1 xsd:boolean xsd:boolean
cacontology-tactical:targetCount owl:DatatypeProperty Number of individuals targeted for arrest.
sh:message Arrest operation must target between 1 and 50 individuals.; Target count should be between 1 and 100.
0, 1 1 xsd:nonNegativeInteger
sh:minInclusive 1
sh:maxInclusive 100, 50
xsd:nonNegativeInteger
cacontology-tactical:weaponsExpected owl:DatatypeProperty Whether weapons were expected during arrest.
sh:message Arrest operation must specify if weapons are expected.
1 1 xsd:boolean xsd:boolean
rdfs:label --
sh:message Arrest operation should have a label.
0 1 rdf:langString --
uco-core:startTime --
sh:message May specify the arrest operation time.
0 1 xsd:dateTime --
cac-core:InvestigativeAction
gufo:hasBeginPointInXSDDateTimeStamp -- begin time
0 1 xsd:dateTimeStamp --
gufo:hasEndPointInXSDDateTimeStamp -- end time
0 1 xsd:dateTimeStamp --
rdfs:label -- label
1 * xsd:string --
cac-core:Event
(cacontology-forensics:examinedBy | cacontology-forensics:performedBy | cacontology-forensics:witnessedBy | cacontology-forensics:authorizedBy) --
sh:message Every forensic event must have at least one participant (gUFO participation)
1 * --
(cacontology-grooming:targetsVictim | cacontology-grooming:performedBy | cacontology-grooming:witnessedBy | cacontology-grooming:facilitatedBy) --
sh:message Every grooming event must have at least one participant (gUFO participation)
1 * --
(cacontology-usa-federal:prosecutedBy | cacontology-usa-federal:investigatedBy | cacontology-usa-federal:defendedBy | cacontology-usa-federal:victimizedBy) --
sh:message Every federal criminal event must have at least one participant
1 * --
(gufo:hasBeginPointInXSDDateTimeStamp | cacontology-enterprises:hasCoercionEventBeginDate | cacontology-enterprises:hasInvestigationBeginDate) --
sh:message gUFO Events must have at least one temporal beginning point.
1 * --
gufo:hasBeginPointInXSDDateTimeStamp -- begin time
Optional temporal begin point for the event.
sh:message Event can have at most one begin point; Forensic action must have at most one begin timestamp (gUFO temporal constraint); Grooming behavior must have at most one begin timestamp (gUFO temporal); Production event must have exactly one begin point.
1 1 xsd:dateTimeStamp --
gufo:hasEndPointInXSDDateTimeStamp -- end time
Optional temporal end point for the event.
sh:message Event can have at most one end point; Forensic action must have at most one end timestamp (gUFO temporal constraint); Grooming behavior must have at most one end timestamp (gUFO temporal); Production event may have an end point.
0 1 xsd:dateTimeStamp --
rdfs:label -- label
Every event should have at least one human-readable label.
1 * xsd:string --
case-investigation:InvestigativeAction
uco-action:endTime --
sh:message When present, action endTime should be at most one xsd:dateTime literal.
0 1 xsd:dateTime
sh:severity sh:Warning
--
uco-action:object --
sh:message Action must reference at least one object IRI.
1 * sh:IRI
sh:severity sh:Violation
--
uco-action:performer --
sh:message Action must have exactly one performer IRI.
1 1 sh:IRI
sh:severity sh:Violation
--
uco-action:result --
sh:message When present, action result values should be IRI nodes.
0 * sh:IRI
sh:severity sh:Warning
--
uco-action:startTime --
sh:message Action must have exactly one startTime (xsd:dateTime).
1 1 xsd:dateTime
sh:severity sh:Warning
--
uco-action:Action
uco-action:endTime --
sh:message When present, action endTime should be at most one xsd:dateTime literal.
0 1 xsd:dateTime
sh:severity sh:Warning
--
uco-action:object --
sh:message Action must reference at least one object IRI.
1 * sh:IRI
sh:severity sh:Violation
--
uco-action:performer --
sh:message Action must have exactly one performer IRI.
1 1 sh:IRI
sh:severity sh:Violation
--
uco-action:result --
sh:message When present, action result values should be IRI nodes.
0 * sh:IRI
sh:severity sh:Warning
--
uco-action:startTime --
sh:message Action must have exactly one startTime (xsd:dateTime).
1 1 xsd:dateTime
sh:severity sh:Warning
--

Implementation

@prefix cac-core: <https://cacontology.projectvic.org/core#> .
@prefix cacontology-tactical: <https://cacontology.projectvic.org/tactical#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
cacontology-tactical:ArrestOperation a owl:Class ;
    rdfs:label "Arrest Operation"@en ;
    rdfs:comment "Law enforcement operation to apprehend and take suspect into custody. Extends investigation:InvestigativeAction for proper CASE ontology integration."@en ;
    rdfs:subClassOf cac-core:InvestigativeAction .