Add "uuid" format

[handrews]

Fixes #542.

[handrews]

(presumably, the CI build will still be segfaulting)

[Julian]

I haven't gone and re-read RFC4122, but from experience a lot of places "argue" about emitting UUIDs with or without hyphens.

IIRC the RFC says to include them in the BNF, but to me it's almost common enough to specifically call out if we intend without-hyphen to be invalid (or vice versa if we intend them to be valid).

[handrews]

@Julian thanks, good point, I don't know anything about that. Maybe I will split the "duration" change out of this so we can leave this open longer for feedback since there is a reasonable question here.

[handrews]

@Julian my inclination is to start with saying that this format indicates / optionally validates that the string strictly conforms with the ABNF in the RFC (which does include the hyphens). It's easier to relax a constraint later than add one.

Alternatively, if anyone thinks this is likely to cause problems, we can punt this until the next draft which will presumably focus on format a lot anyway. I don't consider this as important as adding duration or fixing the reference for hostname.

[Julian]

Sounds reasonable

…

On Sun, Mar 3, 2019, 20:56 Henry Andrews ***@***.***> wrote: @Julian <https://github.com/Julian> my inclination is to start with saying that this format indicates / optionally validates that the string strictly conforms with the ABNF in the RFC (which does include the hyphens). It's easier to relax a constraint later than add one. Alternatively, if anyone thinks this is likely to cause problems, we can punt this until the next draft which will presumably focus on format a lot anyway. I don't consider this as important as adding duration or fixing the reference for hostname. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#715 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUIXt4es_5-sQWfcYBBB34Taud3hIG9ks5vTH01gaJpZM4bN1DU> .