add randomUUID method

[bcoe]

Merge sections from https://github.com/WICG/uuid describing randomUUID()
method.

Refs: WICG/uuid#27

---

Preview | Diff

[twiss]

Hey 👋 Thanks for the PR!
The syntax for referencing external concepts used here is a bit different than the rest of the spec, so I wanted to suggest some changes, but ran into some issues with respec, so I'll update our usage of respec first and then rebase and review this PR afterwards, if you don't mind.

[bcoe]

so I'll update our usage of respec first and then rebase and review this PR afterwards

@twiss sounds great, I'm still learning the ins and outs of the respec syntax, so appreciate the direction.

[twiss]

I'm not an expert on ReSpec either 😅 But as long as we end up with a consistent document I'm happy :)

[twiss]

Hey 👋 I've rebased this PR, and made some editorial changes (mainly to bring the style more in line with the rest of the spec), and pushed them to the branch - let me know if you have any objections to these.

I've also somewhat simplified the wording for getting 16 random bytes - even though that brings it less in line with getRandomValues instead of more, but getRandomValues was explicitly written to support multiple types of TypedArrays, whereas that isn't necessary here.

Finally, this PR uses |foo| whereas the rest of the spec uses <var>foo</var>, but I like the former more so I've left it as is, probably we should update the rest of the spec to match after merging this, though :)

[bcoe]

I've also somewhat simplified the wording for getting 16 random bytes - even though that brings it less in line with getRandomValues instead of more, but getRandomValues was explicitly written to support multiple types of TypedArrays, whereas that isn't necessary here.

@twiss I like this change 👍

Hey 👋 I've rebased this PR, and made some editorial changes (mainly to bring the style more in line with the rest of the spec), and pushed them to the branch - let me know if you have any objections to these.

Thank you for doing this 👏

For next steps, I'm assuming we should leave in draft until discussions take place regrading Web Crypto's charter? (CC: @marcoscaceres).

[bcoe]

@twiss @annevk just checking in, I think this continues to be blocked on the 2021 charter? (any updates for someone who's not tuned into w3c governance.)

[annevk]

Yeah, @samuelweiler would be better equipped to talk about that.

[marcoscaceres]

Progress on the recharter can be tracked here:
w3c/strategy#253

In the meantime, it's fine to do the final reviews and we should just merge this.

We can regenerate the editor's draft here on Github for now and republish "officially" on /TR/ once the rechartering actually happens.

[annevk]

This still looks good, but I have a style nit you might want to address before landing.

[twiss]

Thanks again for all the work here! 😊