Austin Group Minutes of the 15 June Teleconference Austin-303 Page 1 of 1 Submitted by Andrew Josey, The Open Group. June 16, 2006 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Ulrich Drepper, Red Hat Nick Stoughton, USENIX, ISO/IEC OR Mark Brown, IBM, TOG OR Action item review --------------------- ACTION AI-2006-02-04: Nick Stoughton to submit an aardvark against link() when the appropriate time is reached w.r.t. approval of strawman 2. STATUS: OPEN ACTION AI-2006-02-28: AJ to filter the XSH, XCU and XRAT aardvarks for SD5 and interps material. (ongoing action) STATUS: OPEN, ongoing in progress The cutoff for draft 1 was June 12. We are not planning to take any changes past that date at the moment. Austin/280r1 is the latest notes arising from SD5 and is frozen The new document with new issues arising from SD5 is Austin/302 ACTION AI-2006-04-01: Nick Stoughton/Andrew Josey to send reports to SC22 prior to the Sep 2006 SC22 Plenary (due date: July 2006) STATUS: OPEN PASC ---- The SEC will commence a vote on approving the PAR on June 24. Once approved by the SEC we should also submit this to ISO SC22 for information. Aardvark Defect report processing: ----------------------------------- XBD ERN 68 XBD limits.h tracing limits OPEN Fwded to SSWG-RT (Andrew has completed the action) Andrew had also sent email to Joe Gwinn requesting help from the SSWG-RT but is yet to get a response. XSH ERN 131 namespace for _POSIX_C_SOURCE Accept as marked below Some discussion had occurred on the reflector. It was agreed to run this down the interpretations track. Interpretation: ----------------- The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: ----------- We agreed that the standard can be read ambiguously and that the problems include the uses of the phrase "XSI extension" and the last clause of XSH 2.2.1.2 (Page 14 Line 551 2004 edition) "and in addition to enable the XSI extension", which can be interpreted as saying that XSH clause 2.2.1 thus excludes the XSI extension. It is agreed that the intent of the standard is clear and supported by the informative text (non-normative). The intent of the standard is that the XSI text is a POSIX option, as confirmed by the original scope and rationale for XBD section 2. XBD sections 2.1.3.1 and 2.1.3.2 also state that POSIX conformance can include support of the XSI extension . So XSI extension should have been better stated as XSI option and the text in XSH 2.2.1.2 changed to make it clear that it ensures that the XSI option is enabled if not already. Notes to the Editor for a future revision (not part of this interpretation): --------------------------------------------------------------------------- The standard developers note that a future revision will consider the status of all options, and thus should consider whether the separate _XOPEN_SOURCE feature test macro is needed (that is in the scope of the revision). One global change required with the current text is to change uses of "XSI extension" to "XSI option". If the text regarding _XOPEN_SOURCE is kept then the last clause of XSH 2.2.1.2 Page 14 line 551 should change Either delete the last part of the sentence: "and in addition to enable the XSI extension" or Change from: This is needed to enable the functionality described in Section 2.2.1.1 and in addition to enable the XSI extension. To: This is needed to enable the functionality described in Section 2.2.1.1 and to ensure the XSI option is enabled. XSH ERN 132 %M for fscanf OPEN This is invention, but arises from the LSB conflicts. Leave open, need to work on the wording, including fwscanf specifics before we can move forward Action 2006-06-01: Andrew to work out the full set of changes for recirculation for XSH ERN 132 OPEN XSH ERN 133 open and implementation added flags OPEN Left open since we need specific wording XSH ERN 135 pthread_mutexattr_getprotocol OPEN Need to forward to the SSWG-RT (action completed) Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next call will be 22 June irc://irc.freestandards.org/austin ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic