View Issue Details

IDProjectCategoryView StatusLast Update
000213210000-004: Servicespublic2012-08-07 19:35
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0002132: Table 166 explanation of Bad_WaitingForInitialData confusion over word "optionally"
Description

The following sentence that describes Bad_WaitingForInitialData is confusing:

"In such cases the server can optionally send a Notification with this status prior to the Notification with the first valid value."

The word "optionally" is confusing; does it refer to the notification or the status code? Does this mean that the server is NOT required to send an initial data-change if it does not have the data yet, but if it does then it can send zero/null values along with Bad_WaitingForInitialData.

I think the sentence could be rephrased:

"In such cases the server can send an initial data-change Notification with this status prior to the Notification with the first valid value."

I think it's important to communicate that the initial data-change is still sent with or without valid data.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2012-07-24 17:35

developer   ~0003911

Last edited: 2012-07-24 17:36

Changed sentence to:
In such cases the server can send a Notification with this status prior to the Notification with the first valid value or status from the data source.
Changed in document "OPC UA Part 4 - Services RC 1.02.21 Specification.doc"

Matthias Damm

2012-07-24 17:37

developer   ~0003912

See previous note

Jim Luth

2012-08-07 19:35

administrator   ~0003964

Reviewed and agreed to close in telecon 2012-07-24.

Issue History

Date Modified Username Field Change
2012-07-20 14:32 Nathan Pocock New Issue
2012-07-24 17:35 Matthias Damm Status new => assigned
2012-07-24 17:35 Matthias Damm Assigned To => Matthias Damm
2012-07-24 17:35 Matthias Damm Status assigned => resolved
2012-07-24 17:35 Matthias Damm Resolution open => fixed
2012-07-24 17:35 Matthias Damm Note Added: 0003911
2012-07-24 17:36 Matthias Damm Status resolved => assigned
2012-07-24 17:36 Matthias Damm Note Edited: 0003911
2012-07-24 17:37 Matthias Damm Status assigned => resolved
2012-07-24 17:37 Matthias Damm Note Added: 0003912
2012-08-07 19:35 Jim Luth Status resolved => closed
2012-08-07 19:35 Jim Luth Note Added: 0003964
2012-08-07 19:35 Jim Luth Fixed in Version => 1.02