[Rats] Does EAT's $JSON-Selector need a registry?

[Thomas Fossati <[e-mail]>]

Hi,

In EAT, the $JSON-Selector socket is extensible.

EAT defines a few initial types for the $JSON-Selector's type, such as
"BUNDLE" and "JWT", along with their associated semantics, while also
allowing other specifications to extend the socket.

How is the extension process handled since there is no registry to
coordinate it?

Would an "Updates/Extends: $EAT_RFC_NUMBER" tag (and associated prose)
from the extending spec be sufficient?

cheers, thanks
t

PS: In hindsight, using media type strings for types (e.g.,
"application/jwt" rather than "JWT") may have been a better choice.