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

Improvement Ideas for "GUIDELINE: HOW TO CREATE A SUBMODEL TEMPLATE SPECIFICATION", December 2022 #51

Open
foprs opened this issue Nov 29, 2023 · 0 comments

Comments

@foprs
Copy link

foprs commented Nov 29, 2023

  • Consider, how to document SubmodelElementLists in the class tables. Problem: If the lists contains SubmodelElementCollections but these SMC do not have a shortId, the shortId is missing for a class table for that indexed SMC's

  • Consider units in the class table?

  • Cardinality is e.g., [0..1] in class tables and "ZeroToOne" as Qualifier value -> Harmonize?

  • Class table has the row "Explanation:" - Why not harmonize with metamodel to "description" ?

  • sometimes there is no description (metamodel) but the definition (IEC 61360) available -> Define a description/definition@en ?

  • It is defined to use, e.g., valueType [String] not [xs:String] -> why not harmonize 1:1 with the metamodel ValueTypes?

  • With introduction of SubmodelElementListe the cardinality of [..toMany] is not need anymore?! To be reflected in the Guideline?

@foprs foprs changed the title Improvement Ideas for "GUIDELINE: HOW TO CREATE A SUBMODEL TEMPLATE SPECIFICATION" Improvement Ideas for "GUIDELINE: HOW TO CREATE A SUBMODEL TEMPLATE SPECIFICATION", December 2022 Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants