First data type schemas

[UlrikeS91]

adjusted draft of #523

[UlrikeS91]

@Peyman-N, @apdavison and @lzehl I will keep it as a draft for now, but the content is ready for review. Except for one new ControlledTerms terminology*, everything should be functional in the existing framework. Meaning the coordinateSpace still points to the old setup. This will need to be updated when we do the SANDS updates.

I restructured the content from the issue since it seems like several image types share properties (which makes sense).

The schemas are structured the following way:

• 'Image':

  • concept schema
  • contains info about coordinate space and file compression
  • has a lookup label and additional remarks

• 'RasterBasedImage' and 'VectorBasedImage':

  • concept schemas
  • extend 'Image'
  • contain some similar properties: data location & dimension
  • but had to be split due to their inherent differences (vectors are scalable)
  • 'RasterBasedImage' additionally contains device used capture image, color depth and resolution
  • 'VectorBasedImage' additionally contains software used to create image

• specific raster-based images restrict some of the inherited properties and define additional ones:

  • 'RasterGraphic'
  • 'Volume'
  • 'ImageStack'

• specific vector-based images restrict some of the inherited properties and define additional ones:

  • 'VectorGraphic'
  • 'PolygonalMesh'

• new terminology is on 'Image', called 'ImageCompressionType' (e.g., LZW, RLE, JPEG), this could also be solved by defining the value as 'core:Technique' (or 'core:AnalysisTechnique', not sure) since this is basically what is happening - a method applied to the file to reduce the size of the file

Looking forward to discussing this draft 🙂