View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000246910000-011: Historical AccessSpecpublic2013-05-02 19:092015-06-23 15:25
ReporterNathan PocockAssigned ToRod Stein  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0002469: ServerTimestamp support, possibly make available as a property for clients to discover?
Description

CMPWG 5/2/2013:

We think it would be of value if UA Clients had the ability to detect if a ServerTimestamp is supported or not. Currently, the Client must try first and see if it receives an error and then adjust accordingly; this is not ideal.

We (CMP) think that it could be advantageous to add a property to either:
(a) the historicalDataConfigurationType (5.2.2) so that a Server could specify which nodes support the timestamp etc.
(b) the HistoryServerCapabilitiesType (5.4.2) so that a Server can state globally that timestamp is/isn't supported.

Possible property definition:
Name = "ServerTimestampSupported"
Type = Boolean
Optional = TRUE; if omitted then the assumption is SUPPORTED (or not supported, but this will need to be clearly stated)

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Rod Stein

2015-06-01 21:40

developer   ~0006105

Changed in 1.03 draft 03

I agree this would be helpful.

Changed HistoryServerCapabilitiesType to have the optional global indication.
Changed historicalDataConfigurationType to have the optional individual indication.
Added descriptions for each.

Jim Luth

2015-06-23 15:25

administrator   ~0006165

Agreed to changes in edited in telecon.

Issue History

Date Modified Username Field Change
2013-05-02 19:09 Nathan Pocock New Issue
2013-05-28 17:41 Jim Luth Status new => assigned
2013-05-28 17:41 Jim Luth Assigned To => Rod Stein
2014-08-19 17:37 Jim Luth Category (No Category) => Spec
2014-08-19 17:37 Jim Luth Target Version => 1.03
2015-06-01 21:40 Rod Stein Note Added: 0006105
2015-06-01 21:40 Rod Stein Status assigned => resolved
2015-06-01 21:40 Rod Stein Resolution open => fixed
2015-06-23 15:25 Jim Luth Note Added: 0006165
2015-06-23 15:25 Jim Luth Status resolved => closed
2015-06-23 15:25 Jim Luth Fixed in Version => 1.03