microsoft
Provide guidance on how GUIDs are used throughout the spec...
In the LRO meeting, we realized during the operation-id discussion on #353 that how GUIDs are handled varies and could present some challenges. This issue isn't isolated to operation-id but rather can surface anywhere a GUID is used, and potentially represented/treated as a string. We need to provide more clarity on how GUIDs should be treated.
From Shawn:
I can relate to all of the concerns being voiced here. I've had to find a way to generate a uuid when the language being used doesn't support it. I'd say that I'd prefer a string value over a uuid. Gives me the ability to use a value that aligns to my domain space, if that value happens to be a uuid, I'd convert it to a string, if the service is comparing the value as string, and I'm providing it I don't know that I would understand what the issue is.