Skip to content

Add GetAssetAdministrationShellVersionByIdAndDate and GetSubmodelVersionByIdAndDate#540

Open
sebbader-sap wants to merge 4 commits intoIDTA-01002-3-2_workingfrom
SeBa/get-aas-and-sm-version-by-id-and-date
Open

Add GetAssetAdministrationShellVersionByIdAndDate and GetSubmodelVersionByIdAndDate#540
sebbader-sap wants to merge 4 commits intoIDTA-01002-3-2_workingfrom
SeBa/get-aas-and-sm-version-by-id-and-date

Conversation

@sebbader-sap
Copy link
Contributor

No description provided.

@CLAassistant
Copy link

CLAassistant commented Feb 27, 2026

CLA assistant check
All committers have signed the CLA.

@sebbader-sap sebbader-sap changed the base branch from main to IDTA-01002-3-2_working February 27, 2026 14:12
@sebbader-sap sebbader-sap added this to the 3.2 milestone Feb 28, 2026
Copy link
Member

@aaronzi aaronzi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The OpenAPI yaml files look good to me. But on the documentation side, I'm missing the following two things:

  1. Which field in the AAS (or underlying database) is used to find an AAS/Submodel by date? Is it createdAt or updatedAt from the new administrative-information in the metamodel or is this just a field that exists on the server but not in the AAS itself?
  2. What happens if an AAS/Submodel is not found based on the given date? Is the most recent version from before that given date returned or a 404?

And a general remark here. Is it expected that when a new AAS/Submodel is created or updated that the server sets the createdAt and updatedAt fields on it's own or is just the user input used no matter if the given dates make actual sense? Should access rules be used here to only allow setting the createdAt during AAS/Submodel creation and updatedAt when the AAS/Submodel are updated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants