Austin Group Defect Tracker

Aardvark Mark IV


Viewing Issue Simple Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Type Date Submitted Last Update
0001638 [Issue 8 drafts] Base Definitions and Headers Objection Clarification Requested 2023-03-03 10:03 2023-05-16 11:06
Reporter kre View Status public  
Assigned To
Priority normal Resolution Accepted As Marked  
Status Applied   Product Version Draft 2.1
Name Robert Elz
Organization
User Reference
Section XBD 8.3
Page Number 162
Line Number 5648-5651
Final Accepted Text See Note: 0006204.
Summary 0001638: Requirement that TZ "std" and "dst" be 3 chars long (when given) is apparently ambiguous
Description This could be filed against 7 TC2, and I think probably D3 (when it
appears as well) - I don't think the text has changed.

It wasn't changed by 0001619 though perhaps should have been.

The current (as in D2.1) text says:

   The interpretation of these fields is unspecified if either field is
   less than three bytes (except for the case when dst is missing),

To me that was always clear enough, it means that "dst" doesn't have to be
at least 3 chars, if it was omitted, that would be absurd. But on a (unrelated) mailing list, I have just seen a claim:

   When /dst/ is missing, /std/ can be less than 3 bytes.

which is obviously based upon reading that "except" as applying to both
"std" and "dst" rather than just "dst" which I have always assumed.

And when the text is read, without already having a preconceived idea of
what it is intended to mean, I can see how that interpretation is possible.

Beyond that, for all parts of the POSIX TZ strip specification, now that
0001619 has been applied, we really need to remove all "is unspecified"
in invalid cases - those should now be simply invalidating the string as
being considered as a POSIX TZ string, leaving it open to be considered as
one of the new form added by 0001619.

That part I am not going to supply new text for here, that can wait until
after D3 is available, when we know what we're working with.
Desired Action Replace the paragraph in lines 5648-5651 (D2.1) on page 162

The interpretation of these fields is unspecified if either
field is less than three bytes (except for the case when dst is missing),
more than {TZNAME_MAX} bytes, or if they contain characters
other than those specified.


with (something like - and here I am making the working, for just this one
case for now, invalidate the string, as being a POSIX TZ string):

If std contains less than 3 bytes, or dst
(if present in the string) contains less than 3 bytes, or if either
std or dst contain more than {TZNAME_MAX} bytes, or
if either of those fields contains any characters other than those
specified, the string will not be a valid string of this format, and
shall be considered as a candidate for being of the third format.


(Yes, I know, that's ugly - someone else can do better...)
Tags applied_after_i8d3, tc3-2008
Attached Files

- Relationships
related to 0001619Applied Add support for TZ=Area/Location 
related to 0001639Applied Clarify minimun length requirement of "quoted" std and dst names in POSIX TZ string. 

-  Notes
(0006187)
kre (reporter)
2023-03-03 10:11

Rather than "not be a valid string of this format, and
shall be considered as a candidate for being of the third format."
maybe it could say something like

"shall be a failure to match the syntax of this format" which then
fits with the text added in Note: 0006073
(0006188)
Don Cragun (manager)
2023-03-03 14:31

Occurrences of "bugno:" and "POSIZ" in the Description have been changed to "bugid:" and "POSIX", respectively.
(0006204)
Don Cragun (manager)
2023-03-16 15:26

Change:
The interpretation of these fields is unspecified if either field is less than three bytes (except for the case when dst is missing), more than {TZNAME_MAX} bytes, or if they contain characters other than those specified.
to:
The interpretation of std and, if present, dst is unspecified if the field is less than three bytes or more than {TZNAME_MAX} bytes, or if it contains characters other than those specified.

- Issue History
Date Modified Username Field Change
2023-03-03 10:03 kre New Issue
2023-03-03 10:03 kre Name => Robert Elz
2023-03-03 10:03 kre Section => XBD 8.3
2023-03-03 10:03 kre Page Number => 162
2023-03-03 10:03 kre Line Number => 5648-5651
2023-03-03 10:11 kre Note Added: 0006187
2023-03-03 14:31 Don Cragun Note Added: 0006188
2023-03-03 14:31 Don Cragun Description Updated
2023-03-03 16:56 Guy Harris Issue Monitored: Guy Harris
2023-03-16 15:12 nick Relationship added related to 0001619
2023-03-16 15:26 Don Cragun Note Added: 0006204
2023-03-16 15:26 Don Cragun Status New => Resolved
2023-03-16 15:26 Don Cragun Resolution Open => Accepted As Marked
2023-03-16 15:27 Don Cragun Final Accepted Text => See Note: 0006204.
2023-03-16 15:28 Don Cragun Tag Attached: tc3-2008
2023-03-16 15:48 geoffclare Relationship added related to 0001639
2023-05-16 11:06 geoffclare Status Resolved => Applied
2023-05-16 11:06 geoffclare Tag Attached: applied_after_i8d3


Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker