summaryrefslogtreecommitdiff
path: root/oap-0001
blob: 5848abb11d64c2bd6c37449d378e6b8461dd3a3e (plain)
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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
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]