This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1154 - Error processing for specs that are no language nor protocols
Summary: Error processing for specs that are no language nor protocols
Status: RESOLVED REMIND
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: LC-2004-11-22
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-04 13:35 UTC by Dominique Hazael-Massieux
Modified: 2005-04-28 11:53 UTC (History)
0 users

See Also:


Attachments

Description Dominique Hazael-Massieux 2005-03-04 13:35:03 UTC
The spec says "For a language, address what effect an error (be it
syntactic or semantic) in the input has to a processor of this language.
For a protocol, address how should behave a party to this protocol when
a bogus message is received." For things that are not languages and not
protocols, what is required?
Comment 1 Dominique Hazael-Massieux 2005-03-04 17:51:57 UTC
What do you do if you are defining an API  where you would define an error 
mechanism, or other types of specifications? Suggest putting in a general 
statement like, For each class of product that is affected by an error 
condition, address how the error is handled.  Then provide examples, 
recasting current text for protocols/languages as examples and include API 
example.
ACTION:  Reword text and include examples  Dom 15 March
RESOLUTION: agree with the TAG and will make appropriate changes to the text
Comment 2 Dominique Hazael-Massieux 2005-03-21 13:27:44 UTC
new text reads:
"""or each class of product that is affected by an error 
condition, address how the error is handled. For instance: 
for a language, address what effect an error (be it syntactic or
semantic) in the input has to a processor of this language; 
for a protocol, address how a party to this protocol should behave  when
a bogus message is received; for an A.P.I., indicate what exceptions are raised.
"""
Comment 3 Dominique Hazael-Massieux 2005-04-28 11:53:52 UTC
setting version to LC in case of future use