View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008516 | 10000-005: Information Model | Spec | public | 2022-12-06 19:44 | 2023-06-20 18:52 |
| Reporter | Jim Luth | Assigned To | Jeff Harding | ||
| Priority | immediate | 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 | ||
| Summary | 0008516: 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 | 1.05.03 RC | ||||
| Fix Due Date | |||||
| related to | 0007979 | closed | Randy Armstrong | 10000-006: Mappings | 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. |
|
|
Add to nameapace metadata object. |
|
|
Added ModeVersion to NamespaceMetadataType |
|
|
Agreed to changes edited in virtual F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-12-06 19:44 | Jim Luth | New Issue | |
| 2022-12-06 19:44 | Jim Luth | Status | new => assigned |
| 2022-12-06 19:44 | Jim Luth | Assigned To | => Jeff Harding |
| 2022-12-06 19:44 | Jim Luth | Issue generated from: 0007979 | |
| 2022-12-06 19:44 | Jim Luth | Note Added: 0018246 | |
| 2022-12-06 19:44 | Jim Luth | Note Added: 0018247 | |
| 2022-12-06 19:44 | Jim Luth | Relationship added | related to 0007979 |
| 2022-12-06 19:44 | Jim Luth | Project | 10000-006: Mappings => 10000-005: Information Model |
| 2022-12-06 19:45 | Jim Luth | Note Added: 0018248 | |
| 2023-05-30 18:56 | Jim Luth | Target Version | => 1.05.03 RC1 |
| 2023-06-13 16:26 | Jim Luth | Commit Version | => 1.05.03 RC |
| 2023-06-13 16:26 | Jim Luth | Priority | normal => immediate |
| 2023-06-20 07:49 | Jeff Harding | Status | assigned => resolved |
| 2023-06-20 07:49 | Jeff Harding | Resolution | open => fixed |
| 2023-06-20 07:49 | Jeff Harding | Fixed in Version | => 1.05.03 |
| 2023-06-20 07:49 | Jeff Harding | Note Added: 0019543 | |
| 2023-06-20 18:52 | Jim Luth | Status | resolved => closed |
| 2023-06-20 18:52 | Jim Luth | Note Added: 0019577 |
