|
|
|
|
|
|
by PaulHoule
1459 days ago
|
|
|
The URI resolution idea is 99% crap. That is, most of the time you don't want to publish subjects and predicates as resolvable URIs. However, people see so many examples of http:... that they don't release it's even possible to make non-resolvable URIs. I used random UUIDs all the time but that is a super-fraught area since some people really want them to be in temporal sequence so their database index is happy. I've also done the content addressable blob store thing. |
|
|
32 bit millisecond timestamp that just rolls over, i.e. truncate(current_time_ms()), concatenated with 96 bytes of crypto grade entropy.
You get both nice properties, database index locality + proper entropy that you can sleep well and not worry about collisions (since the entire timestamp space will get more densely populated with every overflow (roughly every 50 days)).
It's also what PostgreSQL uses for it's index friendly UID format. :D