ETSI's Bug Tracker - Part 11: Using JSON with TTCN-3
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007914 | Part 11: Using JSON with TTCN-3 | [TTCN-3 Change Requests] Editorial | public | 05-03-2020 06:08 | 23-12-2020 13:59

Reporter | KristÃ³f Szabados |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | V4.8.1 (published 2020-05) |
Target Version | V4.9.1 (ongoing) | Fixed in Version | V4.9.1 (ongoing) |

Summary | 0007914: conflicting definition and examples for usi encoding
Description | Section B.3.7 clearly states that using the "escape as usi" encoding instruction, all characters in the TTCN-3 value shall be encoded using the USI-like escape sequence "\u<HHHH>" Yet the example for "escape as usi" in section 6.4.2 clearly show that only special characters need to encoded like that. None of the examples uses the \u<HHHH> format for the abcd letters.
Steps To Reproduce |
Additional Information | I was looking at version v4.8.1 (2018-05)
Tags | No tags attached.
Relationships |
Attached Files | CR_7914.docx (150,351) 06-10-2020 11:08 http://oldforge.etsi.org/mantis/file_download.php?file_id=3956&type=bug CR_7914_v2.docx (150,303) 08-10-2020 14:35 http://oldforge.etsi.org/mantis/file_download.php?file_id=3960&type=bug

Issue History
Date Modified | Username | Field | Change
05-03-2020 06:08 | KristÃ³f Szabados | New Issue |
10-08-2020 11:02 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
10-08-2020 11:02 | Jens Grabowski | Status | new => assigned
24-08-2020 11:31 | Gyorgy Rethy | Note Added: 0015753 |
06-10-2020 11:08 | KristÃ³f Szabados | File Added: CR_7914.docx |
06-10-2020 11:09 | KristÃ³f Szabados | Note Added: 0015759 |
06-10-2020 13:47 | Jens Grabowski | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
06-10-2020 14:15 | Jacob Wieland - Spirent | Note Added: 0015762 |
06-10-2020 14:16 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => KristÃ³f Szabados
08-10-2020 14:35 | KristÃ³f Szabados | File Added: CR_7914_v2.docx |
08-10-2020 14:35 | KristÃ³f Szabados | Note Added: 0015781 |
08-10-2020 14:36 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
08-10-2020 14:36 | KristÃ³f Szabados | Status | assigned => confirmed
08-10-2020 15:43 | Jacob Wieland - Spirent | Note Added: 0015783 |
08-10-2020 15:43 | Jacob Wieland - Spirent | Status | confirmed => resolved
08-10-2020 15:43 | Jacob Wieland - Spirent | Resolution | open => fixed
08-10-2020 15:43 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Jens Grabowski
17-12-2020 14:30 | Gyorgy Rethy | Note Added: 0015883 |
17-12-2020 14:30 | Gyorgy Rethy | Status | resolved => closed
17-12-2020 14:30 | Gyorgy Rethy | Fixed in Version | => V4.9.1 (ongoing)
17-12-2020 14:30 | Gyorgy Rethy | Target Version | => V4.9.1 (ongoing)
23-12-2020 13:59 | Jens Grabowski | Assigned To | Jens Grabowski => Gyorgy Rethy
23-12-2020 13:59 | Jens Grabowski | Status | closed => assigned
23-12-2020 13:59 | Jens Grabowski | Status | assigned => closed

Notes

(0015753)
Gyorgy Rethy
24-08-2020 11:31

Actually, I think clause 6.4.2 is correct and B.3.7 should be amended. The intension of the encoding instruction is not forcing the replacement of "normal" characters with their escape codes, but rather enable to control which way of escaping to use, IF a character is being escaped.
BUT, to provide a backward compatible correction, tool implementations should be checked and choose the solution, which majority of the tools support.

(0015759)
KristÃ³f Szabados
06-10-2020 11:09

Uploaded initial proposal.

(0015762)
Jacob Wieland - Spirent
06-10-2020 14:15

I would also think that only those characters that MUST be escaped should be escaped: From the standard: except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F)

(0015781)
KristÃ³f Szabados
08-10-2020 14:35

re-phrased accordingly. Please check.

(0015783)
Jacob Wieland - Spirent
08-10-2020 15:43

fine with me

(0015883)
Gyorgy Rethy
17-12-2020 14:30

Implemented in draft 4.8.2