| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 04:27:18 GMT
content-type: text/html
content-encoding: gzip
content-location: 0044.html
vary: negotiate,Accept-Encoding
tcn: choice
last-modified: Thu, 13 Jul 2023 17:54:17 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 04:27:18 GMT
access-control-allow-origin: *
x-request-id: 987e0ba6985270f5
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: REVALIDATED
set-cookie: __cf_bm=8uu1HnAJIjvTw8mMRlw3Q83ApABvlJYpwEdV08WpJ6s-1760156838-1.0.1.1-TjUl7R9lAIjbdhuYgyCweom1olvVDUY7TIb_DEygdyiy73aGFp.MmM3cP6xqgcQNP98_p8eLGqTx5lrOW6_iSjJ5GZpN3hQgBMZj.7TEKHs; path=/; expires=Sat, 11-Oct-25 04:57:18 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cb9aaa995095be-BLR
alt-svc: h3=":443"; ma=86400
[errorHandling-20] CLOSED: What should specifications say about error handling? from Chris Lilley on 2003-12-02 (www-tag@w3.org from December 2003)
[errorHandling-20] CLOSED: What should specifications say about error handling?
- From: Chris Lilley <chris@w3.org>
- Date: Tue, 2 Dec 2003 19:45:47 +0100
- To: Rob Lanphier <robla@real.com>
- Cc: www-tag@w3.org
- Message-ID: <14627455208.20031202194547@w3.org>
Hello Rob, At our Yokohama f2f meeting, the TAG noticed that many aspects of the issue you raised [1] and which we accepted as issue 20 [2] errorHandling-20: What should specifications say about error handling? are by now addressed in the current Architecture Document [3]. Specifically, section 1.2.3 [4] discusses error handling, requires specification of error handling, and establishes that silent recovery from errors is harmful, thus addressing your 'second guessing' point. Section 4.2 [5] discusses extensibility and versioning, what specifications should say about when to ignore extensions and when extensions must be understood. You also raised the issue of conformance to deprecated features, and suggested it might be a different issue. It seems that a deprecated feature is one that content authors and authoring tools should not produce, and that content consumers must understand. We propose therefore to close issue 20 as already addressed. Please let us know whether you are satisfied with this outcome. Thanks again for your help and contributions, [1] https://lists.w3.org/Archives/Public/www-tag/2002May/0124 [2] https://www.w3.org/2001/tag/issues.html#errorHandling-20 [3] https://www.w3.org/2001/tag/2003/webarch-20031128 [4] https://www.w3.org/2001/tag/2003/webarch-20031128/#error-handling [5] https://www.w3.org/2001/tag/2003/webarch-20031128/#ext-version -- Chris mailto:chris@w3.org
Received on Tuesday, 2 December 2003 13:45:48 UTC