summaryrefslogtreecommitdiff
path: root/oap-0001
diff options
context:
space:
mode:
Diffstat (limited to 'oap-0001')
-rw-r--r--oap-0001108
1 files changed, 0 insertions, 108 deletions
diff --git a/oap-0001 b/oap-0001
deleted file mode 100644
index 5848abb..0000000
--- a/oap-0001
+++ /dev/null
@@ -1,108 +0,0 @@
-OSMORA Standards Group I. M. Moffett, Ed.
- OSMORA
- 2 March 2025
-
-
- OSMORA Amelioration Proposals
- OAP-0001
-
-Abstract
-
- Description of OSMORA Amelioration Proposals
-
-Table of Contents
-
- 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1
- 1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 1
- 1.2. Audience . . . . . . . . . . . . . . . . . . . . . . . . 1
- 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
- 3. Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 2
- 4. Normative References . . . . . . . . . . . . . . . . . . . . 2
- Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 2
-
-1. Introduction
-
- OSMORA Amelioration Proposals (OAPs) are structured documents that
- serve to drive changes imposed by OSMORA by describing their
- fundamentals while allowing others to amend/revise them.
-
-1.1. Purpose
-
- The goal of having OAPs is to provide an organized means of proposing
- and improving ideas that contribute to the betterment of society and
- technology. These proposals can range from technical improvements to
- societal reforms, and they are open to discussion and collaboration
- for those who have understood and commited to the OSMORA oath.
-
-1.2. Audience
-
- OAPs are intended for those who are commited to the OSMORA oath.
- These proposals must only be considered offical and bidning when they
- are approved by a number of OSMORA members and a single OSR (OSMORA
- Standards Reviewer).
-
-
-
-
-
-
-
-
-
-Moffett Informational [Page 1]
-
- OAPs March 2025
-
-
-2. Requirements Language
-
- The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
- "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
- "OPTIONAL" in this document are to be interpreted as described in
- BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
- capitals, as shown here.
-
-3. Structure
-
- An OAP will typically include the following:
-
- * OAP ID: Incremental document identifier.
-
- * Abstract: A concise summary of the proposal's intent and impact.
-
- * Motivation: Why this proposal matters and the problem it
- addresses.
-
- OSMORA:
- See OSMORA.ORG
-
- OSMORA Oath:
- A pledge taken by all members of OSMORA ensuring their commitment
- to societal betterment, technological advancement as well as their
- loyalty to the grater good, resisting the forbidden fruit dangled
- by the suits.
-
-4. Normative References
-
- [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
- Requirement Levels", BCP 14, RFC 2119,
- DOI 10.17487/RFC2119, March 1997,
- <https://www.rfc-editor.org/rfc/rfc2119>.
-
- [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
- 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
- May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
-
-Author's Address
-
- Ian M. Moffett (editor)
- OSMORA
- Washington, DC
- Email: ian@osmora.org
-
-
-
-
-
-
-Moffett Informational [Page 2]