ETSI's Bug Tracker - Part 09: Using XML with TTCN-3
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007238 | Part 09: Using XML with TTCN-3 | Clarification | public | 04-12-2015 13:58 | 12-01-2017 09:13

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | no change required |
Platform |  | OS |  | OS Version |
Product Version | v4.7.1 (published 2016-07) |
Target Version | v4.8.1 (published 2017-05) | Fixed in Version | v4.8.1 (published 2017-05) |
Clause Reference(s) | 6.5
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0007238: Follow-up on date/time changes in XSD 1.1
Description | CR6868 pinpointed a change in XSD 1.1, related to XSD 1.0: the new version allows year 0000, while the old one disallowed this. This specific case (the year pattern in clause 6.5 and Annex A) has been changed. However, other potential changes in XSD date/time types shall also be checked and applied in Part-9.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
04-12-2015 13:58 | Gyorgy Rethy | New Issue |
06-01-2016 09:23 | Gyorgy Rethy | Target Version | => v4.8.1 (published 2017-05)
18-07-2016 11:18 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
18-07-2016 11:18 | Jens Grabowski | Status | new => assigned
20-07-2016 10:22 | KristÃ³f Szabados | Note Added: 0013998 |
20-07-2016 10:24 | KristÃ³f Szabados | Note Added: 0013999 |
20-07-2016 10:24 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Gyorgy Rethy
20-07-2016 10:24 | KristÃ³f Szabados | Status | assigned => feedback
18-08-2016 15:54 | Jacob Wieland - Spirent | Note Added: 0014160 |
17-11-2016 14:10 | Jens Grabowski | Status | feedback => closed
17-11-2016 14:10 | Jens Grabowski | Resolution | open => no change required
12-01-2017 09:13 | Gyorgy Rethy | Fixed in Version | => v4.8.1 (published 2017-05)

Notes

(0013998)
KristÃ³f Szabados
20-07-2016 10:22

I found one item that might need to be changed.
Part 9 describes year and yearExpanded as separate entities:
"
year := "[0-9]#(4)",
yearExpansion := "-#(,1)([1-9][0-9]#(0,))#(,1)",
"
Which can follow each other in patterns:
"
type charstring DateTime (pattern
"{yearExpansion}{year}{dash}{month}{dash}{dayOfMonth}T({hour}{cln}{minute}{cln}{second}" &
"{sFraction}|{endOfDayExt}){ZorTimeZoneExt}"
)
with {
variant "XSD:dateTime";
}
"
According to XSD schema (https://www.w3.org/TR/xmlschema11-2/#nt-yrFrag [^]) these should be one item:
"
[16] dateTimeLexicalRep ::= yearFrag '-' monthFrag '-' dayFrag 'T' ((hourFrag ':' minuteFrag ':' secondFrag) | endOfDayFrag) timezoneFrag?
[56] yearFrag ::= '-'? (([1-9] digit digit digit+)) | ('0' digit digit digit))
"
ISO 8601:2004(E) in section 4.1.2.4 says that the year element is expanded with more digits:
"
If, by agreement, expanded representations are used, the formats shall be as specified below. The
interchange parties shall agree the additional number of digits in the time element year. In the examples below
it has been agreed to expand the time element year with two digits
"
I believe the current description of the related patterns in part 9 should be changed to:
"
type charstring Date (pattern
"({yearExpansion}|{year}){dash}{month}{dash}{dayOfMonth}{ZorTimeZoneExt}"
) with {
variant "XSD:date";
}
"
and the yearExpansion to "(-#(,1)[1-9][0-9]#(3,)|0[0-9]#(3))"

(0013999)
KristÃ³f Szabados
20-07-2016 10:24

Could you comment on the changes proposed in the previous comment? (change the yearExpansion and the patterns it is used in)

(0014160)
Jacob Wieland - Spirent
18-08-2016 15:54

would that in any way change the semantics as we have them now? If not, I would not change anything.