W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

[Bug 18523] New: Spec is unclear about the restriction on LWS in the attribute/value in the ABNF for media-type

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Aug 2012 14:57:39 +0000
To: public-webapps@w3.org
Message-ID: <bug-18523-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18523

           Summary: Spec is unclear about the restriction on LWS in the
                    attribute/value in the ABNF for media-type
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: File API
        AssignedTo: arun@mozilla.com
        ReportedBy: saurabhanandiit@gmail.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: public-webapps@w3.org


http://tools.ietf.org/html/rfc2616#section-3.7 says that "Linear white space
(LWS) MUST NOT be used between the type and subtype, nor between an attribute
and its value" whereas http://tools.ietf.org/html/rfc2616#section-3.6 says
"parameter = attribute "=" value".

NOTE : The white space between the word attribute and the equal to sign and
similarly, equal to sign and the word value.

In the Example section of
http://dev.w3.org/2006/webapi/FileAPI/#constructorParams an instance is given
of the call :

var b = new Blob(["foobarbazetcetc", "birdiebirdieboo"], {type:
"text/plain;charset=UTF-8"});

So, I assume |charset = UTF-8| should throw an error |charset=UTF-8| should
not. Only two cases are possible : Either the example is wrong or the algorithm
isn't clear enough.

Expectation : Either a more clear language used in the IETF specification to
explain the ABNF for media-type.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 10 August 2012 14:57:42 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:54 GMT