Closed the-nic closed 2 years ago
Many thanks for pointing this out. We're discussing internally how to address this issue.
Due to compatibility issues, there's no easy and clean fix. However, we could combine the required information with the already existing information, i.e.:
"asset": {
"keys": [
{
"type": "Asset",
"idType": "IRI",
"value": "1030_8141_0112_5510",
"local": true
}
],
"identification": {
"idType": "IRI",
"id": "1030_8141_0112_5510"
},
"idShort": "CA",
"kind": "Instance",
"dataSpecification": [],
"modelType": {
"name": "Asset"
},
"embeddedDataSpecifications": []
}
Would this work for you?
since i am using basyx-python-sdk, I guess so, yes. As a workaround I rewrote the payload to use assetRef
.
Fixed and will be included in next release. Again, many thanks for pointing this out!
I have the following example assets in xml formal:
and a call to endpoint
/shells
returnsHowever, the fields in
asset
must be Referables, ie.See also https://github.com/eclipse-basyx/basyx-python-sdk/issues/9#issuecomment-1074420174