Birgit Boss comments

Results 98 comments of


                                            Birgit Boss

Relaxation of idShort restrictions (Constraint AASd-002)

>into account with at least two characters This is exactly NOT valid, 1-letter idShorts are valid as well

Matching Strategy: Outdated equivalence of ModelReference[Submodel] and GlobalReference with same key

You are right. In "in the case of AssetAdministrationShell/submodel, the spec requires a ModelReference[Submodel] " in this case it would be a bug to use an external reference. The documentation...

Matching Strategy: Outdated equivalence of ModelReference[Submodel] and GlobalReference with same key

@joergneidig: can you please review: https://rwth-iat.github.io/aas-specs-antora/IDTA-01001/snapshot/IDTA-01001_General.html#_matching_algorithm_for_references

Handling of optional sets if elements in serializations

See also https://github.com/admin-shell-io/aas-specs/issues/412

Handling of optional sets if elements in serializations

In Annex D of IDTA-3-0, Page 134, it is stated: `“0..1" means optional. "0.." or "0..3" etc. means that the list may be either not available (null object) or empty....

enable the use of lang tags for langString

How would you express the length restrictions for these two types?

Update Contribution Guide -add chapter about release process

This is about releases and not about branch strategy but of course they are related. This is not yet well-defined.

Optional values for all SubmodelElements

TF Metamodel 2024-04-17 Discussion not yet finalized but recommendation: - at least for (Annotated)RelationshipElement make "first" and "second" optional (conformant to min and max of Range)

JSON Schema for ValueOnly-Serialization. Exception also for SubmodelElementList?

You are right, I will move it

Update Contribution Guide - assign PR to Issue

Every change needs an issue. But this is exactly the scope of the issue to define these rules.