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

ID | Project | Category | View Status | Date Submitted | Last Update
0007913 | Part 11: Using JSON with TTCN-3 | [TTCN-3 Change Requests] Editorial | public | 05-03-2020 06:03 | 17-12-2020 15:29

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 | 0007913: conflicting examples for solidus encoding

Description

The example in section 6.4.2 for encoding the solidus character with "escape as usi" variant shows:
"ab/cd" | "ab/cd" | 2261622F636422 | JSON doesn't require to escape the solidus character
But the example in Annex A shows:
const JSON.String_usi cu_sol := "/"; // encoded as "\u002F" (Solidus or Slash)
It might happen that JSON does not require the escaping of the solidus, but from a didactical point of view:
- either the first example should also show an example of the escaped version (to give a consistent view with the end example)
- or in the end example also point out that there are 2 equally valid ways to encode the solidus character.
Right now the standard sounds confusing, becuse the annex clearly chooses 1 way of encoding, yet 6.4.2 sound to imply that the standard is not choosing 1 way of encoding.

Steps To Reproduce |
Additional Information | I was looking at version v4.8.1 (2018-05) available from www.ttcn-3.org
Tags | No tags attached.
Relationships |
Attached Files | CR_7913.docx (156,117) 10-08-2020 19:20 http://oldforge.etsi.org/mantis/file_download.php?file_id=3903&type=bug CR_7913_v2.docx (154,710) 11-08-2020 15:28 http://oldforge.etsi.org/mantis/file_download.php?file_id=3913&type=bug

Issue History
Date Modified | Username | Field | Change
05-03-2020 06:03 | KristÃ³f Szabados | New Issue |
10-08-2020 11:05 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
10-08-2020 11:05 | Jens Grabowski | Status | new => assigned
10-08-2020 19:20 | KristÃ³f Szabados | File Added: CR_7913.docx |
10-08-2020 19:21 | KristÃ³f Szabados | Note Added: 0015674 |
11-08-2020 10:11 | KristÃ³f Szabados | Note Added: 0015675 |
11-08-2020 10:12 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
11-08-2020 12:06 | Jacob Wieland - Spirent | Note Added: 0015687 |
11-08-2020 12:06 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => KristÃ³f Szabados
11-08-2020 12:33 | KristÃ³f Szabados | Note Added: 0015692 |
11-08-2020 15:28 | KristÃ³f Szabados | File Added: CR_7913_v2.docx |
11-08-2020 15:29 | KristÃ³f Szabados | Note Added: 0015697 |
11-08-2020 15:29 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Jacob Wieland - Spirent
11-08-2020 15:43 | Jacob Wieland - Spirent | Note Added: 0015698 |
11-08-2020 15:43 | Jacob Wieland - Spirent | Status | assigned => resolved
11-08-2020 15:43 | Jacob Wieland - Spirent | Resolution | open => fixed
11-08-2020 15:43 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
17-12-2020 15:29 | Gyorgy Rethy | Note Added: 0015887 |
17-12-2020 15:29 | Gyorgy Rethy | Status | resolved => closed
17-12-2020 15:29 | Gyorgy Rethy | Fixed in Version | => V4.9.1 (ongoing)
17-12-2020 15:29 | Gyorgy Rethy | Target Version | => V4.9.1 (ongoing)

Notes

(0015674)
KristÃ³f Szabados
10-08-2020 19:21

updated example to show escaped form consistent with example in annex.

(0015675)
KristÃ³f Szabados
11-08-2020 10:11

please review

(0015687)
Jacob Wieland - Spirent
11-08-2020 12:06

the changed commment isn't gramatically correct, I have no idea what it means.

(0015692)
KristÃ³f Szabados
11-08-2020 12:33

Would it be better to phrase it like this? Escaped solidus character (escaping solidus is optional in JSON)

(0015697)
KristÃ³f Szabados
11-08-2020 15:29

changed comment. please review.

(0015698)
Jacob Wieland - Spirent
11-08-2020 15:43

ok, fine

(0015887)
Gyorgy Rethy
17-12-2020 15:29

Implemented in draft 4.8.2