I've added the following requirement to the Req doc: R12. Derive the MIME types of Resources In the case that the packaging format does not support labeling resources with a MIME Type, a conforming specification MUST either specify or recommend a means of deriving the MIME type of resources for the purposes of rendering. A conforming specification MAY define a means to override how a widget user agent derives the MIME type of a resource (e.g., treat resources with the file extension .php as text/html), but MUST NOT force a widget user agent to process resources of one MIME type as that of another type (e.g. treating a jpeg image at text/html).
Motivation: Web and offline distribution, device independence, and current development practice or industry best-practice. Rationale: To allow appropriate rendering of resources by the widget user agent. For instance, for the sake of interoperability, all widget user agents should treat resources with a .html file extension as text/html (and not as application/xhtml+xml). Here is the list of file extensions and what they should map to (added to the packaging spec): .html,.htm -> text/html .css -> text/css .gif -> image/gif .jpeg, jpg -> image/jpeg .js -> application/javascript .xml -> application/xml .wav,wave -> audio/x-wav .ico -> image/vnd.microsoft.icon .png -> image/png A widget user agent would be expected to support the above types. All other types are optional. All proprietary types, apart from ico, are optional. Kind regards, Marcos
