Open wznira opened 1 year ago
I agree partially with @wznira. The only difference is that I think a Representation would be a Payload specialization. Even the Representation being composed by many features, as you sad @wznira, it'd be considered only one representation of a data body that could be composed by many "data entity". Talking about the example you sad, I believe the Payload (Representation) would carry a complex data object with Aeronautical and Weather information.
The diagram with this change:
In SDCM REST Extension, we had a class structure as shown in the diagram below -
I believe we should have similar relationships between Resource, Representation, Payload and Data Classes -
en/us
.Diagram below may be applicable -