-
Notifications
You must be signed in to change notification settings - Fork 26
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
Inconsistent naming of DataSpecificationIec61360 #263
Comments
This also affects the following elements
|
Yes, this seems to be inconsistent and should be fixed. @sebbader-sap @s-heppner : we then also need a new release |
This was referenced Apr 13, 2023
Correct, will take a look together with @s-heppner |
mristin
added a commit
to aas-core-works/aas-core-codegen
that referenced
this issue
Apr 18, 2023
We change naming in V3 for RDF & SHACL to be consistent with XSD, and also to make life easier for downstream clients. See: admin-shell-io/aas-specs#263
mristin
added a commit
to aas-core-works/aas-core-codegen
that referenced
this issue
Apr 18, 2023
We change naming in V3 for RDF & SHACL to be consistent with XSD, and also to make life easier for downstream clients. See: admin-shell-io/aas-specs#263
mristin
added a commit
to aas-core-works/aas-core3.0-testgen
that referenced
this issue
Apr 18, 2023
We changed the naming in aas-core-codegen to be consistent with XML, and also to make the life easier for the downstream clients. See: admin-shell-io/aas-specs#263 We update the development requirements to and re-generate everything with [aas-core-codegen 2587a3f]. [aas-core-codegen 2587a3f]: aas-core-works/aas-core-codegen@2587a3f
mristin
added a commit
to aas-core-works/aas-core3.0-testgen
that referenced
this issue
Apr 18, 2023
We changed the naming in aas-core-codegen to be consistent with XML, and also to make the life easier for the downstream clients. See: admin-shell-io/aas-specs#263 We update the development requirements to and re-generate everything with [aas-core-codegen 2587a3f]. [aas-core-codegen 2587a3f]: aas-core-works/aas-core-codegen@2587a3f
s-heppner
added a commit
that referenced
this issue
Apr 19, 2023
Prior, the naming scheme of the RDF and SHACL schemata were inconsistent to the JSON and XML schemat in their naming of abbreviations. This fixes it by applying the same naming rules on the RDF and SHACL schemata. Furthermore we update the examples. This fixes #263
2 tasks
Solved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the V3-schemas for JSON and XML use the spelling
DataSpecificationIec61360
. However, the schemas in RDF and SHACL use the spellingDataSpecificationIEC61360
. This difference is not only inconsistent and therefore impractical in itself. It ripples on and breaks the AAS4J serializers.Therefore, I suggest to adjust the naming to
DataSpecificationIec61360
in RDF and SHACL as well.The text was updated successfully, but these errors were encountered: