- From: <bugzilla@jessica.w3.org>
- Date: Fri, 29 Jul 2011 12:28:31 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417 --- Comment #35 from Jörg Schütz <joerg@bioloom.de> 2011-07-29 12:28:29 UTC --- (In reply to comment #33) Hi Felix, Thanks for your comments! Frankly speaken, I also don't like very much the spelling and grammar checking feature in HTML5. This feature concerns the content creation process, and therefore doesn't have a particular relation to the actual content representation in HTML (which could be yet another seperate process). Translatability, on the other hand, has such a relation to the content representation because it is a means to guide or to trigger possible subsequent processes such as for instance a (machine) translation application because these processes would directly operate on the HTML representation (maybe also through a certain user agent interaction - my first use case). In this context, my examples of other markup candidates point in exactly this processability direction. Since the specification of HTML5 is still floating, I wouldn't distinguish between core and non-core features. This means depending on a particular use case scenario, there should be room for the discussion of different solution alternatives such as the proposed microdata apporach, or even fully fledged semantic web technologies. It would be also a challenging opportunity to demonstrate their applicability in real life scenarios. Last but not least, the proposed microdata approach is available in HTML5 dom. Best -- Jörg -- 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 Friday, 29 July 2011 12:28:35 UTC