#591_StateOfCharge_not_available_when_polling#599
Conversation
…rmation. Moved assetInfo to the core.
edwinvandenbelt
left a comment
edwinvandenbelt
left a comment
There was a problem hiding this comment.
It shouldn't have an id (assetInfo). This makes it traceable. Use the legId instead.
| type: object | ||
| description: asset status information | ||
| properties: | ||
| id: |
There was a problem hiding this comment.
This should be a legId. The TO and MP know how to derive the assetId from the legId. This way, we avoid the problem of traceablity.
There was a problem hiding this comment.
Is it really necessary to hide the asset id in the response?
What is returned here: The MP calling this endpoint get's all the assets that were assigned to legs which were created on behalf of the calling MP.
summary: >-
Retrieve asset info for assets that are assigned to a leg. Only legs
are included that were created on behalf of the calling party.
So the MP only get's the info for assets which he initially requested to be booked. So he does not gain more info about assets compared to what he should already know. I don't think it's necessary to hide the asset info here.
2 participants
Added new enpoint /collections/asset-info/items to provide asset information. Moved assetInfo to the core.