Minutes of the 16th July 2015 Teleconference     Austin-721 Page 1 of 1
Submitted by Andrew Josey, The Open Group.  17th July 2015

Attendees:
    Mark Ziegast, SHware Systems
    Don Cragun, IEEE PASC OR
    David Clissold, IBM
    Roger Faulkner, Oracle, The Open Group OR
    Martin Rehak, Oracle
    Eric Blake, Red Hat
    Jim Grisanzio, Oracle
    Joerg Schilling, FOKUS Fraunhofer
    Geoff Clare, The Open Group
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Richard Hansen, BBN 
    Andrew Josey, The Open Group (partial)

Apologies
	None.

* General news

The IEEE ballot invitation has been sent out during the week
and closes on August 12.

The annual status reports for SC22 have been prepared
and are in the document register as Austin/718 and Austin/719.
A separate status report has been submitted to the PASC
SEC as Austin/720.


* Outstanding actions

( Please note that I have flushed this section to shorten the minutes -
to locate the last set of outstanding actions, look
to the minutes from 26 Feb 2015)

Bug 0000887: printf and other functions appear many times in search results OPEN
http://austingroupbugs.net/view.php?id=887
Andrew is investigating.

Bug 0000900: add qsort_r        OPEN
http://austingroupbugs.net/view.php?id=900

The consensus was that its a good idea to add the suggested interface.
The usual requirements regarding a sponsor for a new interface
apply.

Action: Open Group OR , to ask the Base WG if they wish to sponsor
the additional qsort interface proposed here.

Bug  0000901: reserve _POSIX* shell option namespace for future use        OPEN
http://austingroupbugs.net/view.php?id=901

The forward plan for this bug remains as before:

    Richard: file a new bug report with a concrete feature that
    would use the _POSIX* namespace (as motivation for reserving
    set -o _POSIX*)

    All: debate the proposed feature.  If it's something we want,
    then revisit bug #901.  If not, close bug #901.



Bug 0000922: Implementations should be allowed to change/remove implementation-defined environment variables         OPEN
http://austingroupbugs.net/view.php?id=922

This item remains open. 

Action on Eric: propose wording for Issue 8 to add secure_getenv(),
and make it clear that deleting from environment without explicit
request is not compliant, but ignoring is fine.

For Issue 7 TC 2: Create new bug to add additional conditions on
what makes TMPDIR valid, vs. undefined behavior; also add future
directions to getenv() to mention secure_getenv()

* Current Business


Bug #960: export can fail        OPEN
http://austingroupbugs.net/view.php?id=960

Action: Eric to incorporate Geoff's comments, add wording for 'exit'
and 'return'


Bug #964: should m4 treat mkstemp failure as an error?       Accepted
http://austingroupbugs.net/bug_view_page.php?bug_id=964

This item is tagged for TC2-2008.
An interpretation is required.

Bug #967: character set confusion Accepted as Marked
http://austingroupbugs.net/bug_view_page.php?bug_id=967

This item is tagged for TC2-2008

On page 125 lines 3479-3481, change:

    The first eight entries in [xref to Table 6-1] are defined in
    the ISO/IEC 6429:1992 standard and the rest of the characters
    are defined in the ISO/IEC 10646-1:2000 standard.

to:

    The first eight entries in [xref to Table 6-1] and all characters
    in [xref to Table 6-2] are defined in the ISO/IEC 6429:1992
    standard. The rest of the characters in [xref to Table 6-1] are
    defined in the ISO/IEC 10646-1:2000 standard.

On page 125 line 3483, change:

    | Symbolic Name | Glyph | UCS | Description |

to:

    | Symbolic Name(s) | Glyph | UCS | Description |

On page 125 lines 3485-3491, change:

    | <alert>           |  | <U0007> | BELL (BEL)                |
    | <backspace>       |  | <U0008> | BACKSPACE (BS)            |
    | <tab>             |  | <U0009> | CHARACTER TABULATION (HT) |
    | <carriage-return> |  | <U000D> | CARRIAGE RETURN (CR)      |
    | <newline>         |  | <U000A> | LINE FEED (LF)            |
    | <vertical-tab>    |  | <U000B> | LINE TABULATION (VT)      |
    | <form-feed>       |  | <U000C> | FORM FEED (FF)            |

to (note the description column changes to match the Unicode spec,
and the change in line order):

    | <alert>, <BEL>          |  | <U0007> | BELL                 |
    | <backspace>, <BS>       |  | <U0008> | BACKSPACE            |
    | <tab>, <HT>             |  | <U0009> | CHARACTER TABULATION |
    | <newline>, <LF>         |  | <U000A> | LINE FEED (LF)       |
    | <vertical-tab>, <VT>    |  | <U000B> | LINE TABULATION      |
    | <form-feed>, <FF>       |  | <U000C> | FORM FEED (FF)       |
    | <carriage-return>, <CR> |  | <U000D> | CARRIAGE RETURN (CR) |

On page 125 lines 3505-3510, change:

    | <hyphen-minus> | - | <U002D> | HYPHEN-MINUS |
    | <hyphen>       | - | <U002D> | HYPHEN-MINUS |
    | <full-stop>    | . | <U002E> | FULL STOP    |
    | <period>       | . | <U002E> | FULL STOP    |
    | <slash>        | / | <U002F> | SOLIDUS      |
    | <solidus>      | / | <U002F> | SOLIDUS      |

to:

    | <hyphen-minus>, <hyphen> | - | <U002D> | HYPHEN-MINUS |
    | <full-stop>, <period>    | . | <U002E> | FULL STOP    |
    | <slash>, <solidus>       | / | <U002F> | SOLIDUS      |

On page 126 lines 3556-3557, change:

    | <backslash>       | \ | <U005C> | REVERSE SOLIDUS |
    | <reverse-solidus> | \ | <U005C> | REVERSE SOLIDUS |

to:

    | <backslash>, <reverse-solidus> | \ | <U005C> | REVERSE SOLIDUS |

On page 126 lines 3559-3562, change:

    | <circumflex-accent> | ^ | <U005E> | CIRCUMFLEX ACCENT |
    | <circumflex>        | ^ | <U005E> | CIRCUMFLEX ACCENT |
    | <low-line>          | _ | <U005F> | LOW LINE          |
    | <underscore>        | _ | <U005F> | LOW LINE          |

to:

    | <circumflex-accent>, <circumflex> | ^ | <U005E> | CIRCUMFLEX ACCENT |
    | <low-line>, <underscore>          | _ | <U005F> | LOW LINE          |

On page 127 lines 3591-3592, change:

    | <left-brace>         | { | <U007B> | LEFT CURLY BRACKET |
    | <left-curly-bracket> | { | <U007B> | LEFT CURLY BRACKET |

to:

    | <left-brace>, <left-curly-bracket> | { | <U007B> | LEFT CURLY BRACKET |

On page 127 lines 3594-3595, change:

    | <right-brace>         | } | <U007D> | RIGHT CURLY BRACKET |
    | <right-curly-bracket> | } | <U007D> | RIGHT CURLY BRACKET |

to:

    | <right-brace>, <right-curly-bracket> | } | <U007D> | RIGHT CURLY BRACKET |


On page 127 lines 3601-3603, delete the following sentence:

    The table contains more than one symbolic character name for
    characters whose traditional name differs from the chosen name.


On page 128 lines 3623-3625, after applying the changes in 0000663, delete:

    that are not included in [xref to Table 6-1]


On page 129 lines 3683-3691, change:

    Each symbolic name specified in [xref to Table 6-1] (on page
    125) shall be included in the file and shall be mapped to a
    unique coding value, except as noted below. The glyphs represented
    by the C character constants <tt>'{'</tt>, <tt>'}'</tt>,
    <tt>'_'</tt>, <tt>'-'</tt>, <tt>'/'</tt>, <tt>'\\'</tt>,
    <tt>'.'</tt>, and <tt>'ˆ'</tt> have more than one symbolic name;
    all symbolic names for each such glyph shall be included, each
    with identical encoding. If some or all of the control characters
    identified in [xref to Table 6-2] (on page 130) are supported
    by the implementation, the symbolic names and their corresponding
    encoding values shall be included in the file. The encoding
    values shall each be represented in a single byte. Some of the
    encodings associated with the symbolic names in [xref to Table
    6-2] (on page 130) may be the same as characters found in [xref
    to Table 6-1] (on page 125); both names shall be provided for
    each encoding.

to:

    Each symbolic name specified in [xref to Table 6-1] (on page
    125) shall be included in the file. Each character in [xref to
    Table 6-1] (each row in the table) shall be mapped to a unique
    coding value. For each character in [xref to Table 6-2] that
    exists in the character set described by the file, the character's
    symbolic name(s) from [xref to Table 6-2] and the character's
    single-byte encoding value shall be included in the file.


On page 130 lines 3692-3698, change:

    Table 6-2 Control Character Set

    <ACK> <DC2> <ENQ> <FS>  <IS4> <SOH>
    <BEL> <DC3> <EOT> <GS>  <LF>  <STX>
    <BS>  <DC4> <ESC> <HT>  <NAK> <SUB>
    <CAN> <DEL> <ETB> <IS1> <RS>  <SYN>
    <CR>  <DLE> <ETX> <IS2> <SI>  <US>
    <DC1> [EM]  <FF>  <IS3> <SO>  <VT>

to:

    Table 6-2 Non-Portable Control Characters

    | Symbolic Name(s) |   UCS   | Description                 |
    +------------------+---------+-----------------------------+
    | <SOH>            | <U0001> | START OF HEADING            |
    | <STX>            | <U0002> | START OF TEXT               |
    | <ETX>            | <U0003> | END OF TEXT                 |
    | <EOT>            | <U0004> | END OF TRANSMISSION         |
    | <ENQ>            | <U0005> | ENQUIRY                     |
    | <ACK>            | <U0006> | ACKNOWLEDGE                 |
    | <SO>             | <U000E> | SHIFT OUT                   |
    | <SI>             | <U000F> | SHIFT IN                    |
    | <DLE>            | <U0010> | DATA LINK ESCAPE            |
    | <DC1>            | <U0011> | DEVICE CONTROL ONE          |
    | <DC2>            | <U0012> | DEVICE CONTROL TWO          |
    | <DC3>            | <U0013> | DEVICE CONTROL THREE        |
    | <DC4>            | <U0014> | DEVICE CONTROL FOUR         |
    | <NAK>            | <U0015> | NEGATIVE ACKNOWLEDGE        |
    | <SYN>            | <U0016> | SYNCHRONOUS IDLE            |
    | <ETB>            | <U0017> | END OF TRANSMISSION BLOCK   |
    | <CAN>            | <U0018> | CANCEL                      |
    | [EM]             | <U0019> | END OF MEDIUM               |
    | <SUB>            | <U001A> | SUBSTITUTE                  |
    | <ESC>            | <U001B> | ESCAPE                      |
    | <IS4>, <FS>      | <U001C> | INFORMATION SEPARATOR FOUR  |
    | <IS3>, <GS>      | <U001D> | INFORMATION SEPARATOR THREE |
    | <IS2>, <RS>      | <U001E> | INFORMATION SEPARATOR TWO   |
    | <IS1>, <US>      | <U001F> | INFORMATION SEPARATOR ONE   |
    | <DEL>            | <U007F> | DELETE                      |

On page 198 lines 6484-6500, delete the Symbolic Name column.

Note that the square brackets in [EM] should be angle brackets (I
can't get Mantis to escape the angle brackets, so it thinks I want
to italicize something).


Bug #958: misleading description for the "read" utility       Accepted as Marked
http://austingroupbugs.net/bug_view_page.php?bug_id=958

This item is tagged for TC2-2008

On page 3154 line 105406, change:

    read - read a line from standard input
to:
    read - read from standard input into shell variables

On page 3154 change line 105410 from:
    The read utility shall read a single line from standard input.
to:
    The read utility shall read a single logical line from standard
    input into one or more shell variables.


Bug #962: Should utilities continue when reading one of multiple files fails? Accepted as Marked
http://austingroupbugs.net/bug_view_page.php?bug_id=962

This item is tagged for TC2-2008
An interpretation is required.

Interpretation response:
The standard states that sort must carry on processing later operands
after an error is encountered with an earlier operand, and conforming
implementations must conform to this. However, concerns have been
raised about this which are being referred to the sponsor.

Rationale:
Existing implementations of sort stop processing immediately after
encountering an error when reading input files.

Notes to the Editor (not part of this interpretation):
On page 3211 line 107618 (sort OPERANDS), append the following to
the description of the file operand:

    If sort encounters an error when opening or reading a file
    operand, it may exit without writing any output to standard
    output or processing later operands.


On page 3213 line 107687 (sort CONSEQUENCES OF ERRORS), change from:

    Default.

to:

    The default requirements shall apply, except that if sort
    encounters an error when opening or reading a file operand, it
    may exit without writing any output to standard output or
    processing later operands.


Bug #969: diff output format for -u/-U is too restrictive Accepted
http://austingroupbugs.net/view.php?id=969

This item is tagged for TC2-2008
An interpretation is required.

Interpretation response:
The standard does not speak to this issue, and as such no conformance
distinction can be made between alternative implementations based
on this. This is being referred to the sponsor.

Rationale:
The standard only allows one form for specifying single line changes
in unified diff output, but existing practice uses two forms.

Notes to the Editor (not part of this interpretation):
Make the change specified in the Desired Action.


Action on Andrew to progress any pending interpretations
(completed after the call, 962,964 and 969)


Next Steps
----------
The next call is on July 23, 2015 (a Thursday)
Apologies in Advance:
     A. Josey, 23rd/30th

Calls are anchored on US time. (8am Pacific) 

This call will be for the regular 90 minutes.

http://austingroupbugs.net

An IRC channel will be available for the meeting
irc://irc.freenode.net/austingroupbugs

An etherpad is usually up for the meeting, with a URL using the date format as below:

http://posix@posix.rhansen.org:9001/p/201x-mm-dd
password=2115756#