On 5/22/25 02:08, Pawel Kowalik wrote:
I would also not put too much value to prefixes. Typically the frameworks require full name anyway to access the object or to map it to a programming language representation. Actually I would be in favour of restoring the text of -04 2.4.5 with an explicit update to RFC9083 allowing the bare identifier pattern (which also would solve the issue of justification when SHOULD NOT could be broken and DE review interpretation issue). Contrary to other cases brought up by Andy (I-JSON, Unichars) I think this update would be OK in this draft, as it only affects extensions.
I have written up a proposed compromise: https://github.com/anewton1998/draft-regext-rdap-extensions/compare/main...allow-bare -andy _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
