Nickname:
Title:
State: RAISED OPEN PENDINGREVIEW CLOSED POSTPONED
Product: None API Minimization CLOSED: Versioning Finding: terminology Coordination with IAB (of IETF) on architecture of web applications HTML 5 review Meeting planning and records Metadata Architecture Persistence of identifiers TAG/W3C web site, blog, etc. Web Application Architecture WebApps access control requirements review CLOSED ON 12 MAY 2011 webarch maintenance
Raised By: Daniel Appelquist David Baron Hadley Beeman Tim Berners-Lee Alice Boxhall Kenneth Christiansen Yves Lafon Peter Linss Sangwhan Moon Theresa O'Connor Lukasz Olejnik Henry S. Thompson
Description: Shepherd: Henry Thompson Rank: high deliverables: ??? issue scope: What should specifications say about error handling? community affected: WGs working on data formats: SVG WG, HTML WG, XHTML 2 WG, RDFa's WG re-opened 9 Dec 2008 in a discussion of HTML5, tag soup, and error handling: http://www.w3.org/2001/tag/2008/12/09-minutes.html#item04 announcement of decision: http://lists.w3.org/Archives/Public/www-tag/2003Dec/0044
Add notes (no markup allowed, URIs get automatically hyperlinked):
[DanC]: Postel's law, dealing with invalid content, TInkerbell effect Larry Masinter http://lists.w3.org/Archives/Public/www-tag/2009Jan/0075.html
[johnk]: http://www.w3.org/2001/tag/2009/03/03-agenda#errorhandling
connecting with "HTML 5 review" product a la http://www.w3.org/2001/tag/2009/11/02-agenda
[timbl]:
[noah]: What should specifications say about error handling?
Reviewed status of this at 10 Feb 2011 (8-10 Feb) F2F. Decided to leave this open for now, pending better understanding of where the XML/HTML Unification Task force is going with related issues.