On a Github PR XEP-0353: Add requirement for UUID v4 for id attributes by tmolitor-stud-tu · Pull Request #1262 · xsf/xeps · GitHub <https://github.com/xsf/xeps/pull/1262>, Thilo wrote:
> I think explicit is better than implicit, hence this PR. > Since v0.4 of this XEP isn't implemented by any client yet (to my knowledge) and because the XEP is still experimental, I think we can do this update without bumping the namespace. What do you thing @fippo <https://github.com/fippo> @stpeter <https://github.com/stpeter> ? [Aside: Having been bitten by conversations happening off the list, and therefore with less visibility than I (at least) would like, I'm dragging this conversation back to the list] The suggestion here is that the `id` field should be defined as being a UUIDv4, mandatorily. Also, that this doesn't need a namespace bump. I think both of these are wrong: * The argument that this doesn't need a namespace bump is wrong because "experimental" has no effect here. The entire point of those 'versioned' namespaces was to ensure that we could freely implement Experimental XEPs without worrying about causing compatibility nightmares. The argument that there's no implementation is counter-productive - if there's nobody implementing, then by definition it doesn't matter if you bump the namespace. * In general, I think ids expected to be reasonably unique ought to be UUIDv4. I mean, why not? But I'm hesitant to mandate this absolutely, such as in this change, because although I'd like *senders* to always use a UUIDv4, I'm a bit concerned about *receivers* making that assumption, and trying to parse out a UUIDv4 and storing it in a 128-bit number or something. In some cases, that'd be a handy thing (I've done this internally with MAM identifiers, for example), but I think we should be very careful about when this is the right choice. So, I'd suggest "SHOULD" here at most, and I might choose to phrase it as "RECOMMENDED", which has the same RFC 2119 meaning, but somewhat different implicit meaning in English.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
