View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007979 | 10000-006: Mappings | Spec | public | 2022-05-05 15:10 | 2023-01-24 16:40 |
| Reporter | Herbert Oppmann | Assigned To | Randy Armstrong | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.01 | ||||
| Target Version | 1.05.03 RC1 | Fixed in Version | 1.05.03 RC1 | ||
| Summary | 0007979: 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? | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| related to | 0008516 | closed | Jeff Harding | 10000-005: Information Model | How can a tool find out which Namespace 0 NodeSet is newer / better? |
| related to | 0008517 | closed | Randy Armstrong | NodeSets, XSDs and Generated Code | How can a tool find out which Namespace 0 NodeSet is newer / better? |
|
|
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 |
|
|
Added ModelVersion to UANodeSet schema which is a SemanticVersion compliant version string. |
|
|
Needs spec reference. |
|
|
Added reference and errata. |
|
|
Agreed to changes in web meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-05-05 15:10 | Herbert Oppmann | New Issue | |
| 2022-07-05 16:43 | Jim Luth | Assigned To | => Randy Armstrong |
| 2022-07-05 16:43 | Jim Luth | Status | new => assigned |
| 2022-09-23 13:23 | Jim Luth | Note Added: 0017830 | |
| 2022-09-23 13:24 | Jim Luth | Target Version | => 1.05.03 RC1 |
| 2022-10-17 18:40 | Randy Armstrong | Status | assigned => resolved |
| 2022-10-17 18:40 | Randy Armstrong | Resolution | open => fixed |
| 2022-10-17 18:40 | Randy Armstrong | Fixed in Version | => 1.05.02 |
| 2022-10-17 18:40 | Randy Armstrong | Note Added: 0018067 | |
| 2022-12-06 19:44 | Jim Luth | Issue cloned: 0008516 | |
| 2022-12-06 19:44 | Jim Luth | Relationship added | related to 0008516 |
| 2022-12-06 19:48 | Jim Luth | Issue cloned: 0008517 | |
| 2022-12-06 19:48 | Jim Luth | Relationship added | related to 0008517 |
| 2022-12-06 19:52 | Jim Luth | Note Added: 0018251 | |
| 2023-01-23 04:43 | Randy Armstrong | Note Added: 0018551 | |
| 2023-01-24 16:40 | Jim Luth | Status | resolved => closed |
| 2023-01-24 16:40 | Jim Luth | Fixed in Version | 1.05.02 => 1.05.03 RC1 |
| 2023-01-24 16:40 | Jim Luth | Note Added: 0018564 |
