Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Submodel Reference not correct #28

Closed
BirgitBoss opened this issue Feb 12, 2024 · 3 comments · Fixed by #173
Closed

[BUG] Submodel Reference not correct #28

BirgitBoss opened this issue Feb 12, 2024 · 3 comments · Fixed by #173
Assignees
Labels
bug Something isn't working

Comments

@BirgitBoss
Copy link
Contributor

BirgitBoss commented Feb 12, 2024

To Reproduce
Steps to reproduce the behavior:

  1. download https://github.com/admin-shell-io/submodel-templates/blob/main/published/Carbon%20Footprint/0/9/IDTA%202023-0-9%20_Template_CarbonFootprint.aasx
  2. import to explorer
  3. create new AAS and add a reference to the existing Submodel CarbonFootprint
  4. save as "xml"

The new reference looks like this:

      <submodels>
        <reference>
          <type>ExternalReference</type>
          <keys>
            <key>
              <type>Submodel</type>
              <value>https://admin-shell.io/idta/CarbonFootprint/CarbonFootprint/0/9</value>
            </key>
          </keys>
        </reference>
      </submodels>

but should look like this (ModelReference instead of ExternalReference):

      <submodels>
        <reference>
          <type>ModelReference</type>
          <keys>
            <key>
              <type>Submodel</type>
              <value>https://admin-shell.io/idta/CarbonFootprint/CarbonFootprint/0/9</value>
            </key>
          </keys>
        </reference>
      </submodels>

Version used: v2024-01-15, Build date: Mon 01/15/2024

@JS-Aibel
Copy link

I do not know if it is relevant or related to your issue, but this also happens when adding a reference to an existing Concept Description. The semantic id reference on the property becomes an “ExternalReference”. #11 (comment)

@BirgitBoss
Copy link
Contributor Author

I am not sure: here it is the combination of ExternalReference and Submodel that is not ok. The Metamodel requires a model reference.
For concept descriptions it is recommended to use external references (I.e. the key in this case is GlobalReference).

@juileetikekar
Copy link
Contributor

Hi @BirgitBoss,

Thank you for raising the issue!! The fix will be provided as soon as possible.

@juileetikekar juileetikekar self-assigned this Feb 27, 2024
@juileetikekar juileetikekar linked a pull request Feb 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants