0003626: 8.2 ResendData: Inconsistent text with Part 4 says "current values" and part 5 says "latest values"; applicability to QueueSize? - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0003626	10000-004: Services	Spec	public	2016-12-05 20:18	2016-12-15 22:59

Reporter	Jim Luth	Assigned To	Matthias Damm
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	1.03

Summary	0003626: 8.2 ResendData: Inconsistent text with Part 4 says "current values" and part 5 says "latest values"; applicability to QueueSize?
Description	CMPWG Feb-25-2016: Neither part 4 or part 5 answer the following question: What if a MonitoredItem's QueueSize > 1 and there are multiple values contained, or the queue is full? Should I receive the contents of the queue (whether it is full or partial) or just the latest value in the queue? We think contents of the queue should be returned; not just the latest value. We propose adding the following text: "For monitored items with a QueueSize greater than 1, and multiple values are buffered in the queue, then all of those queued values will be returned in the Publish response."
Tags	No tags attached.

Commit Version
Fix Due Date

Jim Luth 2016-12-05 20:18 administrator ~0007430	Agreed that the spec should explicitly state what happens when queue size is greater than 1. It should state only the latest cached value is sent. This may also need to be fixed in Part 4 (let me know if so when Part 5 is edited).

Jim Luth 2016-12-05 20:18 administrator ~0007431	Also need Errata for 1.03.

Jim Luth 2016-12-05 20:18 administrator ~0007432	I updated Part 5 for this one and looked at Part 4 which I think should also be updated. In section 6.5 I think the following will address the issue. The Server Object provides a Method ResendData that initiates resending of all data monitored items in a Subscription. This Method is defined in Part 5. If this Method is called, subsequent Publish responses shall contain the current value of all data MonitoredItems in the Subscripion where the MonitoringMode is set to Reporting. The Server shall verify that the Method is called within the Session context of the Session that owns the Subscription. Jeff

Matthias Damm 2016-12-09 19:49 developer ~0007483	Part 4 uses "current" to be consistent with the definition in TransferSubscriptions::sendInitialValues parameter that has exactly the same intend like ResendData. Therefore Part 5 should be changed. Added the following sentence to the definition of ResendData and to TransferSubscriptions::sendInitialValues "If a value is queued for a data MonitoredItem, the next value in the queue is sent in the Publish response. If no value is queued for a data MonitoredItem, the last value sent is repeated in the Publish response." Made changes in document version OPC UA Part 4 - Services 1.04 Specification Draft 02.docx

Jim Luth 2016-12-15 22:59 administrator ~0007593	Agreed to changed text in meeting. Agreed that 1.03 Errata NOT needed.

Date Modified	Username	Field	Change
2016-12-05 20:18	Jim Luth	New Issue
2016-12-05 20:18	Jim Luth	Status	new => assigned
2016-12-05 20:18	Jim Luth	Assigned To	=> jeffhardingabb
2016-12-05 20:18	Jim Luth	Issue generated from: 0003349
2016-12-05 20:18	Jim Luth	Relationship added	related to 0003349
2016-12-05 20:19	Jim Luth	Assigned To	jeffhardingabb => Matthias Damm
2016-12-05 20:19	Jim Luth	Project	10000-005: Information Model => 10000-004: Services
2016-12-09 19:49	Matthias Damm	Note Added: 0007483
2016-12-09 19:49	Matthias Damm	Status	assigned => resolved
2016-12-09 19:49	Matthias Damm	Resolution	open => fixed
2016-12-15 22:59	Jim Luth	Note Added: 0007593
2016-12-15 22:59	Jim Luth	Status	resolved => closed
2016-12-15 22:59	Jim Luth	Fixed in Version	=> 1.04