View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000457510000-005: Information ModelSpecpublic2019-01-04 15:122020-06-18 18:15
ReporterPaul Hunkar Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Summary0004575: Display name definition in part 5 is miss leading/wrong
Description

In section 5.1 Table 3 the definition of DisplayName says the english (En) version shall be the same as the BrowseName. This is wrong - the DisplayName can be any string (it is localized text) and a BrowseName has a namespace associated with it.

Maybe the default is the same as the string part of the BrowseName.

I would think that if object is defined in an information model (nodeset file) then the DisplayName can be defined for any locale as part of the nodeset file definition.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0004653 closedPaul Hunkar 10000-009: Alarms and Conditions DisplayName does not match BrowseName in Opc.Ua.NodeSet2.xml 
has duplicate 0005416 closedJeff Harding 10000-005: Information Model Part 5 (Table 3) defines a rule for the DisplayName incorrectly. 
related to 0005415 closedKarl Deiretsbacher 11020: Companion Spec Template Display name definition in part 5 is miss leading/wrong 

Activities

Jim Luth

2019-06-25 16:31

administrator   ~0010411

Remove any requirement on Display name to match Browse name.

Alexander Allmendinger

2020-01-30 09:13

developer   ~0011517

Once this issue has been resolved in Part 5, the Common Node Attribute table in the Companion Specification template needs to be updated as well.

Jeff Harding

2020-05-14 19:13

developer   ~0012058

Changed the specification of DisplayName in Table 3 - Common Node Attributes to the following
"The DisplayName is a LocalizedText. Each server shall provide a DisplayName with the LocaleId “"en”". Whether the server provides translated names for other LocaleIds is server-specific."

Jeff Harding

2020-06-18 18:15

developer   ~0012442

The text references the 10000 series spec only and therefore is good as is.

Jim Luth

2020-06-18 18:15

administrator   ~0012443

Agreed to no-change-required in virtual F2F.

Issue History

Date Modified Username Field Change
2019-01-04 15:12 Paul Hunkar New Issue
2019-06-25 16:31 Jim Luth Relationship added related to 0004653
2019-06-25 16:31 Jim Luth Note Added: 0010411
2019-06-25 16:31 Jim Luth Assigned To => Jim Luth
2019-06-25 16:31 Jim Luth Status new => assigned
2019-06-25 16:31 Jim Luth Assigned To Jim Luth => Jeff Harding
2020-01-30 09:13 Alexander Allmendinger Note Added: 0011517
2020-01-30 13:48 Jim Luth Issue cloned: 0005415
2020-01-30 13:48 Jim Luth Relationship added related to 0005415
2020-05-14 19:13 Jeff Harding Status assigned => resolved
2020-05-14 19:13 Jeff Harding Resolution open => fixed
2020-05-14 19:13 Jeff Harding Fixed in Version => 1.05
2020-05-14 19:13 Jeff Harding Note Added: 0012058
2020-05-14 19:34 Jeff Harding Relationship added related to 0005416
2020-05-14 19:35 Jeff Harding Relationship replaced has duplicate 0005416
2020-06-18 18:14 Jeff Harding Status resolved => feedback
2020-06-18 18:14 Jeff Harding Resolution fixed => reopened
2020-06-18 18:15 Jeff Harding Status feedback => resolved
2020-06-18 18:15 Jeff Harding Resolution reopened => no change required
2020-06-18 18:15 Jeff Harding Note Added: 0012442
2020-06-18 18:15 Jim Luth Status resolved => closed
2020-06-18 18:15 Jim Luth Note Added: 0012443