Changes between Version 1 and Version 2 of Ticket #510


Ignore:
Timestamp:
30/10/13 13:12:34 (9 years ago)
Author:
julian.reschke@…
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #510 – Description

    v1 v2  
    1616----
    1717
    18 I see that “ought” is used in two places on page 6, but not in uppercase
    19 as per RFC 6919. The authors should revisit the use of this term here.
     18~~I see that “ought” is used in two places on page 6, but not in uppercase
     19as per RFC 6919. The authors should revisit the use of this term here.~~ - see http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0411.html
    2020
    2121----
    … …  
    4949----
    5050
    51 The end of Section 2.2 includes the word “might” but not uppercase, as
     51~~The end of Section 2.2 includes the word “might” but not uppercase, as
    5252per RFC 6919. I again suggest that the authors reconsider using this
    53 term in this context.
     53term in this context.~~ - see http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0411.html
    5454
    5555----
    … …  
    7373----
    7474
    75 Section 5.1.2 uses “ought” when discussing definitions for new
     75~~Section 5.1.2 uses “ought” when discussing definitions for new
    7676authentication schemes. See comments above re use of this term.The same
    77 section also uses the phrase “need to” twice, where MUST seems appropriate.
     77section also uses the phrase “need to” twice, where MUST seems appropriate.~~ - see http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0411.html
    7878
    7979----