- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 07 Sep 2009 07:51:44 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7512 Summary: suggested "replacement" for head/@profile does not workk Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML5 spec bugs AssignedTo: dave.null@w3.org ReportedBy: julian.reschke@gmx.de QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org In Editor's draft as of 2009-06-07: "User agents should ignore the profile content attribute on head elements. When the attribute would be used as a globally unique name, the user agent should instead always assume that all known profiles apply to all pages, and should therefore apply the conventions of all known metadata profiles to the document." That ignores the fact that one use for specifying profiles is disambiguation. If a term with the same name is defined in multiple profiles, and the recipient "knows" them, it can't decide which definition to use in absence of advice from @profile. I agree that disambiguation is one of the weakest points of @profile, but it is there, and the suggested replacement does not have it. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 7 September 2009 07:51:55 UTC