View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008517NodeSets, XSDs and Generated CodeApi Changepublic2022-12-06 19:482023-11-28 17:54
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Product Version1.05.01 
Fixed in Version1.05.03 
Summary0008517: How can a tool find out which Namespace 0 NodeSet is newer / better?
Description

Regarding Namespace metadata, both Part 6 (in Table F.1 UANodeSet) and Part 5 (in Table 21 NamespaceMetadataType definition) state that tools shall use the Version string only for display purposes, and not for identifying the latest version. Instead, they shall use the PublicationDate for that.

Now suppose a tool that can manage different versions of the OPC UA core Namespace. How can this tool find out which is the latest and greatest, when there are updated versions of the V1.03xx and V1.04.xx variants which have a newer publication date than some V1.05.xx ones, without looking into the version string? Should this be treated as an exception to the mentioned rules?

TagsNo tags attached.
Commit Version1.05.03
Fix Due Date

Relationships

related to 0007979 closedRandy Armstrong 10000-006: Mappings How can a tool find out which Namespace 0 NodeSet is newer / better? 

Activities

Jim Luth

2022-12-06 19:48

administrator   ~0018249

We agreed to add a new attribute to hold the Semantic Version and mandate that the existing Version string must contain the same string as the new Semantic Version string. The XML Schema will enforce the Semantic version standard using a regex.

This will be added to 1.05.03

Randy Armstrong

2022-12-06 19:48

administrator   ~0018250

Added ModelVersion to UANodeSet schema which is a SemanticVersion compliant version string.

Randy Armstrong

2023-05-12 06:53

administrator   ~0019341

Added
<xs:attribute name="ModelVersion" type="ModelVersion" use="optional" />

Jim Luth

2023-11-28 17:54

administrator   ~0020440

Agreed to changes in Web Meeting.

Issue History

Date Modified Username Field Change
2022-12-06 19:48 Jim Luth New Issue
2022-12-06 19:48 Jim Luth Status new => assigned
2022-12-06 19:48 Jim Luth Assigned To => Randy Armstrong
2022-12-06 19:48 Jim Luth Issue generated from: 0007979
2022-12-06 19:48 Jim Luth Note Added: 0018249
2022-12-06 19:48 Jim Luth Note Added: 0018250
2022-12-06 19:48 Jim Luth Relationship added related to 0007979
2022-12-06 19:49 Jim Luth Project 10000-006: Mappings => NodeSets, XSDs and Generated Code
2022-12-06 19:49 Jim Luth Category Spec => Api Change
2023-05-12 06:53 Randy Armstrong Status assigned => resolved
2023-05-12 06:53 Randy Armstrong Resolution open => fixed
2023-05-12 06:53 Randy Armstrong Note Added: 0019341
2023-11-28 17:54 Jim Luth Status resolved => closed
2023-11-28 17:54 Jim Luth Fixed in Version => 1.05.03
2023-11-28 17:54 Jim Luth Commit Version => 1.05.03
2023-11-28 17:54 Jim Luth Note Added: 0020440