From: scipio <scipio>
Date: Wed, 11 Jul 2007 16:13:08 +0000 (+0000)
Subject: HTML
X-Git-Tag: release_tools_1_2_4_1~40
X-Git-Url: https://oss.titaniummirror.com/gitweb/?p=tinyos-2.x.git;a=commitdiff_plain;h=e3e9ee1a55db4ae12635fc7594e3e68087e750ce

HTML
---

diff --git a/doc/html/tep1.html b/doc/html/tep1.html
index 7bfe2069..8e9d2448 100644
--- a/doc/html/tep1.html
+++ b/doc/html/tep1.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
+<meta name="generator" content="Docutils 0.3.7: http://docutils.sourceforge.net/" />
 <title>TEP Structure and Keywords</title>
 <meta name="author" content="Philip Levis" />
 <style type="text/css">
@@ -296,19 +296,11 @@ ul.auto-toc {
 <tr class="field"><th class="docinfo-name">Type:</th><td class="field-body">Best Current Practice</td>
 </tr>
 <tr><th class="docinfo-name">Status:</th>
-<td>Draft</td></tr>
+<td>Final</td></tr>
 <tr class="field"><th class="docinfo-name">TinyOS-Version:</th><td class="field-body">All</td>
 </tr>
 <tr><th class="docinfo-name">Author:</th>
 <td>Philip Levis</td></tr>
-<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">18-Oct-2004</td>
-</tr>
-<tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.6</td>
-</tr>
-<tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-05-29</td>
-</tr>
-<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
-</tr>
 </tbody>
 </table>
 <div class="note">
@@ -317,14 +309,14 @@ ul.auto-toc {
 TinyOS Community, and requests discussion and suggestions for
 improvements.  Distribution of this memo is unlimited.</p>
 </div>
-<div class="section">
-<h1><a id="abstract" name="abstract">Abstract</a></h1>
+<div class="section" id="abstract">
+<h1><a name="abstract">Abstract</a></h1>
 <p>This memo describes the structure all TinyOS Extension Proposal (TEP)
 documents follow, and defines the meaning of several key words in
 those documents.</p>
 </div>
-<div class="section">
-<h1><a id="introduction" name="introduction">1. Introduction</a></h1>
+<div class="section" id="introduction">
+<h1><a name="introduction">1. Introduction</a></h1>
 <p>In order to simplify management, reading, and tracking development,
 all TinyOS Extension Proposals (TEPs) MUST have a particular
 structure. Additionally, to simplify development and improve
@@ -332,8 +324,8 @@ implementation interoperability, all TEPs MUST observe the meaning of
 several key words that specify levels of compliance. This document
 describes and follows both.</p>
 </div>
-<div class="section">
-<h1><a id="keywords" name="keywords">2. Keywords</a></h1>
+<div class="section" id="keywords">
+<h1><a name="keywords">2. Keywords</a></h1>
 <p>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
 &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this
 document are to be interpreted as described in TEP 1.</p>
@@ -341,33 +333,33 @@ document are to be interpreted as described in TEP 1.</p>
 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.</p>
-<div class="section">
-<h2><a id="must" name="must">2.1 MUST</a></h2>
+<div class="section" id="must">
+<h2><a name="must">2.1 MUST</a></h2>
 <p>MUST: This word, or the terms &quot;REQUIRED&quot; or &quot;SHALL&quot;, mean that the
 definition is an absolute requirement of the specification.</p>
 </div>
-<div class="section">
-<h2><a id="must-not" name="must-not">2.2 MUST NOT</a></h2>
+<div class="section" id="must-not">
+<h2><a name="must-not">2.2 MUST NOT</a></h2>
 <p>MUST NOT: This phrase, or the phrase &quot;SHALL NOT&quot;, mean that the
 definition is an absolute prohibition of the specification.</p>
 </div>
-<div class="section">
-<h2><a id="should" name="should">2.3 SHOULD</a></h2>
+<div class="section" id="should">
+<h2><a name="should">2.3 SHOULD</a></h2>
 <p>SHOULD: This word, or the adjective &quot;RECOMMENDED&quot;, mean that there
 may exist valid reasons in particular circumstances to ignore a
 particular item, but the full implications must be understood and
 carefully weighed before choosing a different course.</p>
 </div>
-<div class="section">
-<h2><a id="should-not" name="should-not">2.4 SHOULD NOT</a></h2>
+<div class="section" id="should-not">
+<h2><a name="should-not">2.4 SHOULD NOT</a></h2>
 <p>SHOULD NOT: This phrase, or the phrase &quot;NOT RECOMMENDED&quot; mean that
 there may exist valid reasons in particular circumstances when the
 particular behavior is acceptable or even useful, but the full
 implications should be understood and the case carefully weighed
 before implementing any behavior described with this label.</p>
 </div>
-<div class="section">
-<h2><a id="may" name="may">2.5 MAY</a></h2>
+<div class="section" id="may">
+<h2><a name="may">2.5 MAY</a></h2>
 <p>MAY: This word, or the adjective &quot;OPTIONAL&quot;, mean that an item is
 truly optional.  One implementer may choose to include the item
 because a particular application requires it or because the
@@ -380,8 +372,8 @@ does include a particular option MUST be prepared to interoperate with
 another implementation which does not include the option (except, of
 course, for the feature the option provides.)</p>
 </div>
-<div class="section">
-<h2><a id="guidance-in-the-use-of-these-imperatives" name="guidance-in-the-use-of-these-imperatives">2.6 Guidance in the use of these Imperatives</a></h2>
+<div class="section" id="guidance-in-the-use-of-these-imperatives">
+<h2><a name="guidance-in-the-use-of-these-imperatives">2.6 Guidance in the use of these Imperatives</a></h2>
 <p>Imperatives of the type defined in this memo must be used with care
 and sparingly.  In particular, they MUST only be used where it is
 actually required for interoperation or to limit behavior which has
@@ -391,23 +383,23 @@ on implementors where the method is not required for
 interoperability.</p>
 </div>
 </div>
-<div class="section">
-<h1><a id="tep-structure" name="tep-structure">3. TEP Structure</a></h1>
+<div class="section" id="tep-structure">
+<h1><a name="tep-structure">3. TEP Structure</a></h1>
 <p>TEPs have two major parts, a header and a body. The header states
-document metadata, for management and status. The body contains the
+document metadata, for management and status. The body contains the 
 content of the proposal.</p>
 <p>All TEPs MUST conform to reStructuredText standards <a class="footnote-reference" href="#id2" id="id1" name="id1">[1]</a> and follow
 the docutils template, to enable translation from  reStructuredText
 to HTML and LaTeX.</p>
-<div class="section">
-<h2><a id="tep-header" name="tep-header">3.1 TEP Header</a></h2>
+<div class="section" id="tep-header">
+<h2><a name="tep-header">3.1 TEP Header</a></h2>
 <p>The TEP header has several fields which MUST be included, as well as
 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.</p>
 <p>The first field is &quot;TEP,&quot; and specifies the TEP number of the
-document. A TEP's number is unique.. This document is TEP 1. The
+document. A TEP's number is unique.. This document is TEP 1. The 
 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
@@ -424,7 +416,7 @@ authors. Developers desiring to add code (or TEPs) to TinyOS SHOULD
 follow all current BCPs.</p>
 <p>Documentary TEPs describe a system or protocol that exists; a
 documentary TEP MUST reference an implementation that a reader can
-easily obtain.  Documentary TEPs simplify interoperability when
+easily obtain.  Documentary TEPs simplify interoperability when 
 needed, and document TinyOS service implementations.</p>
 <p>Informational TEPs provide information that is of interest to the
 community. Informational TEPs include data gathered on radio behavior,
@@ -433,11 +425,11 @@ organizational and logistic information,
 or experiences which could help the community achieve its goals.</p>
 <p>Experimental TEPs describe a completely experimental approach to a
 problem, which are outside the TinyOS core and will not necessarily
-become part of it.  Unlike Documentary TEPs, Experimental TEPs may
+become part of it.  Unlike Documentary TEPs, Experimental TEPs may 
 describe systems that do not have a reference implementation.</p>
 <p>The fourth field is &quot;Status,&quot; which specifies the status of the TEP.
 A TEP status can either be &quot;Draft,&quot; which means it is a work in
-progress, &quot;Final,&quot; which means it is complete and will not change.
+progress, &quot;Final,&quot; which means it is complete and will not change. 
 Once a TEP has the status &quot;Final,&quot; the only change allowed is the
 addition of an &quot;Obsoleted By&quot; field.</p>
 <p>The &quot;Obsoletes&quot; field is a backward pointer to an earlier TEP which
@@ -465,7 +457,7 @@ here (see Section 3.2).</p>
 <p>There is an optional field, &quot;Extends.&quot; The &quot;Extends&quot; 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
+Extends field requires also meeting the requirements of all TEPs listed 
 in the Extends field.</p>
 <p>If a TEP is a Draft, then four additional fields MUST be included:
 Draft-Created, Draft-Modified, Draft-Version, and Draft-Discuss.
@@ -476,8 +468,8 @@ made. Draft-Discuss specifies the email address of a mailing list
 where the draft is being discussed. Final and Obsolete TEPs MUST NOT
 have these fields, which are for Drafts only.</p>
 </div>
-<div class="section">
-<h2><a id="tep-body" name="tep-body">3.2 TEP Body</a></h2>
+<div class="section" id="tep-body">
+<h2><a name="tep-body">3.2 TEP Body</a></h2>
 <p>The first element of the TEP body MUST be the title of the document. A
 TEP SHOULD follow the title with an Abstract, which gives a brief
 overview of the content of the TEP. Longer TEPs MAY, after the
@@ -487,41 +479,43 @@ seeks to solve and providing needed background information.</p>
 <p>If a TEP is Documentary, it MUST have a section entitled
 &quot;Implementation,&quot; which instructs the reader how to obtain the
 implementation documented.</p>
-<p>If a TEP is Best Current Practic, it MUST have a section entitled
+<p>If a TEP is Best Current Practice, it MUST have a section entitled
 &quot;Reference,&quot; which points the reader to one or more reference uses of
 the practices.</p>
-<p>The last numbered section of a TEP (but before citations, if there are any),
-entitled &quot;Author's Address&quot; or &quot;Author's Addresses&quot; MUST contain
-detailed author contact information.</p>
-<p>A TEP MAY have appendices after its numbered sections. Unlike
-numbered sections, appendices are lettered. Please refer to Appendix
-A for details.</p>
+<p>The last three sections of a TEP are author information, citations,
+and appendices. A TEP MUST have an author information section titled
+entitled &quot;Author's Address&quot; or &quot;Authors' Addresses.&quot; A TEP MAY have
+a citation section entitled &quot;Citations.&quot; 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.</p>
 </div>
 </div>
-<div class="section">
-<h1><a id="reference" name="reference">4. Reference</a></h1>
+<div class="section" id="reference">
+<h1><a name="reference">4. Reference</a></h1>
 <p>The reference use of this document is TEP 1 (itself).</p>
 </div>
-<div class="section">
-<h1><a id="acknowledgments" name="acknowledgments">5. Acknowledgments</a></h1>
+<div class="section" id="acknowledgments">
+<h1><a name="acknowledgments">5. Acknowledgments</a></h1>
 <p>The definitions of the compliance terms are a direct copy of
 definitions taken from IETF RFC 2119.</p>
 </div>
-<div class="section">
-<h1><a id="author-s-address" name="author-s-address">6. Author's Address</a></h1>
+<div class="section" id="author-s-address">
+<h1><a name="author-s-address">6. Author's Address</a></h1>
 <div class="line-block">
 <div class="line">Philip Levis</div>
-<div class="line">467 Soda Hall</div>
-<div class="line">UC Berkeley</div>
-<div class="line">Berkeley, CA 94720</div>
+<div class="line">358 Gates Hall</div>
+<div class="line">Stanford University </div>
+<div class="line">Stanford, CA 94305</div>
 <div class="line"><br /></div>
-<div class="line">phone - +1 510 290 5283</div>
+<div class="line">phone - +1 650 725 9046</div>
 <div class="line"><br /></div>
-<div class="line">email - <a class="reference" href="mailto:pal&#64;cs.berkeley.edu">pal&#64;cs.berkeley.edu</a></div>
+<div class="line">email - <a class="reference" href="mailto:pal&#64;cs.stanford.edu">pal&#64;cs.stanford.edu</a></div>
 </div>
 </div>
-<div class="section">
-<h1><a id="citations" name="citations">7. Citations</a></h1>
+<div class="section" id="citations">
+<h1><a name="citations">7. Citations</a></h1>
 <table class="docutils footnote" frame="void" id="id2" rules="none">
 <colgroup><col class="label" /><col /></colgroup>
 <tbody valign="top">
@@ -529,8 +523,8 @@ definitions taken from IETF RFC 2119.</p>
 </tbody>
 </table>
 </div>
-<div class="section">
-<h1><a id="appendix-a-example-appendix" name="appendix-a-example-appendix">Appendix A. Example Appendix</a></h1>
+<div class="section" id="appendix-a-example-appendix">
+<h1><a name="appendix-a-example-appendix">Appendix A. Example Appendix</a></h1>
 <p>This is an example appendix. Appendices begin with the letter A.</p>
 </div>
 </div>
