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 16301 - editorial - ambiguous language
Summary: editorial - ambiguous language
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL: http://dvcs.w3.org/hg/xhr/raw-file/8d...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-10 04:11 UTC by Glenn Adams
Modified: 2012-03-26 17:21 UTC (History)
2 users (show)

See Also:


Attachments

Description Glenn Adams 2012-03-10 04:11:17 UTC
In section 4.7.6 step 3 under "If data is a Document", the following sentence:

"Let mime type be "application/xml" or "text/html" if Document is an HTML document, followed by ";charset=", followed by encoding."

is ambiguous since it can be read either as

A: Let mime type be ( "application/xml" or "text/html" ) if Document is an HTML document ...

or as

B: Let mime type be "application/xml" or ( "text/html" if Document is an HTML document ) ...

suggest rephrasing as follows:

"If Document is an HTML document, then let mime type be "text/html" followed by ";charset=" followed by encoding; otherwise, let mime type be "application/xml".

an even more simplified form would be:

"If Document is an HTML document, then let mime type be "text/html;charset=encoding"; otherwise, let mime type be "application/xml"."

in this case encoding should be set in italic to denote it is a variable corresponding to the same-named variable in the previous paragraph
Comment 1 Anne 2012-03-26 17:21:41 UTC
Interesting, your interpretation of the current text was wrong. Hopefully it's all clear now: http://dvcs.w3.org/hg/xhr/rev/2ba0be2d31cd Thanks!