OASIS Emergency Management TC

 View Only
  • 1.  STRONGLY RECOMMENDED reprise

    Posted 04-22-2014 17:31
    EM TC members, Before using "STRONGLY RECOMMENDED" in place of SHOULD" in the wording of proposed Notes to the CAP 1.3/2.0 spec, I notice that RFC 2119 equates "RECOMMENDED" with "SHOULD", but not "STRONGLY RECOMMENDED": SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. Comments? Tony Mancuso


  • 2.  Re: [emergency] STRONGLY RECOMMENDED reprise

    Posted 04-22-2014 18:24
    I think that the semantics of SHOULD and RECOMMENDED, per RFC 2119 are enough. Adding "STRONGLY" doesn't add much for me, though I can understand that "SHOULD" doesn't go far enough, but do we want to blur the lines of SHOULD/MUST? cheers, Darrell On Tue, Apr 22, 2014 at 1:30 PM, Anthony Mancuso < amancuso@google.com > wrote: EM TC members, Before using "STRONGLY RECOMMENDED" in place of SHOULD" in the wording of proposed Notes to the CAP 1.3/2.0 spec, I notice that RFC 2119 equates "RECOMMENDED" with "SHOULD", but not "STRONGLY RECOMMENDED": SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. Comments? Tony Mancuso