I have to create an UUID and wanted to use the UUIDGenerator. My XSD File has defined the UUID as an ID which may not start with a number. The UUIDGenerator put a number at the front though and I see no way of modifying it. Why is this? and how should I best generator an ID otherwise?
Page 1 / 1
Your XSD is wrong ;-) A GUID starting with any hexadecimal digit m0-9a-z] is perfectly valid.
You can't modify the UUIDGenerator, but you can use e.g. an AttributeCreator with the following expression to replace the first character with an 'a':
a@Substring(@Value(_uuid),1,35)In addition to @david_r 's comment:
It's possible if you're Doctor Who (or have access to a TARDIS or other form of time travel). The first part of a UUID is timestamp-based...
In addition to @david_r 's comment:
It's possible if you're Doctor Who (or have access to a TARDIS or other form of time travel). The first part of a UUID is timestamp-based...
In addition to @david_r 's comment:
It's possible if you're Doctor Who (or have access to a TARDIS or other form of time travel). The first part of a UUID is timestamp-based...
However, a UUID can still start with a number and be valid...
Your XSD is wrong ;-) A GUID starting with any hexadecimal digit m0-9a-z] is perfectly valid.
You can't modify the UUIDGenerator, but you can use e.g. an AttributeCreator with the following expression to replace the first character with an 'a':
a@Substring(@Value(_uuid),1,35)
It depends on the implementation. For example, the Python uuid module supports 4 different ways of generating a GUID, of which only uuid1() is based on a timestamp (well, a clock sequence at least).
identifier is created from a combination of the computer's hardware
characteristics, the current time, and a sequence number." - not sure which variation uses those three items. Can't find anything else with a quick look through our internal systems.