[Feat. Req.] Element history endpoint

[mhrimaz]

What is missing?

Currently, it seems the only focus is on the current state of the asset. So when the object goes into the wrong state, there is no way to rewind the digital twin and check what happened in the past. See a related example in DTDL .

So this can be an example of how a Concept Description has evolved over time, and you can see the past versions of it:

How should it be fixed?

There should be an endpoint to get all the previous states of an element (Concept Description, AAS, Submodel, specific Submodel Element, ...). However, it can either be via version number, or by querying a range of dates.
In the case of continuous telemetry data, the implementation is, of course, challenging. So probably, it might be suitable to selectively activate such history recording for specific elements via a flag or something.

• I have signed the required Developer Certificate of Origin (DCO) already.

[BirgitBoss]

This kind of searching requests to extend AdministrativeInformation by creationDate and updateDate etc.

I created an issue for changed on metamodel: admin-shell-io/aas-specs#484

For a concrete proposal how to extend the existing APIs for registry and discovery see eclipse-tractusx/sldt-digital-twin-registry#466