model.submodel: Implement AASd-129 and AASd-119

[s-heppner]

Constraint AASd-129: If any Qualifier/kind value of a SubmodelElement/qualifier (attribute qualifier inherited
via Qualifiable) is equal to TemplateQualifier, the submodel element shall be part of a submodel template,
i.e. a Submodel with Submodel/kind (attribute kind inherited via HasKind) value equal to Template.

Any suggestions as to how to implement this?

In the same step, we should probably also implement AASd-119:

If any Qualifier/kind value of a Qualifiable/qualifier is equal to TemplateQualifier and
the qualified element inherits from "hasKind", the qualified element shall be of kind Template (HasKind/kind =
"Template").

[s-heppner]

When adding a Qualifiable to a namespace, walk up the parent until the Identifiable, then check that Identifiable's type

[zrgt]

It's very complicated to implement the AASd-129. I doubt that we should implement it.

We must verify this constraint whenever we:

• Change qualifier.kind value
• Set a new parent of a qualifier
• Set a new parent of any of qualifier grand-/parents (including the SubmodelElement it belongs to and all SubmodelElementCollections in the hierarchy above)

[jkhsjdhjs]

Hmm, we could easily implement the following:

• Change qualifier.kind value
• Set a new parent of a qualifier

But the last one:

• Set a new parent of any of qualifier grand-/parents (including the SubmodelElement it belongs to and all SubmodelElementCollections in the hierarchy above)

would require iterating all child SubmodelElements and their qualifiers whenever a new SubmodelElementCollection or SubmodelElementList is added. This wouldn't necessarily be a problem, but would need to be enforced for every NamespaceSet of every SubmodelElement containing other SubmodelElements (e.g. SubmodelElementList / SubmodelElementCollection).

[s-heppner]

We decided not to implement this due to the issue in the comment above.

[s-heppner]

However, we need to document this for the v3.0 Release

[zrgt]

However, we need to document this for the v3.0 Release

@s-heppner the issue can be closed. The reasults are documented in #156