https://ontology.unifiedcyberontology.org/uco/observable/WindowsCriticalSection
A Windows critical section is a Windows object that provides synchronization similar to that provided by a mutex object, except that a critical section can be used only by the threads of a single process. Critical section objects cannot be shared across processes. Event, mutex, and semaphore objects can also be used in a single-process application, but critical section objects provide a slightly faster, more efficient mechanism for mutual-exclusion synchronization (a processor-specific test and set instruction). Like a mutex object, a critical section object can be owned by only one thread at a time, which makes it useful for protecting a shared resource from simultaneous access. Unlike a mutex object, there is no way to tell whether a critical section has been abandoned. [based on https://docs.microsoft.com/en-us/windows/win32/sync/critical-section-objects]
Instances of observable:WindowsCriticalSection can have the following properties:
PROPERTY |
MIN COUNT |
MAX COUNT |
TYPE |
|
|---|---|---|---|---|
| observable:ObservableObject | ||||
| observable:hasChanged | 1 |
xsd:boolean
|
||
| observable:state | 1 |
xsd:string
|
||
| core:UcoObject | ||||
| core:createdBy | 1 |
core:IdentityAbstraction
|
||
| core:description |
xsd:string
|
|||
| core:externalReference | 0 |
core:ExternalReference
|
||
| core:hasFacet |
core:Facet
|
|||
| core:modifiedTime |
xsd:dateTime
|
|||
| core:name | 1 |
xsd:string
|
||
| core:objectCreatedTime | 1 |
xsd:dateTime
|
||
| core:objectMarking |
core:MarkingDefinitionAbstraction
|
|||
| core:specVersion | 1 |
xsd:string
|
||
| core:tag |
xsd:string
|
|||
@prefix observable: <https://ontology.unifiedcyberontology.org/uco/observable/> .
@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#> .
observable:WindowsCriticalSection a owl:Class,
sh:NodeShape ;
rdfs:label "WindowsCriticalSection"@en ;
rdfs:comment "A Windows critical section is a Windows object that provides synchronization similar to that provided by a mutex object, except that a critical section can be used only by the threads of a single process. Critical section objects cannot be shared across processes. Event, mutex, and semaphore objects can also be used in a single-process application, but critical section objects provide a slightly faster, more efficient mechanism for mutual-exclusion synchronization (a processor-specific test and set instruction). Like a mutex object, a critical section object can be owned by only one thread at a time, which makes it useful for protecting a shared resource from simultaneous access. Unlike a mutex object, there is no way to tell whether a critical section has been abandoned. [based on https://docs.microsoft.com/en-us/windows/win32/sync/critical-section-objects]"@en ;
rdfs:subClassOf observable:ObservableObject ;
sh:targetClass observable:WindowsCriticalSection .