View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000327810000-004: ServicesSpecpublic2016-01-28 16:472016-12-20 16:20
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03 
Summary0003278: Table 64: Call -- OperationResults table should be divided into two tables
Description

CMPWG Jan-28-2016:

In reviewing the UA 1.03 Diff document for CALL, it seems that the Operation Results field is listing codes that don't apply to the operation level, that should only apply to the "InputArgumentResults" parameter instead.

We propose either:
(a) separating the codes into two tables: 1x Operation level; 1x inputArgumentResults table
(b) adding more commentary in the existing table to clarify which code can be used in which field.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2016-12-19 21:55

developer   ~0007653

Split operation result tables for operation level statusCode and inputArgumentResults parameters into two tables.

Made changes in document version OPC UA Part 5 - Information Model 1.04.05 Draft Specification.docx

Jim Luth

2016-12-20 16:20

administrator   ~0007664

agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2016-01-28 16:47 Nathan Pocock New Issue
2016-03-01 17:17 Jim Luth Assigned To => Matthias Damm
2016-03-01 17:17 Jim Luth Status new => assigned
2016-03-01 17:17 Jim Luth Target Version 1.03 => 1.04
2016-12-19 21:55 Matthias Damm Note Added: 0007653
2016-12-19 21:55 Matthias Damm Status assigned => resolved
2016-12-19 21:55 Matthias Damm Resolution open => fixed
2016-12-20 16:20 Jim Luth Note Added: 0007664
2016-12-20 16:20 Jim Luth Status resolved => closed
2016-12-20 16:20 Jim Luth Fixed in Version => 1.04