-
Notifications
You must be signed in to change notification settings - Fork 1
/
guidelines.html
47 lines (45 loc) · 2.14 KB
/
guidelines.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Mozilla/4.5 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) [Netscape]">
</head>
<body text="#000000" bgcolor="#FFFFFF" link="#0000FF" vlink="#FF0000" alink="#000088">
<h1>
Spec Guidelines</h1>
The following is a definition of what constitutes a stable standard. This
should be applied to both what we produce, and what we reference by our
standard. This is a guideine and does not prevent the LSB from making
exceptions as needed.
<h3>
Published Specification</h3>
A standard should be published for public use. The standard may be published
at a well know location on the web, preferably under the web site of a
formal organization (as is described later). Publication under someone's
personal web space is discouraged as doing so does not present an image
of permanence.
<h3>
Versioned Specification</h3>
A specification should be adequately versioned. All specifications
should have achieved a 1.0 status. Proper versioning implies that the specification
is developed with
<br>enough controls to ensure stability. The specification should not be
versioned rapidly. A high rate of change does not imply a stable specification.
<h3>
Complete Specification</h3>
The specification should be complete in that is covers all interfaces that
are part of the command or API. The specification should explicitly define
the behavior of all interfaces. The specification should be written in
a manner that is conducive to extracting a set of assertions from which
a test suite can be developed. The specification should be complete enough to
allow a compatible implementation to be independently developed.
<h3>
Specification Committee</h3>
The specification should be developed by a committee or group. The committee
or group should include representatives from multiple vendors or organization.
The group should be open to new membership.
The group should have well defined processes making progress and resolving
issues. The group should have a roadmap defined for the specification.
<br>
</body>
</html>