Based on personal experience in the libraries I have been writing already that do much of this and discussions with @smizzel, I would like to propose the following for the initial focus:
Define interface and write "Representor" library with associated Builder.
Define interface and write Serializer and Deserializer Class Pairs for HAL and Siren.
Actually, these are done in tandem the second, refining the first (or at least the internal implementation of the representor object).
We could set up a standard set of fixtures for each use in each of the languages for testing. I am not proposing writing the whole serialization factor/functionality. I know there was discussion about just writing the "Representor" and associated builder classes, but we can write this to do anything. Whether it supports serializing and deserializing media types is the real proof test.
Based on personal experience in the libraries I have been writing already that do much of this and discussions with @smizzel, I would like to propose the following for the initial focus:
Actually, these are done in tandem the second, refining the first (or at least the internal implementation of the representor object).
We could set up a standard set of fixtures for each use in each of the languages for testing. I am not proposing writing the whole serialization factor/functionality. I know there was discussion about just writing the "Representor" and associated builder classes, but we can write this to do anything. Whether it supports serializing and deserializing media types is the real proof test.