Skip to content

Reuse of properties in several submodels #144

@empwilli

Description

@empwilli

In [If the same properties are used in several submodels, shall they also be entered several times or shall they be referenced?](https://github.com/admin-shell-io/questions-and-answers?tab=readme-ov-file#id5) ist says:

Submodels shall be as independent as possible so that they can be changed and developed separately. Consequently, the same properties shall be copied to another submodel and references shall not be used in such case. The concept description referenced in semanticId, however, should be the same.

However, with the introduction (and use, e.g. in Digital Nameplate 3.0) of DropIns (see also "Guideline: How to Create a Submodel Template Specification"), the idea of definition and reuse, even across SM boundaries, is promoted.

In my opinion, this section should either be removed, or mention DropIns as a mechanism to realize reuse. In the latter case, it may make some suggestions when DropIns are more suitable and when SMTs should provide individual definitions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions