A. Pagaltzis wrote: > SHOULD is costly and should be avoided in favour of MUST or MAY > wherever possible – we had this discussion we had frequently in > the Atom WG. Over time, given enough implementations, any given > SHOULD tends to be treated as either a MAY or a MUST anyway. > > That reasoning leads me to conclude that we can reduce the cost > of this SHOULD over time by making it no formal requirement at > all for app data and a MUST for TAP metainformation right off the > bat.
I'm down with changing it to MUST for TAP meta and MAY for diagnostics. I completely missed MAY in RFC 2119. There's a misleading page break in the text version that makes it look like the list ends at SHOULD and there's nothing lower. -- Stabbing you in the face so you don't have to.
