- if the ID is intended to be opaque then the vendor shouldn't document it as a UUID, as this changing to a different format would be a breaking change
- if the customer isn't going to process the subcomponents of the UUID then they should process it as an opaque string
- if the UUID library encounters a version number in a UUID it doesn't understand, it shouldn't reject the UUID but present it as an unstructured string.
After this blog post it seems likely that even Kite more customer will parse the IDs to extract time, since this has been documented.
- if the ID is intended to be opaque then the vendor shouldn't document it as a UUID, as this changing to a different format would be a breaking change
- if the customer isn't going to process the subcomponents of the UUID then they should process it as an opaque string
- if the UUID library encounters a version number in a UUID it doesn't understand, it shouldn't reject the UUID but present it as an unstructured string.
After this blog post it seems likely that even Kite more customer will parse the IDs to extract time, since this has been documented.