This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26257 - poor example of byte sequence or poor terminology or both
Summary: poor example of byte sequence or poor terminology or both
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-03 04:20 UTC by Glenn Adams
Modified: 2015-02-17 12:37 UTC (History)
1 user (show)

See Also:

Attachments

Description Glenn Adams 2014-07-03 04:20:11 UTC 
`true` is not a byte sequence, it is a sequence of six printed symbols; or, excluding the backquotes, a sequence of four printed symbols 't' 'r' 'u' 'e'

on the other hand, the sequence of four hexadecimal 8-bit byte value representations <0x74 0x72 0x75 0x65> is a byte sequence

you are confusing bytes and characters or bytes and printed symbols
Comment 1 Anne 2014-07-03 05:34:08 UTC 
It's a convenient representation of bytes as otherwise spelling out HTTP stuff would be a pain and make things unreadable.
Comment 2 Glenn Adams 2014-07-03 05:46:56 UTC 
(In reply to Anne from comment #1)
> It's a convenient representation of bytes as otherwise spelling out HTTP
> stuff would be a pain and make things unreadable.

Let me study your encoding document and see if I can suggest an alternative.
Comment 3 Anne 2014-10-30 16:33:12 UTC 
I'm using this a lot now. Changing would be quite a pain. However, did you come up with something that is clearer?