https://unifiedcyberontology.org/ontology/uco/observable#WindowsFilemapping
A Windows file mapping is the association of a file's contents with a portion of the virtual address space of a process within a Windows operating system. The system creates a file mapping object (also known as a section object) to maintain this association. A file view is the portion of virtual address space that a process uses to access the file's contents. File mapping allows the process to use both random input and output (I/O) and sequential I/O. It also allows the process to work efficiently with a large data file, such as a database, without having to map the whole file into memory. Multiple processes can also use memory-mapped files to share data. Processes read from and write to the file view using pointers, just as they would with dynamically allocated memory. The use of file mapping improves efficiency because the file resides on disk, but the file view resides in memory.[based on https://docs.microsoft.com/en-us/windows/win32/memory/file-mapping]
Instances of observable:WindowsFilemapping can have the following properties:
PROPERTY |
MIN COUNT |
MAX COUNT |
TYPE |
|
|---|---|---|---|---|
| observable:ObservableObject | ||||
| observable:hasChanged | 0 | 1 |
xsd:boolean
|
|
| observable:state | 0 | 1 |
xsd:string
|
|
| core:UcoObject | ||||
| core:createdBy | 0 | 1 |
core:IdentityAbstraction
|
|
| core:description | 0 | * |
xsd:string
|
|
| core:externalReference | 0 | * |
core:ExternalReference
|
|
| core:hasFacet | 0 | * |
core:Facet
|
|
| core:id | 0 | 1 |
types:Identifier
|
|
| core:modifiedTime | 0 | * |
xsd:dateTime
|
|
| core:name | 0 | 1 |
xsd:string
|
|
| core:objectCreatedTime | 0 | 1 |
xsd:dateTime
|
|
| core:objectMarking | 0 | * |
core:MarkingDefinitionAbstraction
|
|
| core:specVersion | 0 | 1 |
xsd:string
|
|
| core:tag | 0 | * |
xsd:string
|
|
| core:type | 0 | * |
xsd:string
|
|
@prefix observable: <https://unifiedcyberontology.org/ontology/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:WindowsFilemapping a owl:Class,
sh:NodeShape ;
rdfs:label "WindowsFilemapping"@en ;
rdfs:comment "A Windows file mapping is the association of a file's contents with a portion of the virtual address space of a process within a Windows operating system. The system creates a file mapping object (also known as a section object) to maintain this association. A file view is the portion of virtual address space that a process uses to access the file's contents. File mapping allows the process to use both random input and output (I/O) and sequential I/O. It also allows the process to work efficiently with a large data file, such as a database, without having to map the whole file into memory. Multiple processes can also use memory-mapped files to share data. Processes read from and write to the file view using pointers, just as they would with dynamically allocated memory. The use of file mapping improves efficiency because the file resides on disk, but the file view resides in memory.[based on https://docs.microsoft.com/en-us/windows/win32/memory/file-mapping]"@en ;
rdfs:subClassOf observable:ObservableObject ;
sh:targetClass observable:WindowsFilemapping .