View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002973 | UA Specification | Spec | public | 2015-02-18 08:23 | 2020-06-02 16:32 |
| Reporter | Gerhard Gappmeier | Assigned To | Jim Luth | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Product Version | 1.02 | ||||
| Summary | 0002973: Reference to RFC2119 missing | ||||
| Description | I was convinced that the OPC UA spec, like all others specs an RFCs contain a reference to RFC2119, explaining the keywords as shown below. Because a colleague was asking me today I tried to search for that explanation in the UA spec, but I couldn't find it. (Wasn't this there in older releases?) | ||||
| Additional Information | All parts of the specs should contain a section like the following: 1.1 Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
We follow the IEC specification rules on this matter, not the IETF. |
|
|
Nevertheless a section should be added with the information that the keywords SHALL, SHOULD, etc should be interpreted according to IEC. At the moment the spec does not include any information about that and the reader must guess. I think the correct cross-reference would be this: |
|
|
Part 2 had added text like this: The terminology in this document follows the rules set forth by the IEC. This document is also available as an IEC document. The relevant guidelines for terminology can be found here: General layout and styles can be found here |
|
|
The provided link does not work. The IEC specs do not contain such information so we will not add it to ours. |
|
|
Need to check with IEC for appropriate text. The IEC guidelines for editors is not appropriate for this. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-02-18 08:23 | Gerhard Gappmeier | New Issue | |
| 2015-03-03 17:28 | Jim Luth | Note Added: 0005869 | |
| 2015-03-03 17:28 | Jim Luth | Status | new => closed |
| 2015-03-03 17:28 | Jim Luth | Assigned To | => Jim Luth |
| 2015-03-03 17:28 | Jim Luth | Resolution | open => no change required |
| 2015-03-12 12:36 | Gerhard Gappmeier | Note Added: 0005903 | |
| 2015-03-12 12:36 | Gerhard Gappmeier | Status | closed => feedback |
| 2015-03-12 12:36 | Gerhard Gappmeier | Resolution | no change required => reopened |
| 2015-03-12 12:41 | Gerhard Gappmeier | Note Edited: 0005903 | |
| 2015-07-09 19:38 | Jim Luth | Target Version | => 1.04 |
| 2015-07-28 17:39 | Paul Hunkar | Note Added: 0006289 | |
| 2017-08-22 15:42 | Jim Luth | Note Added: 0008406 | |
| 2017-08-22 15:42 | Jim Luth | Status | feedback => closed |
| 2017-08-22 15:42 | Jim Luth | Resolution | reopened => no change required |
| 2017-08-29 15:59 | Jim Luth | Assigned To | Jim Luth => |
| 2017-08-29 15:59 | Jim Luth | Note Added: 0008418 | |
| 2017-08-29 15:59 | Jim Luth | Status | closed => feedback |
| 2017-08-29 15:59 | Jim Luth | Resolution | no change required => reopened |
| 2017-08-29 16:01 | Jim Luth | Assigned To | => Jim Luth |
| 2017-08-29 16:01 | Jim Luth | Status | feedback => acknowledged |
| 2017-08-29 16:06 | Jim Luth | Project | 10000-002: Security => UA Specification |
| 2017-08-29 16:55 | Jim Luth | Assigned To | Jim Luth => |
| 2020-06-02 16:32 | Jim Luth | Assigned To | => Jim Luth |
| 2020-06-02 16:32 | Jim Luth | Status | acknowledged => closed |
| 2020-06-02 16:32 | Jim Luth | Resolution | reopened => won't fix |
