Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AdministrativeInformation: add createdAt and updatedAt attributes #484

Open
BirgitBoss opened this issue Nov 15, 2024 · 2 comments
Open
Labels
ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Milestone

Comments

@BirgitBoss
Copy link
Collaborator

BirgitBoss commented Nov 15, 2024

Is your feature request related to a problem? Please describe.
There are requirements requesting search capabilities via date or date ranges an AAS or Submodel was created, see for example admin-shell-io/aas-specs-api#176 or eclipse-tractusx/sldt-digital-twin-registry#466

Additionally we also need administrative information for AssetAdministrationShellDescriptors (for SubmodelDescriptors it might not be needed).

Note: AssetAdministrationShellDescriptor/administration is the administrative information for the AssetAdministrationShell, not for the Descriptor.

Describe the solution you'd like
Add the following optional attributes to AdministrativeInformation:

  • createdAt
  • updatedAt

with type dateType and add

  • constraint requiring that the format is YYYY-MM-DDTHH:MM:SSZ

Add the following optional attributes to AssetAdministrationShellDescriptor:

  • descriptorCreatedAt
  • descriptorUpdatedAt

or

  • descriptorAdministration with existing type AdministrativeInformation
@BirgitBoss
Copy link
Collaborator Author

In admin-shell-io/aas-specs-api#346 only creationsDate is requested but not updateDate

@BirgitBoss
Copy link
Collaborator Author

2024-11-27 TF AAS Metamodel
change request approved, it makes sense to include creation and updateDate in the metamodel

@BirgitBoss BirgitBoss added ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream and removed requires workstream approval strategic decision proposal needs to be prepared in TF spec team labels Nov 27, 2024
@BirgitBoss BirgitBoss modified the milestones: V3.1, V3.x Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Projects
None yet
Development

No branches or pull requests

1 participant