Pattern for ModelType "RelationshipElement" is ambiguous

[sebbader-sap]

What?

JSON Schema defines the "modelType" for "RelationshipElement" as "const": "RelationshipElement", which for the Part 1 domain was translated to "pattern": "RelationshipElement".
This however also maps to "modelType": "AnnotatedRelationshipElement", therefore a validator compares an instance of "AnnotatedRelationshipElement" against the schema for "RelationshipElement".

How?

Possible solutions, sorted by preference:

A) Check if "pattern" in OpenAPI can be replaced with "const"

B) Change "pattern": "RelationshipElement" to "pattern": "^RelationshipElement$" also for all other SubmodelElements / all "modelType" attributes.

C) Change "pattern": "RelationshipElement" to "pattern": "^RelationshipElement$" only.

[sebbader-sap]

With Bugfix 3.0.2, Option B has been introduced already. I propose to keep the usage of pattern: "^<ModelType>$", even though the aas.json declares it as "cons": "<ModelType>".

[sebbader-sap]

• @sebbader-sap adjust the V3.1 Part 1 Domain YAML with pattern: "^<ModelType>$"
• @sebbader-sap also check for the Part 2 YAML