Austin/15

Joint Meeting Agenda
2-4 March 1999
Menlo Park, California, USA

The second meeting of the Austin Group is occuring on March 2nd through
March 4th in Menlo Park California. The meeting is being hosted by Sun
Microsystems and The Open Group.

A file of logistics and hotel information is available at
http://www.opengroup.org/austin/logistics.html .

Meeting Goals

The goal of this meeting is to produce enough editing instructions for the
production of draft one of the Common Specifications. It is anticipated that
draft one will be available in June 1999, so that a review can take place
during the latter part of June, and issue resolution to occur at the July
1999 meeting to be held in Montreal, Canada.

Meeting Preparation

Please bring with you paper copies of the base documents for use as
reference material at the meeting. Some of the materials will also be
available in electronic form on a reference CD-ROM. Please familiarise
yourself with the documents produced from Austin-1, these documents are
available in the online document register.

Meeting Format

The meeting will consist of a plenary and breakout sessions. Three breakout
groups will consider the contents of particular volumes, produce a proposed
structure plan and then bring that back to the plenary for discussion.

Meeting times

It is anticipated that the meeting will run from 9am until 5pm each day

Tuesday March 2nd 9am -> 5pm (*)
Wednesday March 3rd 9am -> 5pm (**)
Thursday March 4th 9am -> 5pm

(*) Note: On Tuesday evening a group of us will go to the Linux World
Conference in San Jose to catch the keynote from Linus Torvalds (at 6:30pm).

(**) Note: On Wednesday morning, breakout groups will be meeting and the
group will not meet in plenary until 11:30am. This also allows some of us to
attend a session (on the Linux Standard Base) at the Linux conference on the
wednesday morning (9:00-10:15).

----------------------------------------------------------------------------

Agenda Items

  1. Administrivia
        o Introductions
        o Approval of Agenda
        o Approval of Minutes
        o Review of Action Items
  2. Procedures - the purpose here is not to debate the procedures but to
     inform.
  3. Identification of Organizational Reps and election of the Chair
  4. Status Reports
        o POSIX Status
        o IEEE/TOG Status
        o Joint Procedures Committee Status
  5. Old business
        o How do we handle the duplicate interface definitions between ISO C
          and the Single UNIX Specification (see email seq 44, 46, 47); for
          a view of the scope of the issue look at the fseek() specification
          in ISO C, POSIX and SUS.
  6. New business
        o 6.1 What if .2b fails ?
        o 6.2 What about projects that fail at 12/31 ? 98-01-04
        o 6.3 Cross book references - is it important to have the ability to
          revise each book independently - if so we need to structure the
          doc accordingly - this is a question we need to consider ?
        o Namespace reservation - can we reserve namespace for anticipated
          future standards such as .21
  7. Break-out groups.
        o Working meeting to break out into 3 or 4 subgroups (one for each
          volume, [4 if we include the rationale]) and produce a document
          contents and structure plan for that volume.
  8. Discussion and approval of structure plans for each volume.
  9. Consideration of what can be merged into D1 (i.e. what is ready today)
        o .1a D16 , very few funcs not already in Single UNIX , so this will
          require a technical parse for differences
        o 2b - a lot of material, symlinks, vi/ex, pax
        o from existing .1 and .2 :
             + Portability considerations
             + Any normative parts of POSIX not covered in the Base specs.
        o Parse thru for Terminology changes
        o Interpretations /corrigenda - straightforward for TOG corrigenda/
          resolutions, but will require more work for PASC interpretations.
        o Removal of obsolescense / legacy
        o Identification of alternative behaviors in the specification and
          consideration for whether one can now be mandated (instead of the
          either or )
        o Integration of .13 feature groups.
        o What about POSIX version, and version identifiers for the symbolic
          constants in 2-10
 10. Consent list
 11. Issues list
 12. Action Item Review
 13. Meeting Schedule
 14. AOB


-----
Andrew Josey                                The Open Group
Base WG Chair                               Apex Plaza,Forbury Road,
Email: a.josey@opengroup.org                Reading,Berks.RG1 1AX,England
Tel:   +44 118 9508311 ext 2250             Fax: +44 118 9500110