Composite ID inside the resource object

As the application I am currently working on is stateless facade and there is no way to persist a surrogate key - I am going to use id as an irrelevant “write-only” value in order to be compliant with the current spec.
However, I consider it a workaround for the fact that spec doesn’t support aggregate entities with composite keys, which are perfectly normal way to model things.