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

ID | Project | Category | View Status | Date Submitted | Last Update
0007719 | Part 11: Using JSON with TTCN-3 | [TTCN-3 Change Requests] Editorial | public | 19-10-2017 15:13 | 05-01-2018 10:36

Reporter | nikolajev |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | V4.7.1 (published 2017-06) |
Target Version | V4.8.1 (published 2020-05) | Fixed in Version | V4.8.1 (published 2020-05) |

Summary | 0007719: Errors in examples for "Part 11: Using JSON with TTCN-3", "6.4.2 JSON Strings"

Description

In "Part 11: Using JSON with TTCN-3" specification V4.7.1, examples under "6.4.2 JSON Strings" cannot work as shown in specification.
1) In example for:
const JSON.String c_string1 := <actual value> with (variant "escape as short");
where <actual value> is:
"ab" & char(U7) &cu_ht & "cd"
and JSON character sequence is:
"ab\u0007\u0009cd"
"Note" in example states:
The horizontal tab character is encoded according to the encoding instruction of the referenced definition ("escape as usi") and not according to the referencing definition ("escape as short")
This however cannot work with current TTCN-3 specification, as strings are concatenated first and encoded later, encoding variant of referenced "cu_ht" string has no effect on encoding of "c_string1", entire string will use "short" escape sequence.
2) In example for:
const JSON.String c_string1 := <actual value> with (variant "escape as usi");
The same issue applies, encoding variant of referenced "cs_ht" string has no effect on encoding of "c_string1", entire string will use "usi" escape sequence.
3) In example for:
const JSON.String c_string1 := <actual value> with (variant "escape as transparent");
where <actual value> is:
"ab" & char(U7) & "cd"
and JSON character sequence is:
"ab\u0007cd"
and UTF-8 serialization of the JSON value:
2261625C75303030375C74636422
UTF-8 serialization contains 5C74 encoding of a character (horizontal tab I assume) that is not present in <actual value> or "JSON character sequence"
4) Please change to valid TTCN-3 syntax.
Attributes are enclosed in curly brackets {}, not parentheses () as used in specification:
const JSON.String c_string1 := <actual value> with (variant "...");

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7719.docx (227,069) 26-10-2017 09:57 http://oldforge.etsi.org/mantis/file_download.php?file_id=3706&type=bug CR7719_v2.docx (148,630) 26-10-2017 15:49 http://oldforge.etsi.org/mantis/file_download.php?file_id=3718&type=bug

Issue History
Date Modified | Username | Field | Change
19-10-2017 15:13 | nikolajev | New Issue |
24-10-2017 10:51 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
24-10-2017 10:51 | Jens Grabowski | Status | new => assigned
24-10-2017 10:52 | Jens Grabowski | Note Added: 0014833 |
26-10-2017 09:57 | KristÃ³f Szabados | File Added: CR7719.docx |
26-10-2017 09:58 | KristÃ³f Szabados | Note Added: 0014881 |
26-10-2017 09:58 | KristÃ³f Szabados | Status | assigned => confirmed
26-10-2017 10:17 | KristÃ³f Szabados | Note Added: 0014882 |
26-10-2017 10:17 | KristÃ³f Szabados | Status | confirmed => assigned
26-10-2017 15:49 | KristÃ³f Szabados | File Added: CR7719_v2.docx |
26-10-2017 15:50 | KristÃ³f Szabados | Note Added: 0014899 |
26-10-2017 15:50 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Tomas Urban
26-10-2017 15:50 | KristÃ³f Szabados | Status | assigned => confirmed
27-10-2017 13:00 | Tomas Urban | Note Added: 0014918 |
27-10-2017 13:00 | Tomas Urban | Status | confirmed => resolved
27-10-2017 13:00 | Tomas Urban | Resolution | open => fixed
27-10-2017 13:00 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
04-01-2018 17:00 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 11: Using JSON with TTCN-3
05-01-2018 10:36 | Gyorgy Rethy | Note Added: 0015004 |
05-01-2018 10:36 | Gyorgy Rethy | Status | resolved => closed
05-01-2018 10:36 | Gyorgy Rethy | Product Version | => V4.7.1 (published 2017-06)
05-01-2018 10:36 | Gyorgy Rethy | Fixed in Version | => V4.8.1 (published 2020-05)
05-01-2018 10:36 | Gyorgy Rethy | Target Version | => V4.8.1 (published 2020-05)

Notes

(0014833)
Jens Grabowski
24-10-2017 10:52

STF decision: Kristof to check with György.

(0014881)
KristÃ³f Szabados
26-10-2017 09:58

uploaded fix for issues 3 and 4. Issues 1 and 2 need more discussion (might need to be handled in separate CR).

(0014882)
KristÃ³f Szabados
26-10-2017 10:17

incorrectly set to confirmed

(0014899)
KristÃ³f Szabados
26-10-2017 15:50

The examples mentioned in issue 1 and 2 are corrected too. Please check.

(0014918)
Tomas Urban
27-10-2017 13:00

No problems found, the resolution is ready to be included in the next version of the "Using JSON with TTCN-3" specification.

(0015004)
Gyorgy Rethy
05-01-2018 10:36

Implemented in draft version V4.7.2.