Over the lifetime of WG15 it has seen fit to produce a number of Resolutions intended to guide the future work and philosophy of the group.  These 'unlimited' Resolutions are reproduced below:
 

Orcas 90-93. Distribution of WG15 Correspondence:

Whereas, it is important that there be an historical record of the activities of WG15; and

The official correspondence constitutes an important part of that history; and

It is important for WG15 to have access to that correspondence as part of its deliberations;

Therefore, all official WG15 correspondence should:

1. be assigned WG15 document numbers
2. be distributed to WG15 member bodies

 
Note: Only actual correspondence, not attachments, need to be covered in this resolution since it is assumed that the attachments already have been assigned WG15 document numbers.

Rotterdam 91-114 Letter Ballots

Rotterdam 91-151 Meeting Locations

Whereas sufficient continuity of participation of active technical experts is critical to progress of the ISO/IEC JTC1/SC22/WG15 programme of work, and

Whereas there has been considerable discussion within ISO/IEC JTC1/SC22/WG15 regarding the location of ISO/IEC JTC1/SC22/WG15 meetings,

Therefore ISO/IEC JTC1/SC22/WG15 establishes the following guidelines, in addition to the ISO/IEC JTC1 Directive 1990, for selection of meeting sites.
 

1. ISO/IEC JTC1/SC22/WG15 meetings normally should be held in countries which actively participate in the work of ISO/IEC JTC1/SC22/WG15.
2. Consideration normally should not be given to conducting an ISO/IEC JTC1/SC22/WG15 meeting in a country that is not a member of JTC1 as an "O" or "P" member. (Reference ISO/IEC JTC1 Directive 1990 3.5.3.2 P.17)

Rotterdam 91-158 Management of WG15 meetings

Whereas there is a rapid increase in the number of ISO/IEC JTC1/SC22/WG15 work items, and

Whereas the number of issues associated with these work items is also increasing rapidly, and

Whereas it may be required that ISO/IEC JTC1/SC22/WG15 meetings be divided into small groups for some significant portion of the meeting,

Therefore ISO/IEC JTC1/SC22/WG15 reiterates the following operating procedure:
 

1. Advance Notice of Meeting (including information regarding small groups) shall be distributed to Member Bodies in accordance with then current ISO/IEC JTC1 directives.
2. The Draft Meeting Agenda shall include small group agendas if small group meetings will be held.
3. All documents to be used at a ISO/IEC JTC1/SC22/WG15 meeting shall be distributed to Member Bodies in accordance with then current ISO/IEC JTC1 Directives.

Stockholm 91-175. ISO/IEC JTC1/SC22/WG15 and IEEE POSIX Meetings

Whereas the workload associated with the development of international standards has significantly increased with a corresponding increase in the need for cooperation and clear communications between the members of ISO/IEC JTC1/SC22/WG15 and the community of POSIX technical experts,

Therefore, ISO/IEC JTC1/SC22/WG15 plans to schedule at least one ISO/IEC JTC1/SC22/WG15 meeting a year in conjunction with a scheduled IEEE POSIX meeting.

Hamilton 92-184. GENERATION OF ACTION ITEMS

SC22/WG15 adopts the following operating rule:
All actions arising from a SC22/WG15 Resolution shall be included in the Action Item list for the meeting at which the Resolution is passed. The action item shall include a pointer to the corresponding Resolution. Note: As a result, document N202 will not need to be maintained.

Hamilton 92-189. ISSUES LIST

WG15 adopts N252 as the modus operandi for the Issues List

Reading 92-220 Liaison Reports

Whereas Liaison Reports are official communications between SC22/WG15 and other standards authorities, and

Whereas Liaison Reports represent official SC22/WG15 statements,

Therefore, all SC22/WG15 Liaisons are instructed to submit their Liaison Reports to SC22/WG15 to obtain a SC22/WG15 document number, before the Liaison Reports are submitted to the groups with which they are approved to liaise.

Heidelberg 93-233 Requirements on Specification Methods

SC22/WG15 reaffirms the following requirements relating to the choice of specification methods for projects JTC1.22.21, JTC1.22.39, and JTC1.22.42:

1. To provide a clear and authoritative functional specification for POSIX services, and
2. To provide coordination and consistency between multiple language bindings to the same services, and reaffirms the following related objectives:
3. To support easier and faster development of language bindings,
4. To support the development of language bindings that are appropriate for each programming language,
5. To support the development of language bindings by independent Standard Development Organizations, and
6. To support the development of POSIX standards in a timely and efficient manner.

Heidelberg 93-234 PASC Information

Whereas SC22/WG15 has a requirement to develop both language Independent Specifications (LIS) and Language Dependent Specifications (LDS), and

Whereas SC22/WG15 recognizes that, due to resource constraints, the current approach to the development of PASC LIS standards is having a severe negative impact on the ability of the US member body to develop and forward LDS standards in a timely manner, and that this has an equal effect on the work of SC22/WG15, and

Whereas SC22/WG15 notes that the current US development group may discontinue the current requirement for the parallel development of LIS and LDS, for the reasons given above, and

Whereas SC22/WG15 recognizes that the current work in the area of LIS is not yet mature, and is the subject of work in other groups, such as WG11, and

Whereas SC22/WG15 recognizes that the requirement that LIS was intended to satisfy may be met in other ways, and

Whereas SC22/WG15 wishes to ensure that both LIS and LDS are brought forward into the international arena in as
timely a manner as possible,

Therefore SC22/WG15 resolves:
 

1. To investigate the most appropriate means of satisfying the requirements and objectives contained in Resolution 93-233, for which the current LIS methods were originally formulated, taking account of the work of other groups, such as WG11.
2. That it will accept LDS documents for progression to DIS, without an accompanying LIS, on an individual basis where Member Bodies support the action, until such time as it determines the precise form in which the requirements and objectives, for which LIS was originally formulated, are to be met.
3. To request the US to preserve and progress in a timely manner the LIS work that is currently underway, taking fully into account the requirements and objectives set out in SC22/WG15 Resolution 93-233, and to ensure that US standards developed for progression within SC22/WG15 satisfy those requirements and objectives.

Heidelberg 93-242 Delegate Notification

SC22/WG15 requests member bodies to provide the names of delegates who will attend each SC22/WG15 meeting and any Rapporteur group meetings, in writing to the convener of the meeting in accordance to the JTC1 Directives.

Annapolis 93-246 Ad-Hoc to Provide Agenda and Document Assignment

WG15 establishes an Ad-Hoc group on meeting agenda and document assignment. WG15 establishes the following instructions for that Ad-Hoc:
 
1. The WG15 Convener announces the meetings of this Ad-Hoc group
2. The Ad-Hoc group will meet before each WG15 meeting, preferably the day before the start of the WG15 meeting
3. The Ad-Hoc groups tasks include:
• reviewing the agenda
• assigning available documents to the appropriate agenda item
• providing an updated agenda with document numbers to the delegates before the start of the WG15 meeting
• ensuring availability of all documents listed on the updated agenda to the delegates before the start of the WG15 meeting
4. Invites the following to participate in the Ad-Hoc group meetings:
• Chair
• Convener
• Secretary
• representative of each WG15 member

Annapolis 93-257 Profiles to be developed by WG15

Whereas profiles, which reference POSIX standards, are under development within the US, and

Whereas it can be expected that these profiles soon will reach the state at which they can be registered as ISPs, and

Whereas the procedures adopted by the US and SC22/WG15 governing the development and adoption of POSIX Based standards (i.e., synchronization plan, WG15 N352) can apply to ISPs,

Therefore SC22/WG15 instructs its convener to:

• request SC22 to include the development of ISPs within the scope of SC22/WG15, and

Therefore

• SC22/WG15 notes that its NP proposals for ISPs will be developed and approved in close cooperation with SGFS and the regional workshops in areas of Profile Identifiers, scope of the profile and taxonomy issues, and
• SC22/WG15 notes that its ISPs will be consistent with TR10000, and
• SC22/WG15 recognizes that additional procedures within SC22 and SGFS may be necessary.

Annapolis 93-261 PASC Mailings

Whereas the PASC has offered to distribute drafts of PASC standards under development and working mailings from the PASC SEC and PMC groups to the SC22/WG15 HoDs, and

Whereas timely delivery of these documents is important to the progress of these standards once they reach WG15,

Therefore, SC22/WG15 requests the US member to send these documents:

1. By express delivery to those National Body designated recipients whose delegations attend SC22/WG15 meetings,
2. By regular delivery to those National Body designated recipients whose delegations are participating in SC22/WG15 meetings but do not regularly attend meetings and who have responded to the SC22/WG15 mailing address confirmation,
3. To drop those National Bodies of SC22/WG15 from the distribution list who have not responded to the SC22/WG15 mailing address confirmation. These are Austria, Belgium, Sweden, Russia.

Annapolis 93-264 Ballot Disposition of Comments

SC22/WG15 instructs its Project Editor to conduct editing meetings for the purpose of preparing proposed disposition of comments on SC22 or JTC1 Ballots. It is understood that this instruction includes calling meetings, in coordination with Rapportteur groups if appropriate, for ballot comment disposition and that SC22/WG15 retains approval authority for the disposition of comments.

(This is superceded by 94-294)

Vancouver 94-294 Conduct and Scheduling of SC22/WG15 Editing Meetings

Whereas
WG15 is aware of some concerns among its Member Bodies regarding the conduct and scheduling of its Editing Meetings,

Therefore
WG15 instructs its Project Editor as follows:

That meetings shall be announced and conducted in accordance with the JTC1 Directives. That at least 4 weeks notice shall be provided for calling editing meetings.

That meeting announcements shall be provided by electronic mail to the SC22/WG15 Email distribution list, and shall be provided by Fax to all Heads of Delegation who do not have recorded electronic mail addresses.

That meetings may be conducted via teleconference.

That all documents to be discussed at the editing meeting shall be made available to all participants at least 2 weeks before the meeting.

That the disposition of comments developed during editing meetings may be distributed via the SC22/WG15 Email distribution list and shall be provided to the SC22/WG15 convener within 2 weeks of the end of the meeting.

That SC22/WG15 retains approval authority for the disposition of comments developed during editing meetings, to be accomplished by either a 30-day SC22/WG15 Letter ballot or a SC22/WG15 Working Group meeting, unless otherwise authorized by a SC22/WG15 resolution

That in the disposition of comments report the participants in the editing meeting shall be identified, as well as the resulting position, if known, of National bodies who balloted negative.

That the Project Editor shall endeavor to ensure the widest possible participation in the editing meeting and shall take this into account when scheduling meetings.

Copenhagen 96-342 Decision Making by E-mail

Dallas 98-398 Meeting Schedule and Frequency

New Orleans 99-407 Voting Representatives

Whereas the rapporteur groups established in 99-406 are in fact joint working groups of The Open Group, IEEE PASC, and WG15, and whereas a voting procedure has been proposed whereby each of those organizations has a single vote in the case of non-consensus, therefore the lead rapporteur of each group has the responsibility of ensuring that WG15 has a voting representative present at every meeting.

Montreal 99-415 WG15 Vice Chair

Resolved that the JTC1/SC22/WG15 Convenor shall be the standing vice-chair of WG15.

Montreal 99-421 Project Editors Reports

Whereas JTC1/SC22/WG15 has a large number of documents assigned to a large group of editors, and
Whereas regular reports from these editors are essential to the conduct of business within JTC1/SC22/WG15,

Therefore, JTC1/SC22/WG15 respectfully requests that all project editors for work assigned to this working
group submit a written report on the work assigned to them thirty days before any formal plenary meeting of
JTC1/SC22/WG15.