View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000092010000-004: Servicespublic2009-12-17 19:492011-03-23 06:41
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0000920: SamplingInterval -1 clarification
Description

Table 128 samplingInterval description requires clarification, particularly the following sentence:

"The value -1 indicates that the default sampling interval defined by the publishing rate of the Subscription is used."

This was interpreted by all in the CMP WG that the server was required to honor this sampling rate. Since many servers will have limited sampling rates that they support there are cases where a server couldn't honor that request.

The sentence should continue to say something like:

"Even when -1 is specified by the Client, the server is allowed to revise the sampling interval thus requiring the Client to check the revisedSamplingInterval parameter.

Furthermore, what about other negative numbers? should they be considered "-1"?

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0000902 closedMatthias Damm Compliance issue: Clarifiy CreateSubscription Parameters 
related to 0000916 closedMatthias Damm 5.12.1.2 Sampling Interval missing information about negative numbers 

Activities

user2

2010-01-12 18:24

  ~0001479

Agreed to clarify that illegal request values for parameters that can be revised do not generate errors. Instead the server will choose default values and indicate them in the "revised" buckets. This needs to be applied everywhere the requested/revised paradigm is used.

Agreed to add the rest of the requested clarification.

Matthias Damm

2011-03-13 14:58

developer   ~0002387

Added clarification that all negative numbers are requesting the publishing interval and that the revised sampling interval can be different than the publishing interval.

Added clarification to all services with revised parameters that illegal request parameters that can be revised do not generate errors and server will choose defaule values and return them in the corresponding revised parameter.

Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc"

Randy Armstrong

2011-03-23 06:41

administrator   ~0002522

Reviewed in telco on March 23, 2011
The final changes are included in the document revision OPC UA Part 4 - Services 1.02.04 Draft.doc

Issue History

Date Modified Username Field Change
2009-12-17 19:49 Nathan Pocock New Issue
2009-12-17 22:11 Nathan Pocock Description Updated
2010-01-12 18:24 user2 Note Added: 0001479
2010-01-12 18:24 user2 Status new => assigned
2010-01-12 18:24 user2 Assigned To => Matthias Damm
2010-01-12 18:39 user2 Relationship added related to 0000902
2011-03-13 13:54 Matthias Damm Relationship added related to 0000916
2011-03-13 14:58 Matthias Damm Status assigned => resolved
2011-03-13 14:58 Matthias Damm Resolution open => fixed
2011-03-13 14:58 Matthias Damm Note Added: 0002387
2011-03-23 06:41 Randy Armstrong Status resolved => closed
2011-03-23 06:41 Randy Armstrong Note Added: 0002522