ETSI's Bug Tracker - TDL | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0008220 | TDL | New Feature | public | 11-01-2024 19:13 | 11-01-2024 19:13 |
Reporter | Philip Makedonski | ||||
Assigned To | Philip Makedonski | ||||
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Platform | OS | OS Version | |||
Clause Reference(s) | Part 1, Clause 6.3.2 + related | ||||
Source (company - Author) | Martti Käarik, Elvior | ||||
Summary | 0008220: Add MemberReference to ParameterBinding to support path expressions | ||||
Description | Currently it can be cumbersome to specify only deeply nested values in data uses in particular, for example given a data instance: //base instance s1 ss1 ( //TODO: do we need this here as well? f1 = "a", f2 = ( p1 = "a", p2 = "b", p3 = ( o1 = "x", o2 = "y", o3 = ( r1 = "z" ), o4 = ["a", "b"] ) ) ) If in a data use we need to override r3 it will require at least specifying all the parent structures, e.g.: tester::g sends ss1 ( f2 = ( p3 = ( o3 = ( r1 = "z" ) ) ) ) to sut::g Apart from that, the semantics are not quite clear, especially when it comes to collections, e.g. if a member of a collection item is to be overridden, is the entire collection item overridden or just the member? Is the entire collection overridden or just the item in question? In other languages so called "path-expressions" are a common shorthand syntax to overcome some of the issues. They could also help resolve the unclear semantics where the expanded syntax can be used to reassign entire structures and the path-expression to override individual members. The above would be condensed to: tester::g sends ss1 ( f2.p3.o3.r1 = "z" ) to sut::g See also https://labs.etsi.org/rep/top/ide/-/issues/56 [^] and https://labs.etsi.org/rep/top/ide/-/issues/59 [^] | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
11-01-2024 19:13 | Philip Makedonski | New Issue | |||
11-01-2024 19:13 | Philip Makedonski | Status | new => assigned | ||
11-01-2024 19:13 | Philip Makedonski | Assigned To | => Philip Makedonski |
There are no notes attached to this issue. |