ISSUES LIST Austin/19

1. ISSUE if SGML is required, this may mean that the SUD rather SUS is used as a base doc, which is less familiar to most people in the WG. Should we mandate that the specification is developed in SGML?

Resolved; SGML is not a requirement for the base doc, but is left entirely to the editor. There will probably be an SGML version generated at the end.

2. ISSUE: how to handle overlapping functions between ISO-C and the joint standard. Proposal: document all functions but clearly identify which words give way to C standard

3. ISSUE: how to handle UNIX extended functionality. AUSTIN/18 identifies a large number of functions not currently in POSIX (and marked as EX in XSH/XCU) that may require to be optional, or new mandatory. Some may become new legacy/obsolete.