View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000279710000-009: Alarms and ConditionsSpecpublic2014-06-12 18:442014-12-02 18:03
ReporterNathan PocockAssigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0002797: Table 14 - AddComment: why BadMethodInvalid instead of BadNotSupported?
Description

CMPWG Jun-12-2014:

AddComment is a mandatory method associated to the ConditionType (table 7).

AddComment result codes (Table 14) says the following for Bad_MethodInvalid:

"See Part 4 for the description of this result code.
The addressed Condition does not support adding comments."

We have two questions:
(1) Wouldn't Bad_NotSupported be a better option that is more applicable?
(2) If AddComment is required; how can it be 'not supported' as stated in the text?

We have defined test-cases for this functionality and need clarification if adding comments is truly mandatory or optional. At this point, we can't quite tell. Thanks.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0002798 closedPaul Hunkar 5.5.6 AddComment: Required or Optional? Can't determine 

Activities

Jim Luth

2014-06-24 16:53

administrator   ~0005366

Agreed that the expected error returns need to be clarified for these two use cases:

  1. No conditions in a server ever allow comments (should the method be optional? What error code is returned when an unimplemented method is called?)
  2. Some conditions in a server allow comments and others don't. (Can a server pretend to not implement a method for some instances but not others?)

Paul Hunkar

2014-11-20 20:41

developer   ~0005648

fixed extra text to "The addressed EventId does not support adding comments." All condition support adding comments - the issue is that the pointed to eventId might not be for a condition - which would mean it does not support the method.

Jim Luth

2014-12-02 18:03

administrator   ~0005673

Reviewed and agreed to text edited in the telecon.

Issue History

Date Modified Username Field Change
2014-06-12 18:44 Nathan Pocock New Issue
2014-06-12 18:49 Nathan Pocock Relationship added related to 0002798
2014-06-24 16:53 Jim Luth Note Added: 0005366
2014-06-24 16:53 Jim Luth Status new => assigned
2014-06-24 16:53 Jim Luth Assigned To => Paul Hunkar
2014-08-19 17:34 Jim Luth Category (No Category) => Spec
2014-08-19 17:34 Jim Luth Target Version => 1.03
2014-11-20 20:41 Paul Hunkar Note Added: 0005648
2014-11-20 20:41 Paul Hunkar Status assigned => resolved
2014-11-20 20:41 Paul Hunkar Resolution open => fixed
2014-12-02 18:03 Jim Luth Note Added: 0005673
2014-12-02 18:03 Jim Luth Status resolved => closed
2014-12-02 18:03 Jim Luth Fixed in Version => 1.03