X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=blobdiff_plain;f=doc%2Fhtml%2Ftep1.html;h=9b0d882c9ce7a358787eab181a14b52a3d2e0102;hb=b1b9366c5a59ead38e3c1a0e765a7eb93120df59;hp=b517558810c74fbcc935b818fe42c92fda9646c1;hpb=e3c0b957baa23adb432835a3ca5f4e805a649b0d;p=tinyos-2.x.git diff --git a/doc/html/tep1.html b/doc/html/tep1.html index b5175588..9b0d882c 100644 --- a/doc/html/tep1.html +++ b/doc/html/tep1.html @@ -41,11 +41,6 @@ blockquote.epigraph { dd { margin-bottom: 0.5em } -/* Uncomment (& remove this text!) to get bold-faced definition list terms -dt { - font-weight: bold } -*/ - div.abstract { margin: 2em 5em } @@ -296,19 +291,11 @@ ul.auto-toc { Type:Best Current Practice Status: -Draft +Final TinyOS-Version:All Author: Philip Levis -Draft-Created:18-Oct-2004 - -Draft-Version:1.2 - -Draft-Modified:2006-07-12 - -Draft-Discuss:TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu> -
@@ -338,7 +325,9 @@ describes and follows both.

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in TEP 1.

Note that the force of these words is modified by the requirement -level of the document in which they are used.

+level of the document in which they are used. These words hold their +special meanings only when capitalized, and documents SHOULD avoid using +these words uncapitalized in order to minimize confusion.

2.1 MUST

MUST: This word, or the terms "REQUIRED" or "SHALL", mean that the @@ -394,26 +383,27 @@ interoperability.

TEPs have two major parts, a header and a body. The header states document metadata, for management and status. The body contains the content of the proposal.

-

All TEPs MUST follow the TEP docutils template, and conform to -reStructuredText standards [1], to enable translation from -reStructuredText to HTML and Latex.

+

All TEPs MUST conform to reStructuredText standards [1] and follow +the docutils template, to enable translation from reStructuredText +to HTML and LaTeX.

3.1 TEP Header

The TEP header has several fields which MUST be included, as well as -others which MAY be included. The first six header fields MUST be +others which MAY be included. The TEP header MUST NOT include headers +which are not specified in TEP 1 or supplementary Best Current +Practice TEPs. The first six header fields MUST be included in all TEPs, in the order stated here.

The first field is "TEP," and specifies the TEP number of the document. A TEP's number is unique.. This document is TEP 1. The -TEP type (discussed below) -determines how a number is assigned to it. Generally, when a document -is ready to be a TEP, it is assigned the smallest available number. -BCP TEPs start at 1 and all other TEPs (Documentary, Experimental, -and Informational) start at 101.

+TEP type (discussed below) determines TEP number assignment. Generally, +when a document is ready to be a TEP, it is assigned the smallest +available number. BCP TEPs start at 1 and all other TEPs +(Documentary, Experimental, and Informational) start at 101.

The second field states the name of the working group that produced the document. This document was produced by the Core Working Group.

The third field is "Type," and specifies the type of TEP the document is. There are four types of TEP: Best Current Practice (BCP), -Documentary, Informational, and Experimental. This document is Best +Documentary, Informational, and Experimental. This document's type is Best Current Practice.

Best Current Practice is the closest thing TEPs have to a standard: it represents conclusions from significant experience and work by its @@ -434,18 +424,36 @@ become part of it. Unlike Documentary TEPs, Experimental TEPs may describe systems that do not have a reference implementation.

The fourth field is "Status," which specifies the status of the TEP. A TEP status can either be "Draft," which means it is a work in -progress, "Final," which means it is complete and will not change, or -"Obsolete," which means it should no longer be considered. If a TEP is -"Obsolete" because it has been replaced by another TEP, then the new -TEP number should follow "Obsolete," such as "Obsolete by TEP 1231."

+progress, "Final," which means it is complete and will not change. +Once a TEP has the status "Final," the only change allowed is the +addition of an "Obsoleted By" field.

+

The "Obsoletes" field is a backward pointer to an earlier TEP which +the current TEP renders obsolete. An Obsoletes field MAY have multiple +TEPs listed. For example, if TEP 191 were to replace TEPs 111 and 116, it +would have the field "Obsoletes: 111, 116".

+

The "Obsoleted By" field is added to a Final TEP when another TEP has +rendered it obsolete. The field contains the number of the obsoleting +TEP. For example, if TEP 111 were obsoleted by TEP 191, it would have +the field "Obsoleted By: 191".

+

"Obsoletes" and "Obsoleted By" fields MUST agree. For a TEP to list another +TEP in its Obsoletes field, then that TEP MUST list it in the Obsoleted By +field.

+

The obsoletion fields are used to keep track of evolutions and modifications +of a single abstraction. They are not intended to force a single approach or +mechanism over alternative possibilities.

If a TEP is Best Current Practices or Documentary, then it MUST include an additional field, "TinyOS-Version:," which states what version(s) of TinyOS the document pertains to. This document pertains to all versions of TinyOS, until made obsolete by a future TEP. This field MUST appear after the Status field and before the Author field.

-

The final required field is Author, which states the names of the +

The final required field is "Author," which states the names of the authors of the document. Full contact information should not be listed here (see Section 3.2).

+

There is an optional field, "Extends." The "Extends" field refers to +another TEP. The purpose of this field is to denote when a TEP represents +an addition to an existing TEP. Meeting the requirements of a TEP with an +Extends field requires also meeting the requirements of all TEPs listed +in the Extends field.

If a TEP is a Draft, then four additional fields MUST be included: Draft-Created, Draft-Modified, Draft-Version, and Draft-Discuss. Draft-Created states the date the document was created, Draft-Modified @@ -466,12 +474,17 @@ seeks to solve and providing needed background information.

If a TEP is Documentary, it MUST have a section entitled "Implementation," which instructs the reader how to obtain the implementation documented.

-

If a TEP is Best Current Practices, it MUST have a section entitled +

If a TEP is Best Current Practice, it MUST have a section entitled "Reference," which points the reader to one or more reference uses of the practices.

-

The last section of a TEP (but before citations, if there are any), -entitled "Author's Address" or "Author's Addresses" MUST contain -detailed author contact information.

+

The last three sections of a TEP are author information, citations, +and appendices. A TEP MUST have an author information section titled +entitled "Author's Address" or "Authors' Addresses." A TEP MAY have +a citation section entitled "Citations." A citations section MUST +immediately follow the author information section. A TEP MAY have +appendices. Appendices MUST immediately follow the citations section, +or if there is no citations section, the author information section. +Appendices are lettered. Please refer to Appendix A for details.

@@ -487,13 +500,13 @@ definitions taken from IETF RFC 2119.

6. Author's Address

Philip Levis
-
467 Soda Hall
-
UC Berkeley
-
Berkeley, CA 94720
+
358 Gates Hall
+
Stanford University
+
Stanford, CA 94305

-
phone - +1 510 290 5283
+
phone - +1 650 725 9046

- +
@@ -505,6 +518,10 @@ definitions taken from IETF RFC 2119.

+
+

Appendix A. Example Appendix

+

This is an example appendix. Appendices begin with the letter A.

+