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

Unexpected Behaviour of "cannot convert to String" error message #77

Open
GW1708 opened this issue Nov 28, 2024 · 2 comments
Open

Unexpected Behaviour of "cannot convert to String" error message #77

GW1708 opened this issue Nov 28, 2024 · 2 comments

Comments

@GW1708
Copy link

GW1708 commented Nov 28, 2024

This error message appears 4 times for the attached aas json model:
"cannot convert to String ..."
Example_AAS_Final.json

  • date_of_manufacture - Cannot convert to string: valueType must be xs:string
    There is no "date_of_manufacture" in the model but "DateOfManufacture". Here valueType is xs:date for value "2024-08-01". This cannot be changed because it is specified by submodel template. If changed from xs:date to xs:string the error is resolved for the validation tool.
  • firmware_version - Cannot convert to string: must be a Property
    There is no firmware_version but FirmwareVersion. Here there is no valueType but model type multi language property. This cannot be changed because it is specified by submodel template and metamodel.
  • hardware_version - Cannot convert to string: must be a Property
    see above
  • software_version - Cannot convert to string: must be a Property
    see above

It is not possible to resolve the first error message without breaking the specification, and unclear how to resolve the error message for the latter three cases.

@otto-ifak
Copy link
Collaborator

Thanks @GW1708 for your feedback. You are right, the fields are implemented wrong.
After fixing, I still get some errors for the file you provided:

Check
   Check meta model
   Check constraints
   Check submodel '0cb33d20-8378-44e7-8402-84823c4b51dd'
      Template: DigitalNameplate (https://admin-shell.io/zvei/nameplate/2/0/Nameplate)
      'CEO' is not a valid RoleOfContactPerson @ /ContactInformation/RoleOfContactPerson
      Cannot convert to lang string: no value @ /ContactInformation/Email/PublicKey
      Cannot convert to lang string: no value @ /ContactInformation/Email/TypeOfPublicKey
      Cannot convert to lang string: no value @ /ContactInformation/MiddleName
      Cannot convert to lang string: no value @ /ContactInformation/Title
      Cannot convert to lang string: no value @ /ContactInformation/FurtherDetailsOfContact

Are these errors as expected?

@otto-ifak
Copy link
Collaborator

(addressed in a355091)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants