View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000397110000-004: ServicesSpecpublic2017-09-27 20:122017-11-09 17:55
ReporterLiam Power Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Product Version1.02 
Summary0003971: ContinuationPoint type is inconsistent (V 1.03)
Description

The BrowseNext, QueryFirst and QueryNext message definitions and the BrowseResult type definition both say that the continuation point is of type Continuation Point. The Continuation Point type is described in section 7.6.

The HistoryRead request and response message definitions say that the continuation point is of type ByteString although section 7.6 is referenced in the description. Surely the type should be Continuation Point, similar to the other definitions?

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2017-10-17 15:13

administrator   ~0008584

Discussed in UA Call. Agreed these should be of type ContinuationPoint not ByteString. Agreed to fix in 1.04. No errata necessary because on the wire a ByteString is used.

Matthias Damm

2017-10-23 13:03

developer   ~0008592

Change data type to ContinuationPoint

Changed in version OPC UA Part 4 - Services RC 1.04.21 Specification.docx

Jim Luth

2017-11-09 17:55

administrator   ~0008673

Reviewed and agreed to close in 2017-10-24 Telecon.

Issue History

Date Modified Username Field Change
2017-09-27 20:12 Liam Power New Issue
2017-10-17 15:13 Jim Luth Note Added: 0008584
2017-10-17 15:13 Jim Luth Target Version => 1.04
2017-10-17 15:13 Jim Luth Assigned To => Matthias Damm
2017-10-17 15:13 Jim Luth Status new => assigned
2017-10-23 13:03 Matthias Damm Note Added: 0008592
2017-10-23 13:03 Matthias Damm Status assigned => resolved
2017-10-23 13:03 Matthias Damm Resolution open => fixed
2017-11-09 17:55 Jim Luth Note Added: 0008673
2017-11-09 17:55 Jim Luth Status resolved => closed