View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006269 | 10000-004: Services | Spec | public | 2020-11-18 09:20 | 2021-03-02 15:09 |
| Reporter | Christoffer Lind | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0006269: Handle unsupported characters | ||||
| Description | I orignally posted this question here: https://opcfoundation.org/forum/opc-ua-standard/handle-unsupported-unicode-characters/ To summarize: The specification states: Is it allowed to exclude (or rather reject) other unicode characters as well? Would Bad_WriteNotSupported or perhaps Bad_OutOfRange be a valid error code if unsupported characters are received? | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Clarify that Bad_OutOfRange is the appropriate code to use when a client write or method call presents a Server with a string with unacceptable chracters. |
|
|
Added clarification for Bad_OutOfRange: Updated in |
|
|
Agreed to changes in Virtual F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-11-18 09:20 | Christoffer Lind | New Issue | |
| 2021-02-02 17:54 | Jim Luth | Project | 10000-003: Address Space => 10000-004: Services |
| 2021-02-02 17:55 | Jim Luth | Note Added: 0013662 | |
| 2021-02-02 17:56 | Jim Luth | Assigned To | => Matthias Damm |
| 2021-02-02 17:56 | Jim Luth | Status | new => assigned |
| 2021-03-01 14:12 | Matthias Damm | Status | assigned => resolved |
| 2021-03-01 14:12 | Matthias Damm | Resolution | open => fixed |
| 2021-03-01 14:12 | Matthias Damm | Note Added: 0013838 | |
| 2021-03-02 15:09 | Jim Luth | Status | resolved => closed |
| 2021-03-02 15:09 | Jim Luth | Fixed in Version | => 1.05 |
| 2021-03-02 15:09 | Jim Luth | Note Added: 0013883 |