--On Wednesday, March 26, 2008 01:13:33 PM -0400 Barry Leiba <leiba@xxxxxxxxxxxxxx> wrote:
In particular, I don't agree with Alexey's thought that if WE can't think of an alternative value for a field, our advice should be MUST. I much prefer the other approach: if there's not a compelling reason for MUST, make it SHOULD and let the implementation determine whether there's a good reason not to comply with that (remember the meaning of SHOULD).
I agree with Barry here. This is exactly what SHOULD is for. -- Jeff