Skip to content

Add Constraint forbidding AasReferables as value for external references #592

@BirgitBoss

Description

@BirgitBoss

Is your feature request related to a problem? Please describe.
see admin-shell-io/submodel-templates#79 (comment)

The following working example is definitely is wrong although it seems no constraint is violated

(GlobalReference)) submodel/id
(SubmodelElementCollection) smc
(File) file
(FragmentReference) tag

The following two examples are correct:

(Submodel)) submodel/id
(SubmodelElementCollection) smc
(File) file
(FragmentReference) tag
(GlobalReference) path to file
(FragmentReference) tag

Describe the solution you'd like

Add Constraint forbidding to use any element from AasReferables if the first Key equals to "GlobalReference".

Constraint AASd-xxx: For external references, i.e. References with Reference/type = ExternalReference the value of any Key/type contained in the Reference shall not be one of AasReferables.

  • add an invalid example
  • explain that to use a ModelReference instead

Although adding new constraints typically is non-backward-compatible I consider this change just to be clarification because semantically everything else does not make sense.

Metadata

Metadata

Assignees

No one assigned

    Labels

    acceptedaccepted as proposedspecificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions