View Issue Details

IDProjectCategoryView StatusLast Update
000787110000-014: PubSubSpecpublic2022-06-23 12:33
ReporterZbynek Zahradnik Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.04 
Target Version1.05.02 RC1Fixed in Version1.05.02 RC1 
Summary0007871: JSON DataSetMessage fields Timestamp and StatusCode need clarification.
Description

https://reference.opcfoundation.org/v104/Core/docs/Part14/7.2.3/ says:

Timestamp DateTime A timestamp which applies to all values contained in the DataSetMessage.
This value is optional. The presence of the value depends on the setting in the JsonDataSetMessageContentMask.

Status StatusCode A status code which applies to all values contained in the DataSetMessage.
This value is optional. The presence of the value depends on the setting in the JsonDataSetMessageContentMask.

Clarifications needed:
1) "A timestamp which applies to all values contained in the DataSetMessage.". Is it source timestamp, server timestamp, or both?
2) What should the subscriber do if it receives a message that has the Timestamp or StatusCode field present at the DataSetMessage level, and at the same time, the field value is formatted as DataValuie and already the timestamp(s) and/or status code? a) use the info from DataValue (I prefer this solution), b) use the info from DataSetMessage, c) reject the message ?

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0007036 closedMatthias Damm Timestamp and Status in keep-alive JSON DataSetMessage not clearly specified 

Activities

Jim Luth

2022-05-10 16:19

administrator   ~0016697

Clarify by stating it is the time the message was created -- do not relate it to source and server timestamp.

Matthias Damm

2022-06-22 13:35

developer   ~0016987

Replaced confusing reference to "all values contained" with text from UADP DataSetMessage

Timestamp
The time the Data was collected.

Status
The overall status of the DataSetMessage.

Jim Luth

2022-06-23 12:33

administrator   ~0017027

Agreed to changes edited in Munich F2F.

Issue History

Date Modified Username Field Change
2022-03-18 13:35 Zbynek Zahradnik New Issue
2022-03-18 13:35 Zbynek Zahradnik Relationship added related to 0007036
2022-05-10 16:19 Jim Luth Note Added: 0016697
2022-05-10 16:19 Jim Luth Assigned To => Matthias Damm
2022-05-10 16:19 Jim Luth Status new => assigned
2022-06-22 05:47 Matthias Damm Target Version 1.05.03 => 1.05.02 RC1
2022-06-22 13:35 Matthias Damm Status assigned => resolved
2022-06-22 13:35 Matthias Damm Resolution open => fixed
2022-06-22 13:35 Matthias Damm Fixed in Version => 1.05.02 RC1
2022-06-22 13:35 Matthias Damm Note Added: 0016987
2022-06-23 12:33 Jim Luth Status resolved => closed
2022-06-23 12:33 Jim Luth Note Added: 0017027