ࡱ > U W T a jbjbA]A] b8 +? +? C $ T . . . P . / L T dG | \/ `/ v/ v/ v/ Q0 @ 1 d 1 4 F F F F F F F , I R 2L F )2 Q0 Q0 )2 )2 F 3 v/ v/ F 4 3 3 3 )2 ^ v/ v/ F 3 D ( , )2 F 3 3 UE F P/ b$ . 2 0 UF F G H dG kF : L 3 L , F 3 T $ x $ T x $ Technical Note Template Status of this RFC This RFC provides information to the NASA Earth Science community. This RFC does not specify an Earth Science Data Systems (ESDS) standard. Distribution of this memo is unlimited. Change Explanation This document is not a revision to an earlier version. Copyright Notice Copyright 2008 United States Government as represented by the Administrator of the National Aeronautics and Space Administration. No copyright is claimed in the United States under Title 17, U.S. Code. All Other Rights Reserved. Abstract This document provides a simplified template for Earth Science Data Systems Technical Notes. Introduction ESDS-RFC-003 Instructions to Authors [1] describes the required format and content of an RFC (Request for Comments). The Technical Note Template in Appendix A is a distillation of the information in ESDS-RFC-003 and provides a template meant to simplify the task of creating an RFC that is a Technical Note. Technical Note Structure A Technical Note can be structured in two ways: 1. It can be a standalone document, i.e. the content of the technical note is the material the authors wish to convey (for example, this document is self-contained it describes and contains a template), or 2. It can refer to a different document, i.e. the technical note is a "wrapper" for some externally available material (for example, a technical note can describe the benefit of using a standard that was created by a standards body rather than copying all the material into the technical note, the note refers to that material). The main difference between the two kinds is that what is labeled the "Body" in the template below either contains information or refers to it. In either case, the other sections of the technical note serve to provide unambiguous statements regarding the origin of the material, the copyright, the revision status, and most importantly, the motivation for the existence of the technical note itself. The importance of the Introduction is not to be understated. A good introduction provides readers (particularly reviewers) with a reason to read the rest of the material. Lessons Learned for Authors The purpose of the Introduction section is to clearly articulate why the rest of the material in the technical note is of importance to the readers and reviewers. RFCs that are submitted with weak introductory material are generally returned to the authors for more information. The introduction should be very clear in providing a rationale for the RFC, explaining why it is important. It should also clearly describe the applicability of the RFC (e.g. is it specific to a discipline, relevant to all of NASA, etc.) References [1] ESDS-RFC-003 - Instructions to RFC Authors Authors The members of the Earth Science Data Systems Standards Process GroupChair: Richard Ullman, NASA GSFC, richard.ullman@nasa.gov Appendix A Glossary RFC Request for Comments ESDS Earth Science Data Systems NASA National Aeronautics and Space Administration Appendix B Template The template starts on the next page. Everything that is to be filled in by the authors is contained in angle brackets < > and there is a short explanation of how to fill in each part.