data format individuals #2205

[stap-m]

Summary of the discussion

Based on #2205
Adding image data formats as individuals for text file format and binary file format

Type of change (CHANGELOG.md)

Add

• CSV, JSON, CPACS, KML, BADA, VTK as subclass of text file format
• NETCDF, SO6, GeoTiffs as subclass of binary file format

Workflow checklist

Automation

Closes #2205

PR-Assignee

• 🐙 Follow the Pull Request Workflow
• 📝 Update the CHANGELOG.md
• 📙 Add #'s to term tracker annotation

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[github-actions]

Changed axioms per ontology

Note: Changes in term tracker annotations are not displayed

oeo-model.omn: 34 changes

Ontology comparison

Left

• Ontology IRI: https://openenergyplatform.org/ontology/oeo/oeo-model/
• Version IRI: https://openenergyplatform.org/ontology/oeo/dev/oeo-model.omn
• Loaded from: file:/__w/ontology/ontology/./dev/src/ontology/edits/oeo-model.omn

Right

• Ontology IRI: https://openenergyplatform.org/ontology/oeo/oeo-model/
• Version IRI: https://openenergyplatform.org/ontology/oeo/dev/oeo-model.omn
• Loaded from: file:/__w/ontology/ontology/src/ontology/edits/oeo-model.omn

Ontology imports

Ontology annotations

BADA https://openenergyplatform.org/ontology/oeo/OEO_00020481

Added

• Individual: BADA

• BADA alternative term "Base of Aircraft Data"

• BADA label "BADA"@en

• BADA Type text file format

CPACS https://openenergyplatform.org/ontology/oeo/OEO_00020479

Added

• Individual: CPACS

• CPACS definition "CPACS is an XML-based data standard for aircraft design and multidisciplinary analysis."

• CPACS alternative term "Common Parametric Aircraft Configuration Schema"

• CPACS label "CPACS"@en

• CPACS Type text file format

CSV https://openenergyplatform.org/ontology/oeo/OEO_00020476

Added

• Individual: CSV

• CSV definition "CSV is a simple text-based file format. Each line represents a row, and values are separated by delimiters (commonly commas)."

• CSV alternative term "Comma-Separated Values"@en

• CSV label "CSV"@en

• CSV Type text file format

GeoTiff https://openenergyplatform.org/ontology/oeo/OEO_00020485

Added

• Individual: GeoTiff

• GeoTiff definition "GeoTIFF is an extension of the TIFF image format that embeds geospatial information directly into the image file."

• GeoTiff alternative term "Georeferenced Tagged Image File Format"@en

• GeoTiff label "GeoTiff"@en

• GeoTiff Type data file format

JSON https://openenergyplatform.org/ontology/oeo/OEO_00020477

Added

• Individual: JSON

• JSON definition "JSON is a lightweight text format used to represent structured and hierarchical data."

• JSON alternative term "JavaScript Object Notation"@en

• JSON label "JSON"@en

• JSON Type text file format

KML https://openenergyplatform.org/ontology/oeo/OEO_00020480

Added

• Individual: KML

• KML definition "KML is an XML-based geographic data format"

• KML alternative term "Keyhole Markup Language"@en

• KML label "KML"@en

• KML Type text file format

NetCDF https://openenergyplatform.org/ontology/oeo/OEO_00020483

Added

• Individual: NetCDF

• NetCDF definition "NetCDF is a self-describing, machine-independent binary file format designed for storing and sharing multidimensional scientific data."

• NetCDF alternative term "Network Common Data Form"@en

• NetCDF label "NetCDF"@en

• NetCDF Type binary file format

SO6 https://openenergyplatform.org/ontology/oeo/OEO_00020484

Added

• Individual: SO6

• SO6 definition "SO6 is a flight trajectory data format developed by EUROCONTROL for air traffic flow and trajectory analysis."

• SO6 alternative term "EUROCONTROL SO6 Flight Trajectory Format"@en

• SO6 label "SO6"@en

• SO6 Type binary file format

VTK https://openenergyplatform.org/ontology/oeo/OEO_00020482

Added

• Individual: VTK

• VTK definition "The VTK data format is a Standard for Scientific Data Visualization it can be ASCII or Binary"

• VTK label "VTK"@en

• VTK Type data file format

oeo.omn: 0 changes

Ontologies are identical

[stap-m]

@AhlemRhayem I started the implementation. Please provide one sentence of explanation for each file format, either as comment or directly in the ontology.
E.g. "BADA (Base of Aircraft Data) is an image file format for Aircraft Data." Something like that.

[stap-m]

Undo unintended changes

[stap-m]

I updated the individuals and added the pseudo definitions proposed in #2205 (comment).
For those individuals that can be both text or binary or image, I added them as individuals of data file format to not hurt the asserted monohierarchy.