Enhancing Property Requiredness: Introducing a "Recommended" Option

[Philipp-Liedl]

Currently, the definition of a property's requiredness is limited to mandatory or optional, using an SMT/Cardinality qualifier: ZeroTo* for optional properties and OneTo* for mandatory ones (see screenshot below).

For larger submodels, such as SM PurchaseOrder, it would be beneficial to introduce an additional qualifier - "recommended" - for optional properties. This would help indicate preferred usage, improving both implementation and adoption with minimal effort for users.

IA preferred solution would be to establish a clear standard, allowing properties to be classified as mandatory, recommended, or optional.

The only alternative currently is to mention "recommended" in the property's description, which is suboptimal as it can be easily overlooked.

Current approach to set the requiredness a property, limited to mandatory (1..) or optional (0..):

[BirgitBoss]

Thanks for your finding. Up to now no qualifiers are specified in IDTA-01001. So the first step is to include it in the guideline How to create a submodel template specification

@MichaelHoffmeisterFesto : may you please have a look