- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 21 Oct 2009 07:12:15 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7862 --- Comment #10 from Julian Reschke <julian.reschke@gmx.de> 2009-10-21 07:12:14 --- (In reply to comment #9) > (In reply to comment #8) > > The key here is that use of @profile, required by specs such as GRDDL and > > DC-HTML, should not cause a validator error *or* warning. > > Then it would seem that another possible solution is for them to work with > validator maintainers to add specific validation support for GRDDL and DC-HTML > to validators. Or I think a lot of people would argue that an perhaps better I don't think that solution scales. Is anybody who continues to use a now invalid element/attribute supposed to speak to *every* validator implementor? Also, unless that's the default validation mode I really don't see how that would help with the issue. > solution for them to consider amending or updating their specs to not include > @profile at all. Which sort-of requires us, as the HTML WG, to propose a replacement first. The "proposal" in HTML5 does not work (see separate bug). -- 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 Wednesday, 21 October 2009 07:12:16 UTC