Inheritance Relationship Missing in JSON Schema Between Abstract and EO-Specific Classes

In the conceptual model defined in TDML Part 1, AI_EOTrainingDataset is derived from AI_AbstractTrainingDataset (and similarly for AI_EOTrainingData → AI_AbstractTrainingData, and AI_EOTask → AI_AbstractTask).

However, in the corresponding JSON Schemas, this inheritance relationship is not explicitly declared. For example:

https://schemas.opengis.net/trainingdml-ai/part2/1.0/ai_trainingDataset.json

https://schemas.opengis.net/trainingdml-ai/part2/1.0/ai_eoTrainingDataset.json

Although JSON Schema does not natively support inheritance, it can be modeled indirectly using keywords such as allOf or oneOf. See the following reference for details:
https://json-schema.org/blog/posts/modelling-inheritance#representing-our-models-using-constraints

Impact on Conformance Testing

This missing inheritance representation leads to issues in the conformance test implementation. Specifically:

Item withtype="AI_EOTrainingDataset" is not recognized as AI_AbstractTrainingDataset

Since ai_trainingDataset.json requires the type field to be AI_AbstractTrainingDataset, any file whose type is AI_EOTrainingDataset will fail Abstract Test 11 in TDML Part 2.

Related issue:
https://github.com/opengeospatial/ets-trainingdmlai10-part2/issues/35

Start by comparing ai_trainingDataset.json and ai_eoTrainingDataset.json at the linked schemas.opengis.net URLs, then read the JSON Schema inheritance reference and Abstract Test 11 in the issue. Check the related ets-trainingdmlai10-part2 issue for context. Done means EO-specific types are recognized as their abstract types and the affected conformance test passes.