View Issue Details

IDProjectCategoryView StatusLast Update
000334910000-005: Information ModelSpecpublic2016-12-14 23:50
ReporterNathan PocockAssigned Tojeffhardingabb  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03 
Summary0003349: 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."

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0003626 closedMatthias Damm 10000-004: Services 8.2 ResendData: Inconsistent text with Part 4 says "current values" and part 5 says "latest values"; applicability to QueueSize? 

Activities

Jim Luth

2016-03-01 16:22

administrator   ~0006758

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-03-01 16:23

administrator   ~0006759

Also need Errata for 1.03.

Jim Luth

2016-12-05 20:18

administrator   ~0007429

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

jeffhardingabb

2016-12-08 20:27

developer   ~0007466

Added clarification text to Part 5 section 9.2

jeffhardingabb

2016-12-08 20:28

developer   ~0007467

Just noticed your comment about Part 4 needing a change also

jeffhardingabb

2016-12-09 12:00

developer   ~0007471

Clarifying Text added to Part 5 section 9.2

Matthias Damm

2016-12-09 19:30

developer   ~0007482

Part 4 uses "current" to be consistent with the definition in TransferSubscriptions::sendInitialValues parameter that has exactly the same intend like ResendData.

The core feature is to get an "initial" value for ALL monitored items, even if they have no value in the queue. The intent is NOT to replace Publish and to deliver the content of the queueus.

There is a reason for not having detailed descriptions in Part 5 since Part 5 only defines the signature and the behaviour is described only in one place (Part 4).

Therefore I propose the following changes:
Change "the latest value of the data monitored items"
to "the current values of all data monitored items"

Remove the new sentence "Even if the queue size of the Monitored Item is greater than 1 then only the latest queued value of the Monitored Item is sent."
This sentence is wrong since describe what a regular Publish would do (send queued values) and not what ResendData should do (send even values if nothing is in the queue). Behaviour should be described only in Part 4.

jeffhardingabb

2016-12-14 23:49

developer   ~0007545

Part5 has adopted the term used by Part 4 "current".

Jim Luth

2016-12-14 23:50

administrator   ~0007546

Agreed to change edited in meeting.

Issue History

Date Modified Username Field Change
2016-02-25 17:46 Nathan Pocock New Issue
2016-03-01 16:22 Jim Luth Note Added: 0006758
2016-03-01 16:23 Jim Luth Note Added: 0006759
2016-03-01 16:23 Jim Luth Assigned To => Wolfgang Mahnke
2016-03-01 16:23 Jim Luth Status new => assigned
2016-03-01 16:23 Jim Luth Product Version => 1.03
2016-03-01 16:23 Jim Luth Target Version => 1.04
2016-11-29 14:16 Jim Luth Assigned To Wolfgang Mahnke => jeffhardingabb
2016-12-05 20:18 Jim Luth Note Added: 0007429
2016-12-05 20:18 Jim Luth Issue cloned: 0003626
2016-12-05 20:18 Jim Luth Relationship added related to 0003626
2016-12-08 20:27 jeffhardingabb Note Added: 0007466
2016-12-08 20:27 jeffhardingabb Status assigned => resolved
2016-12-08 20:27 jeffhardingabb Fixed in Version => 1.04
2016-12-08 20:27 jeffhardingabb Resolution open => fixed
2016-12-08 20:28 jeffhardingabb Assigned To jeffhardingabb => Jim Luth
2016-12-08 20:28 jeffhardingabb Note Added: 0007467
2016-12-08 20:28 jeffhardingabb Status resolved => feedback
2016-12-08 20:28 jeffhardingabb Resolution fixed => reopened
2016-12-09 12:00 jeffhardingabb Note Added: 0007471
2016-12-09 12:00 jeffhardingabb Status feedback => resolved
2016-12-09 12:00 jeffhardingabb Resolution reopened => fixed
2016-12-09 19:30 Matthias Damm Assigned To Jim Luth => jeffhardingabb
2016-12-09 19:30 Matthias Damm Note Added: 0007482
2016-12-09 19:30 Matthias Damm Status resolved => feedback
2016-12-09 19:30 Matthias Damm Resolution fixed => reopened
2016-12-14 23:49 jeffhardingabb Note Added: 0007545
2016-12-14 23:49 jeffhardingabb Status feedback => resolved
2016-12-14 23:49 jeffhardingabb Resolution reopened => fixed
2016-12-14 23:50 Jim Luth Note Added: 0007546
2016-12-14 23:50 Jim Luth Status resolved => closed