Very curious how people are thinking about RDF/semantic technologies these days after the initial question was posed. With "Artificial Hallucinations" running rampant in the ChatGPT world, a call for more moderated/structured data may be a possible prescription which is where RDF/ST shines. While relational/no-sql continue to dominate our industry, I'm very surprised that a graphdb hasn't emerged to compete with the former given how incredibly flexible graphs are in our space.
Any good research going on with RDF/ST to call out here?
1) Are there any issues co-mingling v4 & v5 UUIDs in a single system? We would use v5 to transition the legacy systems to UUID and v4 for generating anything outside the legacy systems (new systems).
2) Per https://tools.ietf.org/html/rfc4122, "A UUID is 128 bits long, and requires no central registration process.". This implies anyone in our ecosystem can generate a UUID and probably never collide. However, are there minimum restrictions on the machine that would generate these UUIDs? For instance, I would imagine a dependable clock (eg one that doesn't reset to 1/1/1970 ever time it restarts) is necessary, but do they all have to be in sync or is some measure of skewing acceptable? Anything else?
3) Is there a list of reliable (future proof) uuid implementations we can use to cover all the major languages or are the standard libraries sufficient for v4/v5 uuid gens? We have a mix of various flavors of *nix and windows in our ecosystem.
Thank you!
Obviously I can help her but I work during the day and she's taking some time off to focus exclusively on this pivot so I don't want her to sit around waiting on me.
Does anyone have any good resources (authors/books, bloggers, youtube instructors) that they like that has an easy to understand teaching style for beginners?
TIA