You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the official docker image of AAS server (eclipsebasyx/aas-server:1.3.0). However, the JSON response of AAS server is different than basyx-python-sdk JSON serialization result (Version: 0.2.2)
For example, when kind of submodel is instance there is no "kind":"Instance" in the output. In the image below you can see the structure is not consistent and this is reflected in the code too, however I don't know this is according to specification or just implementaiton difference.
And here you can see there are asset and assetRef on the left produced by AAS server. python sdk asset is equivalent to assetRef and asset is completely missing.
Is there any way to reproduce exact result of AAS server in python? or which java library should be used, basyx-java-sdk or eclipse-aas4j/aas4j or something else?
Please let me know if you require further information.
The text was updated successfully, but these errors were encountered:
Hi,
I am using the official docker image of AAS server (eclipsebasyx/aas-server:1.3.0). However, the JSON response of AAS server is different than basyx-python-sdk JSON serialization result (Version: 0.2.2)
For example, when kind of submodel is instance there is no
"kind":"Instance"
in the output. In the image below you can see the structure is not consistent and this is reflected in the code too, however I don't know this is according to specification or just implementaiton difference.And here you can see there are
asset
andassetRef
on the left produced by AAS server. python sdkasset
is equivalent toassetRef
andasset
is completely missing.Is there any way to reproduce exact result of AAS server in python? or which java library should be used, basyx-java-sdk or eclipse-aas4j/aas4j or something else?
Please let me know if you require further information.
The text was updated successfully, but these errors were encountered: