View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000079910000-004: Servicespublic2009-07-23 09:442012-02-09 22:34
ReporterKarl Deiretsbacher Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0000799: Specification of Diagnostic Info not precise enough
Description

(1) It should be mentioned that the Diagnostic Info is always related
to a StatusCode inside a Service Response. It provides additional
information for this StatusCode.
The descriptions should refer to this StatusCode when useful.

(2) It is not clear which fields have to be provided by a Server
Proposal: SymbolicId and LocalizedText shall be supported
with the Standard UA Server Profile
(Conformance Unit: "Base Info Diagnostics")

(3) NamespaceUri:
Why can't this be an index into the NamespaceTable?

(3) SymbolicId - is specified as follows:
"A vendor-specific symbolic identifier string identifies an error or condition"
What is ment with condition?
Is a SymbolicId still required if the vendor has no additional information?
Should we recommend the string version of the StatusCode?
What will the NamespaceUri be in this case?

(4) LocalizedText -
"a text that describes the symbolic id"
Shouldn't it "describe the StatusCode which this DiagnosticInfo belongs to"?

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

user2

2009-08-04 16:39

  ~0001385

Discussed in telecon. Agreed that Namespace URI should never be a standard UA namespace and if SymbolicId is provided then the server must also provide localized text. But all these fields are optional for a server and do not need to be provided for all nodes.

Clarify the SymbolicId is used for subcodes and should not contain standard UA return codes.

Clarify that the Localized text string refers to the SymbolicId if present, otherwise it is the string that describes the standard UA return code when the server provides translations. If this field is -1 then then the server has no translation to return and the client should use the invariant text in the specification.

NamespaceURI is already and index into the string table returned with the call and these URIs are not necessarily in the Namespace table.

Matthias Damm

2011-03-17 19:56

developer   ~0002494

Added clarification that no symbolicIds are provided for standard StatusCodes and that the localized text provides the description for the symbolicId or for the standard StatusCode if no symbolicId is provided.

Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.03 Body.doc"

Randy Armstrong

2011-03-23 06:16

administrator   ~0002515

Reviewed in telco on March 23, 2011
The final changes are included in the document revision OPC UA Part 4 - Services 1.02.04 Draft.doc

Issue History

Date Modified Username Field Change
2009-07-23 09:44 Karl Deiretsbacher New Issue
2009-07-23 09:44 Karl Deiretsbacher Status new => assigned
2009-07-23 09:44 Karl Deiretsbacher Assigned To => Matthias Damm
2009-08-04 16:39 user2 Note Added: 0001385
2011-03-17 19:56 Matthias Damm Status assigned => resolved
2011-03-17 19:56 Matthias Damm Resolution open => fixed
2011-03-17 19:56 Matthias Damm Note Added: 0002494
2011-03-23 06:16 Randy Armstrong Status resolved => closed
2011-03-23 06:16 Randy Armstrong Note Added: 0002515
2012-02-09 22:34 Jim Luth Fixed in Version => 1.02
2012-02-09 22:34 Jim Luth Description Updated