- From: Robert J Burns <rob@robburns.com>
- Date: Fri, 20 Jun 2008 18:57:05 +0200
- To: bugzilla@wiggum.w3.org
- Cc: public-html@w3.org
Sorry for the mixup, but this bug[1] should have read "embedded resources" rather than "linked resources" It is related to bug #5773 [2] which is about linked resources, but different since it deals with embedded resources and how they get processed by the UA. Take care, Rob [1]: Author control over embedded resources <http://www.w3.org/Bugs/Public/show_bug.cgi?id=5776 > [2]: Author control over linked resources <http://www.w3.org/Bugs/Public/show_bug.cgi?id=5773 > On Jun 20, 2008, at 2:50 PM, bugzilla@wiggum.w3.org wrote: http://www.w3.org/Bugs/Public/show_bug.cgi?id=5776 Summary: Authors need more control over handling of linked resources Product: HTML WG Version: unspecified Platform: All URL: http://esw.w3.org/topic/HTML/ LinkAndEmbeddingAttributes OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Spec proposals AssignedTo: dave.null@w3.org ReportedBy: rob@robburns.com QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org * Authors may want to treat a resource as a type for embedding or linking different than the resource’s intrinsic type * HTTP attempted to provide some solutions especially for tailoring the processing of content to an authors needs, however: - because of the history of server-side and client-side http UAs, the content-type headers no longer serve this purpose - any HTTP solution may not be available to all HTML authors: i.e., those who have no access to configure the server or are not using an HTTP server for delivery - providing an HTML solution permits a single resource with only one representation to be processed in various ways while an HTTP solution requires either duplicating the resource or providing a symbolic or hard linking the same resource to provide different HTTP header metadata which may require additional network traffic as well - new headers could be added to HTTP, but it still would not provide an HTML internal solution Some attribute allowing authors to fine-tune the handling would be ideal. For example an HTML tutorial might include side-by-side iframe elements loading the same resource: one as text/html and one as text/plain. (see http://esw.w3.org/topic/HTML/LinkAndEmbeddingAttributes for evolving solution proposals) [author issue, minor added implementation, attribute only solution] -- Configure bugmail: http://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, 20 June 2008 16:57:58 UTC