W3C home > Mailing lists > Public > www-html-editor@w3.org > July to September 2006

[xhtml2] Conflict between HTTP and XHTML 2.0 about mimetype

From: <karl@w3.org>
Date: Thu, 17 Aug 2006 03:27:33 -0000
To: www-html-editor@w3.org
Message-Id: <20060817032738.2B6974F54F@homer.w3.org>

This is a QA Review comment for "XHTML 2.0"
8th WD

About http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-embedding.html#adef_embedding_srctype

In 18. XHTML Embedding Attributes Module, the specification says:

	"srctype = ContentTypes
    This attribute specifies the allowable content 
	types of the resource referenced by the relevant src URI."

no MUST, no REQUIRED, it doesn't specify the mandatoriness of the value. Though in the *informative* introduction:

	Type: in HTML 4, the srctype attribute when referring 
	to an external resource was purely a hint to the user 
	agent. In XHTML 2 it is no longer a hint, but specifies 
	the type(s) of resource the user agent must accept.
	-- XHTML 2.0 - Introduction
	Wed, 26 Jul 2006 20:04:35 GMT

Beside the fact that "srctype" doesn't exist in HTML 4, you meant one of the type attributes like for example

It is in conflict with 
	- CHIPS - Common HTTP Implementation Problems
	- CUAP - Common User Agent Problems
	- TAG findings - Mime Respect
	  "Specifications MUST NOT work against the Web architecture 
	  by requiring or suggesting that a recipient override 
	  authoritative metadata without user consent."
	- HTTP 1.1
and THEN in conflict with XHTML 2.0 User Agent Conformance, which says

	"When the user agent claims to support facilities defined 
	within this specification or required by this specification 
	through normative reference, it must do so in ways consistent 
	with the facilities' definition."

	HTTP has precedence over markup languages.
	Any HTTP/1.1 message containing an entity-body SHOULD include a
	Content-Type header field defining the media type of that body. If
	and only if the media type is not given by a Content-Type field, the
	recipient MAY attempt to guess the media type via inspection of its
	content and/or the name extension(s) of the URI used to identify the
	resource. If the media type remains unknown, the recipient SHOULD
	treat it as type "application/octet-stream"
    -- 7.2.1 Type

Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Thursday, 17 August 2006 03:29:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:08:55 UTC