This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 35"
Jump to navigation
Jump to search
Line 16: | Line 16: | ||
both are fine if you guarantee that noone ever changes it in one | both are fine if you guarantee that noone ever changes it in one | ||
UUID. Once created it has to stay one way. .... may be brittle. .... | UUID. Once created it has to stay one way. .... may be brittle. .... | ||
+ | |||
+ | == Editors Comment == | ||
+ | |||
+ | This also is wrong. UUIDs are fixed to uppercase, RUIDs have a fixed | ||
+ | case, OID's are not susceptible to case. Noted in the spec that | ||
+ | comparison is case sensitive, and that this is ok. | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] |
Latest revision as of 04:58, 1 June 2007
Contents
Data Types Issue 35: UID Case sensitivity
Introduction
? backward compatible.
Discussion
Recommend that UIDs be considered case sensitive. Fundamentally, we should treat UIDs as strings that can simply be compared.
Cologne WGM 2007-04-30 - Motion made and approved to declare UIDs case sensitive. Closed.
Add a note that UUID's may be represented in either upper or lowercase...
uppercase or lowercase both are fine. But we can only say that both are fine if you guarantee that noone ever changes it in one UUID. Once created it has to stay one way. .... may be brittle. ....
Editors Comment
This also is wrong. UUIDs are fixed to uppercase, RUIDs have a fixed case, OID's are not susceptible to case. Noted in the spec that comparison is case sensitive, and that this is ok.
Links
Back to Data Types R2 issues