There are a lot of different individual concerns along with ideas on how things could be solved. It would be valuable to have a concise list of these along with the current decision on what the outcome is as expressed in the current draft. It should summarize the concern/question, concisely list out the alternatives and/or the pros and cons, and the decision as currently expressed in the draft. This should make discussions about specific features very focused and avoid having to repeat the same concerns over and over. It also means that good ideas and valid concerns that are still being considered have a place they can be recorded and summarized and made easily accessible. The README for this repo is probably the appropriate place. Visible, and people can submit PRs to add things (which I will readily merge as long as they concisely include data and pros and cons and leave out the "therefore MUST do something this way" - what we need instead is "the concerns are A, B, C solution X solves A and B but not C, solution Y solves all three but introduces problem D"). If all of the data can be concisely collected, the ensuing discussions will be far more productive and then the exact reason for changes can be documented as well.
Examples of things to cover:
Should we have alternate text formats or just the existing hex with dashes.
Are we sticking with 128-bits or are we introducing variable-length
Should a sort order be defined, if so what.
Is this a solution only for globally unique IDs, or does it include locally unique IDs as well (unique within one system, not the whole planet/solar system/galaxy/universe)
There are a bunch of these and they have exact arguments for various solutions, and only a subset of that information is covered in the draft.
There are a lot of different individual concerns along with ideas on how things could be solved. It would be valuable to have a concise list of these along with the current decision on what the outcome is as expressed in the current draft. It should summarize the concern/question, concisely list out the alternatives and/or the pros and cons, and the decision as currently expressed in the draft. This should make discussions about specific features very focused and avoid having to repeat the same concerns over and over. It also means that good ideas and valid concerns that are still being considered have a place they can be recorded and summarized and made easily accessible. The README for this repo is probably the appropriate place. Visible, and people can submit PRs to add things (which I will readily merge as long as they concisely include data and pros and cons and leave out the "therefore MUST do something this way" - what we need instead is "the concerns are A, B, C solution X solves A and B but not C, solution Y solves all three but introduces problem D"). If all of the data can be concisely collected, the ensuing discussions will be far more productive and then the exact reason for changes can be documented as well.
Examples of things to cover:
There are a bunch of these and they have exact arguments for various solutions, and only a subset of that information is covered in the draft.
Related: https://github.com/bradleypeabody/gouuidv6/issues/3