When our API was implemented we applied the constraints for member names to all members, including id, and everything was good until we had a specific resource which needed a period inside it’s id.
The values of type members MUST adhere to the same constraints as member names.
And there is referred that:
To enable an easy mapping of member names to URLs, it is RECOMMENDED that member names use only non-reserved, URL safe characters specified in RFC 3986.
However I couldn’t find any specific constraints for the id member, can anyone help me?