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

ID | Project | Category | View Status | Date Submitted | Last Update
0007722 | Part 11: Using JSON with TTCN-3 | [TTCN-3 Change Requests] Clarification | public | 25-10-2017 10:57 | 05-01-2018 09:34

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 | 0007722: "Part 11: Using JSON with TTCN-3":"B.3.4 Name as" syntax is confusing, does not match examples throughout specification

Description

1) Single quotes or not for freetext?
There are multiple examples in specification
with { variant "name as 'freetext'"} and without
with { variant "name as freetext"}
2) What can "freetext" or "alias" contain?
B.3.4 description states "The syntax of the alias is the same as the syntax of TTCN-3 identifiers (regex: [A-Za-z][A-Za-z0-9_]*)."
But some examples of the specification show "name as 'house no.' "
There are 2 characters that are not allowed in TTCN-3 identifier " ", ".".
If alias syntax is the same of TTCN-3 identifiers, why is alias used at all?
TTCN-3 field name is a TTCN-3 identifier, which makes alias and field name syntax exactly the same.
Alias only makes sense if any JSON string is allowed to be used.
3) In "B.3.4 Name as" examples contain "JSON:" prefix inside "name as ..." variant:
variant(numericID) "JSON:name as ID";
variant(email) "JSON:name as Email";
variant(name) "JSON:name as Name";
prefix should be removed.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7722.docx (142,072) 26-10-2017 11:53 http://oldforge.etsi.org/mantis/file_download.php?file_id=3712&type=bug

Issue History
Date Modified | Username | Field | Change
25-10-2017 10:57 | nikolajev | New Issue |
26-10-2017 11:44 | KristÃ³f Szabados | Assigned To | => KristÃ³f Szabados
26-10-2017 11:44 | KristÃ³f Szabados | Status | new => assigned
26-10-2017 11:49 | KristÃ³f Szabados | Note Added: 0014887 |
26-10-2017 11:53 | KristÃ³f Szabados | File Added: CR7722.docx |
26-10-2017 11:54 | KristÃ³f Szabados | Note Added: 0014888 |
26-10-2017 11:54 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Tomas Urban
26-10-2017 11:54 | KristÃ³f Szabados | Status | assigned => confirmed
27-10-2017 12:43 | Tomas Urban | Note Added: 0014916 |
27-10-2017 12:43 | Tomas Urban | Status | confirmed => resolved
27-10-2017 12:43 | Tomas Urban | Resolution | open => fixed
27-10-2017 12:43 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
04-01-2018 17:01 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Part 11: Using JSON with TTCN-3
05-01-2018 09:34 | Gyorgy Rethy | Note Added: 0015001 |
05-01-2018 09:34 | Gyorgy Rethy | Status | resolved => closed
05-01-2018 09:34 | Gyorgy Rethy | Product Version | => V4.7.1 (published 2017-06)
05-01-2018 09:34 | Gyorgy Rethy | Fixed in Version | => V4.8.1 (published 2020-05)
05-01-2018 09:34 | Gyorgy Rethy | Target Version | => V4.8.1 (published 2020-05)

Notes

(0014887)
KristÃ³f Szabados
26-10-2017 11:49

STF discussion: - the freetext should be in '', otherwise it could be confused with definitions and the changeCase options - the "JSON:" is also to be removed. The core standard desribes the "variant {"Codec1","Codec2"}."Rule1"" format to specify if a variant is related to a specific encoding.

(0014888)
KristÃ³f Szabados
26-10-2017 11:54

Please check

(0014916)
Tomas Urban
27-10-2017 12:43

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

(0015001)
Gyorgy Rethy
05-01-2018 09:34

Corrected in draft V4.7.2.