PASC PMC Procedures
                  Appendix A - PAR Review Criteria
                      Approved July 12, 1994
		     (Revised July 18,  1996)

PASC SEC procedures require that each PAR submitted for sponsorship must
have attached to it a list of responses to these criteria.  PARs which a
submitter believes are exempt from certain criteria should state the
reasons for such an exemption during the PAR submission process.  If such
an exemption requests that a PAR be approved when there is not an existing
body of work, the submitter must indicate why preliminary work should not
be done in another forum first and then moved into a PASC sponsored work
group.

Projects handled by PASC fall roughly into eight classes: base API
standards, profiles, test method specifications, language bindings to base
APIs (including LIS developed after a language-specific API), technical
corrigenda, revisions of approved standards, guides, and recommended
practice specifications.  The criteria apply to these classes to varying
degrees as described below.  The last three document types are actually
orthogonal attributes (e.g., one might have a test method specification
which was a recommended practice rather than a standard); in this case,
the weaker requirement for each of the criteria would apply.

In the following tables, a "Y" indicates that the criterion applies; "N/A"
indicates that the criterion does not apply; "Y*" indicates that
evaluation of this criterion involves a judgement call.  Each of the
specification types may be accompanied by additional text which better
defines the meaning of the criterion in that context.

1.	INDUSTRY EXPERIENCE

There must be widespread existing industry experience (User, Producer and
General Interest) which represents a substantive portion of the scope of
the PAR.

Base Standards	Y
Profiles	Y - look for experience with using the various pieces that
		    make up the profile and with building systems which
		    provide some of the relevant features (e.g. for a
		    real-time profile, there should be industry experience
		    with systems which support dot1-like and dot4-like
		    functionality simultaneously)
Test Methods	Y - must be widespread industry experience which represents
		    testing the capabilities underlying the standard to
		    which the methods will be applied.
Lang. Bindings	Y - exactly as if you had proposed a new base standard in
		    the same area in the chosen language
Corrigenda	N/A
Revisions	Y - for any new content
Guides		Y
Rec. Practice	Y

2.	BASE DOCUMENT

There must be a base document with community support from which the work
can be started. If there are several documents, then there must be evidence
of the willingness of the affected parties to work together to generate a
single standard. Any such document must be for use free of encumbrances.

Base Standards	Y - each separable component mentioned in the scope must
		    have an identified base document
Profiles	Y - it could be as simple as RFP's, statements of
		    prerequistes extracted from other documents, etc.
Test Methods	Y - however, not required if developed using IEEE 2003
Lang. Bindings	Y* - At most, base docs must exist to cover the scope of
		    the binding PAR (which may be a subset of the base doc
		    PAR); however, there need not be complete coverage of
		    even the scope of the binding PAR. There should
		    *enough*, though, to assure limited invention by
		    committee.
Corrigenda	N/A - however, the PAR must identify the defect(s) to be
		    corrected
Revisions	Y - for new content identified in the PAR scope
Guides		Y - however, an unencumbered base document is not required;
		    also, guides may have multiple base docs that overlap.
Rec. Practice	Y

3.	REALISTIC SCOPE AND TIMELINE

The scope of work must specify a realistic set of objectives, attainable
by the specified completion date. Note that the completion date must be
within a window which allows the produced standard to be accepted and useful.

Such objectives should include:
	- Document outline
	- First Draft
	- First Ballot

Base Standards	Y - minimum three years
Profiles	Y - minimum two years
Test Methods	Y - minimum three years
Lang. Bindings	Y - minimum two years
Corrigenda	Y - could be very fast; possibly as little as six months
Revisions	Y - minimum three years
Guides		Y - minimum two years
Rec. Practice	Y - minimum two years

4.	APPROPRIATENESS AND INDUSTRY ACCEPTANCE

Is there evidence that developers of portable applications will use the
results of the work? Not just "is it within PASC scope" but "does this bring
sufficient value to the industry" or "does it sufficiently further the
interests of the industry"?

Base Standards	Y*
Profiles	Y*
Test Methods	Y*
Lang. Bindings	Y*
Corrigenda	N/A
Revisions	Y* - This is critical; the alternatives (simple
		     reaffirmation or withdrawal) must be considered
Guides		Y*
Rec. Practice	Y*

5.	COORDINATION PLAN

For PARs affecting approved standards, a plan for coordination and integ-
ration of the work must be established. Extensions or modifications to
approved standards should only be made after careful consideration of the
impact on the community which relies on these stable, approved standards.
PARs which propose extensions or modifications must indicate the other PASC
standards work which they will affect.

Base Standards	Y
Profiles	Y
Test Methods	Y
Lang. Bindings	Y
Corrigenda	Y
Revisions	Y
Guides		Y
Rec. Practice	Y

6.	COMMUNITY COMMITMENT

Submitters of a PAR must exhibit the community's commitment to participate in
the work. These participants must include a Chair and Technical Editor, as
well as a sufficient number of technical experts representing a reasonable
balance of viewpoints, and the participants must be willing to support the
secretarial function. Committed participants should have expertise in the
subject matter or should be able to draw upon resource with that expertise.

Base Standards	Y
Profiles	Y
Test Methods	Y
Lang. Bindings	Y
Corrigenda	Y* - This might be a minimum of one person
Revisions	Y
Guides		Y
Rec. Practice	Y

7.	WITHIN PASC SCOPE

The PAR's proposed scope of work must be within the scope of PASC activities.

Base Standards	Y
Profiles	Y
Test Methods	Y
Lang. Bindings	Y
Corrigenda	Y
Revisions	Y
Guides		Y
Rec. Practice	Y

8.	REASONABLE RESOURCE IMPACT

The time frame for the work specified in the PAR must be appropriate given
the impact it will have on PASC resources (e.g. core personnel from other
active PASC work groups, meeting space, etc.)

Base Standards	Y
Profiles	Y
Test Methods	Y
Lang. Bindings	Y
Corrigenda	N/A - there may be circumstances where, regardless of the
		    pain required, we have to do the work
Revisions	Y
Guides		Y
Rec. Practice	Y

9.	TEST PLAN

The submitter must provide a Test Plan.

Base Standards	Y
Profiles	Y
Test Methods	N/A
Lang. Bindings	Y
Corrigenda	Y
Revisions	Y
Guides		N/A
Rec. Practice	Y