View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000692610000-100: DevicesSpecpublic2021-05-09 11:382021-09-21 19:52
ReporterWolfgang Mahnke Assigned ToKarl Deiretsbacher  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006926: Add capability to provide a semantic version for SoftwareRevision
Description

We discussed in the Asset Management Basics WG that it would be desirable to provide more semantic in the SoftwareRevision than just a string, where you - in a nutshell - just compare if it is the same version or not. In many cases, there is more information like, Major, Minor, Build Number, etc. This website (https://semver.org/) gives a BNF how this can be represented in a string. This allows you to identify, if it is a newer or older version.

As not all SoftwareRevisions will be provided in such a format and we do not want to introduce a breaking change we suggest to:
Create a subtype of String which requires the specific syntax (e.g. called SemVerString). Servers can use the subtype and thus expose to the client, that a specific format is used. Companion Specs can require this format by refining the Property to this data type. Clients can use the information so that they know a specific format is used.

Remark: (Not discussed in WG): Maybe it even make sense to put this data type into the base spec? Then Part 100 should still mention its possible usage as SoftwareRevision.

TagsNo tags attached.

Relationships

related to 0006949 closedJeff Harding 10000-005: Information Model Add capability to provide a semantic version for SoftwareRevision 

Activities

Wolfgang Mahnke

2021-05-18 13:51

reporter   ~0014384

Discussed in WG Meeting:
Define Type called SemanticVersionString as subtype of string.
Copy BNF into spec.
Add note in IVendorNamplateType and SoftwareVersionType that the datatype can be used instead of the "normal" string.

Clone item to Part 5 and potentially define DataType in Part 5.

Wolfgang Mahnke

2021-05-27 12:25

reporter   ~0014425

Proposal from FDI/PA-DIM-WGs (probably also Fx):
“Limit the version parts to 1..5 characters. Furthermore, the number expressed by each part of the version string shall fit into an 16 bit unsigned integer, i.e. <= 65.536.”

Karl Deiretsbacher

2021-09-07 09:10

administrator   ~0014815

Added as suggested to V1.03.1.
The SemanticVersionString DataType is described in the RC but will be transferred to OPC UA 1.05.0.

Matthias Damm

2021-09-07 13:40

administrator   ~0014818

Reviewed and closed in meeting today

Issue History

Date Modified Username Field Change
2021-05-09 11:38 Wolfgang Mahnke New Issue
2021-05-18 13:51 Wolfgang Mahnke Note Added: 0014384
2021-05-18 13:53 Wolfgang Mahnke Issue cloned: 0006949
2021-05-18 13:53 Wolfgang Mahnke Relationship added related to 0006949
2021-05-18 13:54 Wolfgang Mahnke Assigned To => Karl Deiretsbacher
2021-05-18 13:54 Wolfgang Mahnke Status new => assigned
2021-05-27 12:25 Wolfgang Mahnke Note Added: 0014425
2021-09-07 09:10 Karl Deiretsbacher Status assigned => resolved
2021-09-07 09:10 Karl Deiretsbacher Resolution open => fixed
2021-09-07 09:10 Karl Deiretsbacher Note Added: 0014815
2021-09-07 13:40 Matthias Damm Status resolved => closed
2021-09-07 13:40 Matthias Damm Note Added: 0014818
2021-09-21 19:52 Karl Deiretsbacher Issue cloned: 0007274