Disposition of comments for the Mobile Web Best Practices Working Group

Not all comments have been marked as replied to. The disposition of comments is not complete.

In the table below, red is in the WG decision column indicates that the Working Group didn't agree with the comment, green indicates that a it agreed with it, and yellow reflects an in-between situation.

In the "Commentor reply" column, red indicates the commenter objected to the WG resolution, green indicates approval, and yellow means the commenter didn't respond to the request for feedback.

Commentor	Comment	Working Group decision	Commentor reply
LC-1466 Dan Connolly `<connolly@w3.org>` (archived comment)	I see: "If the request response does specify a character encoding but it is not "UTF-8", FAIL" -- http://www.w3.org/TR/mobileOK/#id4485785 How about US-ASCII? especially since you can treat US-ASCII as UTF-8 and preserve the meaning of the bytes. It's perhaps not worthwhile to complicate things, if very few documents are labelled US-ASCII. p.s. I wonder if it's acceptable to limit encodings to UTF-8 and exclude UTF-16; it wasn't when XML was ratified. But I'll leave it to those who have 1st-hand experience with the need for UTF-16 to comment on that. p.p.s. The fragid #id4485785 seems fragile. If you're going to break it, break it only once, for the next draft. At that point, change it to something like #char-encoding-support and keep it that way for future revisions.	Dan we discussed character encoding and US-ASCII at our weekly call. One concern was that several Japanese phones would not recognize the US-ASCII encoding when called "US-ASCII" and would default to Shift_JIS instead of UTF-8. The same may be true of other handsets. I think the position of the group would be that a document encoded as US-ASCII is also encoded as UTF-8 and so should be declared as "UTF-8" instead. We'd not want to tell people to assume that phones know what US-ASCII is, as it seems there is enough lack of support to puncture that assumption.	yes
LC-1467 Dan Connolly `<connolly@w3.org>`		Resolved per Sean's reply in the next draft	tocheck