W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2011

Re: an edit for easy reading on 5.4.1 "byte ranges"

From: Dale Anderson <dra@redevised.net>
Date: Fri, 26 Aug 2011 14:31:48 -0700
Message-ID: <CANNRn6KUtaTsOdoupwZb8h1ULJxstQ22b7Eq2JGCxNGmDqHSPw@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Missing a couple words there in my suggestion. Some tech-writing
background, eh? Here's what I meant, sorry 'bout that.

"""
   If a syntactically valid byte-range-set includes at least one byte-
   range-spec whose first-byte-pos is less than the current length of
   the representation, or at least one suffix-byte-range-spec with a
   non-zero suffix-length, then the byte-range-set is satisfiable.
   Otherwise, the byte-range-set is unsatisfiable.

   If the byte-range-set is satisfiable, then the server SHOULD return
   a response with a 206 (Partial Content) status code containing the
   satisfiable ranges of the representation.

   If the byte-range-set is unsatisfiable, then the server SHOULD return
   a response with a 416 (Requested range not satisfiable) status code.
"""

Cheers

Dale Anderson

2011/8/26 Dale Anderson <dra@redevised.net>:
> A potential good edit on part 5:
>  - In eighth paragraph of 5.4.1 "byte ranges"
>
> """
>   If a syntactically valid byte-range-set includes at least one byte-
>   range-spec whose first-byte-pos is less than the current length of
>   the representation, or at least one suffix-byte-range-spec with a
>   non-zero suffix-length, then the byte-range-set is satisfiable.
>   Otherwise, the byte-range-set is unsatisfiable.  If the byte-range-
>   set is unsatisfiable, the server SHOULD return a response with a 416
>   (Requested range not satisfiable) status code.  Otherwise, the server
>   SHOULD return a response with a 206 (Partial Content) status code
>   containing the satisfiable ranges of the representation.
> """
>
> I would paragraph break that after "Otherwise, the byte-range-set is
> unsatisfiable" and consider changing the first recommendation to
> address the satisfiable condition instead of unsatisfiable, and make
> it two short paragraphs, like this.
>
> """
>   If a syntactically valid byte-range-set includes at least one byte-
>   range-spec whose first-byte-pos is less than the current length of
>   the representation, or at least one suffix-byte-range-spec with a
>   non-zero suffix-length, then the byte-range-set is satisfiable.
>   Otherwise, the byte-range-set is unsatisfiable.
>
>   If the byte-range-set the server
>   SHOULD return a response with a 206 (Partial Content) status code
>   containing the satisfiable ranges of the representation.
>
>   If the byte-range-set is unsatisfiable, the server SHOULD return a
> response with a 416
>   (Requested range not satisfiable) status code.
> """
>
> Just my tech-writing background kicking in there but I think it reads
> more clearly.
>
> Regards,
>
> Dale Anderson
>
Received on Friday, 26 August 2011 21:32:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:47 GMT