ETSI's Bug Tracker - Ext Pack: Advanced Matching (ES 203 022)
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007827 | Ext Pack: Advanced Matching (ES 203 022) | Clarification | public | 07-03-2019 12:29 | 17-12-2019 10:11

Reporter | Martin Hauch |
Assigned To | Jens Grabowski |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v1.2.1 (published 2018-05) |
Target Version |  | Fixed in Version |  |
Clause Reference(s) | 5.3.4
Source (company - Author) | Devoteam - Martin Hauch
TS version | ?

Summary | 0007827: Semantic of disjunction

Description

In chapter 5.3.4 one sentence is:
It provides a successful match, if
and only if one of the disjunction alternatives matches the maximal subset of still unmatched elements inside the value
that still allows the containing template to match the whole value.
This means, if more than on disjunction alternatives are matching the result is mismatch.
Other sentence is:
The disjunction alternatives are matched in the order of their specification inside the disjunction matching mechanism
(i.e. from left to right) so that the leftmost alternative that fulfils the above condition contributes to the successful match
while the following disjunction alternatives are ignored.
If one disjunction alternative is matching all following alternatives are not checked, which leads to a different result?
Could this be clarified? Perhaps change 1st sentence to:
It provides a successful match, if
and only if at least one of the disjunction alternatives ...

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7827.docx (124,502) 06-08-2019 08:54 http://oldforge.etsi.org/mantis/file_download.php?file_id=3818&type=bug

Issue History
Date Modified | Username | Field | Change
07-03-2019 12:29 | Martin Hauch | New Issue |
07-03-2019 13:58 | Jacob Wieland - Spirent | Note Added: 0015335 |
06-08-2019 08:54 | Jacob Wieland - Spirent | File Added: CR7827.docx |
06-08-2019 08:54 | Jacob Wieland - Spirent | Note Added: 0015367 |
06-08-2019 08:54 | Jacob Wieland - Spirent | Assigned To | => Tomas Urban
06-08-2019 08:54 | Jacob Wieland - Spirent | Status | new => confirmed
07-08-2019 09:19 | Tomas Urban | Note Added: 0015389 |
07-08-2019 09:19 | Tomas Urban | Status | confirmed => resolved
07-08-2019 09:19 | Tomas Urban | Resolution | open => fixed
07-08-2019 09:19 | Tomas Urban | Assigned To | Tomas Urban => Jens Grabowski
17-12-2019 10:11 | Jens Grabowski | Status | resolved => closed

Notes

(0015335)
Jacob Wieland - Spirent
07-03-2019 13:58

Yes, the intention of the sentence was 'one' in the sense of 'at least one', not in the sense of 'exactly one'. We'll clarify this.

(0015367)
Jacob Wieland - Spirent
06-08-2019 08:54

please review

(0015389)
Tomas Urban
07-08-2019 09:19

Proposed resolution fixes the reported issue and it can be added to the next version of the standard.