s-heppner
s-heppner
[Page 36 of the v3.0 Part 1 specification](https://industrialdigitaltwin.org/wp-content/uploads/2023/06/IDTA-01001-3-0_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf#Page=36) mentions an equivalence relationship: > (Submodel)https://example.com/aas/1/1/1234859590 > is identical to > (GlobalReference)https://example.com/aas/1/1/1234859590 At first glance, this is logical in the sense that...
These schemata are not tested yet and are meant for reference only. They are not the offical final version.
These schemata are not tested yet and are meant for reference only. They are not the offical final version. Since the PathType does not follow RFC 8089 anymore, but the...
This can only be done once the spec is publicly released
Currently, the synchronization between [aas-core-meta](https://github.com/aas-core-works/aas-core-meta/), [aas-core-codegen](https://github.com/aas-core-works/aas-core-codegen) and [aas-core3.0-testgen](https://github.com/aas-core-works/aas-core3.0-testgen) to aas-specs is done by hand. This process is not only tedious, but also prone to errors. I suggest finding a way...
This adapts the schema files to version 3.0.1 of the specification. However, this is not an official release yet and may be subject to change. This is only meant as...
We document in the JSON and RDF schema `README` files, that we deviate from the pattern in the specification of AASd-130, due to the fact that most schema engines test...
**Describe the bug** The GitHub Action "Check title and description" fails, for example in [this PR](https://github.com/admin-shell-io/aas-specs/pull/426), even though the title and description both fulfill the requirements **Where** PRs **Additional context**...
This fixes two bugs found in schema files: # SHACL Make SHACL regex patterns follow JSON Schema ones We included the regex pattern as-is from the input which caused problems...