cbdc:public:cbdc_omg:04_doc:12_summary:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cbdc:public:cbdc_omg:04_doc:12_summary:start [2022/05/16 19:23] terrance |
cbdc:public:cbdc_omg:04_doc:12_summary:start [2022/06/17 17:41] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 3.0 White Paper Analysis ====== | ====== 3.0 White Paper Analysis ====== | ||
| - | [[cbdc:public:cbdc_omg:start| OMG Responses to Federal Reserve Discussion Paper]] | + | [[cbdc:public:cbdc_omg:start| OMG's CBDC WG Responses to Federal Reserve Discussion Paper]] |
| |< 100% >| | |< 100% >| | ||
| | [[cbdc:public:cbdc_omg:04_doc:start| Return to the Main Document]] | <WRAP> | | [[cbdc:public:cbdc_omg:04_doc:start| Return to the Main Document]] | <WRAP> | ||
| <html><b> | <html><b> | ||
| - | <a href="mailto:[email protected]?Subject=OMG CBDC Response: | + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: |
| - | 2.0 Methodology | + | 3.0 White Paper Analysis |
| ">Provide Feedback</a></b> | ">Provide Feedback</a></b> | ||
| Line 11: | Line 11: | ||
| </WRAP> | | </WRAP> | | ||
| A breakdown of the **White Paper** discussion of a U.S. CBDC and the Desirements(( | A breakdown of the **White Paper** discussion of a U.S. CBDC and the Desirements(( | ||
| - | **Desirement** is a blended word combining the word **Desire** and **Requirement**. **Desirement** is something that is desired, but not absolutely required and is often used to caption the capabilities of a product or system before it has reached the formal requirements phase. | + | **Desirement** is a blended word combining the word **Desire** and **Requirement**. **Desirement** is something desired but not absolutely required and is often used to caption the capabilities of a product or system before it has reached the formal requirements phase. |
| Source: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:desirement | Desirement]] | Source: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:desirement | Desirement]] | ||
| - | )) for that effort. Each Desirement is identified as to the page it was found on, its classification as a Benefit, Policy, Risks, Design, and a brief actionable statement. | + | )) for that effort. Each Desirement is identified with the page number it is found on, its classification as a Benefit, Policy, Risks, Design, and a brief actionable statement. |
| ===== Executive Summary ===== | ===== Executive Summary ===== | ||
| Line 29: | Line 29: | ||
| : //This paper is the first step in a public discussion between the Federal Reserve and stakeholders | : //This paper is the first step in a public discussion between the Federal Reserve and stakeholders | ||
| - | about [[cbdc:public:cbdc_omg:8_append:20_glossary:cbdc| Central Bank Digital Currencies (CBDCs)]]. For the purpose of this paper, a CBDC is defined as | + | about [[cbdc:public:cbdc_omg:8_append:20_glossary:cbdc| Central Bank Digital Currencies (CBDCs)]]. For this paper, a CBDC is defined as |
| a digital liability of a central bank that is widely available to the general public. In this respect, it is | a digital liability of a central bank that is widely available to the general public. In this respect, it is | ||
| analogous to a digital form of paper money. The paper has been designed to foster a broad and | analogous to a digital form of paper money. The paper has been designed to foster a broad and | ||
| - | transparent public dialogue about CBDCs in general, and about the potential benefits and risks of | + | transparent public dialogue about CBDCs in general and about the potential benefits and risks of |
| a U.S. CBDC. The paper is not intended to advance any specific policy outcome, nor is it intended | a U.S. CBDC. The paper is not intended to advance any specific policy outcome, nor is it intended | ||
| to signal that the Federal Reserve will make any imminent decisions about the appropriateness of | to signal that the Federal Reserve will make any imminent decisions about the appropriateness of | ||
| Line 40: | Line 40: | ||
| [[cbdc:public:cbdc_omg:04_doc:12_summary:start| Return to Top]] | [[cbdc:public:cbdc_omg:04_doc:12_summary:start| Return to Top]] | ||
| - | In order to provide answers to the 22 questions requested by the Federal Reserve in the [[https://www.federalreserve.gov/publications/files/money-and-payments-20220120.pdf | White Paper]], it is important to summarize the rest of the content of the **White Paper** so as to help provide context for the questions in the White Paper and OMG's answers to these questions. The questions fall into two major categories: | + | In order to provide answers to the 22 questions requested by the Federal Reserve in the [[https://www.federalreserve.gov/publications/files/money-and-payments-20220120.pdf | White Paper]], it is important to summarize the rest of the content of the **White Paper** to help provide context for the questions in the White Paper and OMG's CBDC WG answers to these questions. The questions fall into two major categories: |
| * CBDC Benefits, Risks, and Policy Considerations | * CBDC Benefits, Risks, and Policy Considerations | ||
| * CBDC Design | * CBDC Design | ||
| - | In order for the [[cbdc:public:cbdc_omg:04_doc:04_intro:start#about_the_object_management_group| Object Management Group (OMG) ]] to prepare responses to the questions in the **White Paper**, the OMG has taken a traditional Systems Engineering approach to understanding the problem by dissecting it into smaller, more manageable pieces based on the stated objectives outlined in the **White Paper**. We noted four major objectives: | + | In order for the [[cbdc:public:cbdc_omg:04_doc:04_intro:start#about_the_object_management_group| Object Management Group's (OMG) ]] CBDC WG to prepare responses to the questions in the **White Paper**, the OMG's CBDC WG has taken a traditional Systems Engineering approach to understanding the problem by dissecting it into smaller, more manageable pieces based on the stated objectives outlined in the **White Paper**. We noted four major objectives: |
| - | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#benefits| Benefit Considerations ]] | + | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#benefit_considerations| Benefit Considerations ]] |
| * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#policy_considerations| Policy Considerations]] | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#policy_considerations| Policy Considerations]] | ||
| - | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#risks| Risk Considerations ]] | + | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#risk_considerations| Risk Considerations ]] |
| - | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#design| Design Considerations]] | + | * [[cbdc:public:cbdc_omg:04_doc:12_summary:start#design_considerations| Design Considerations]] |
| ==== Methodology ==== | ==== Methodology ==== | ||
| [[cbdc:public:cbdc_omg:04_doc:12_summary:start| Return to Top]] | [[cbdc:public:cbdc_omg:04_doc:12_summary:start| Return to Top]] | ||
| - | The **White Paper** was read linearly (i.e., from top to bottom) with each statement classified as describing or providing: Background, Benefits, Policy Considerations, Risks, or Design. The sentences were then copied into the appropriate table (e.g., Table {{ref>Benefits}}, Benefits) in this White Paper Overview. Statements in the **White Paper** that provided Background were not transcribed into any table. This does not mean these Background statements were unimportant; they were used to provide definitions and context for the Benefits, Policy Considerations, Risks, or Design statements captured in the tables below. | + | The **White Paper** was read linearly (i.e., from top to bottom) with each statement classified as describing or providing: Background, Benefits, Policy Considerations, Risks, or Design. The sentences were copied into the appropriate table (e.g., Table {{ref>Benefits}}, Benefits) in this White Paper Overview. Statements in the **White Paper** that provided Background were not transcribed into any table. This does not mean these Background statements were unimportant; they were used to provide definitions and context for the Benefits, Policy Considerations, Risks, or Design statements captured in the tables below. |
| - | : **Note:** Some of the statements have been edited to allow them to be standalone and written in the form of an "action". For future iterations, these statements need be written as requirements. See: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:1.4_req:00_aboutreq:07_reqspec | Specifying Requirements]] in the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra | Distributed Immutable Data Object - References Architecture (DIDO-RA)]]. | + | : **Note:** Some of the statements have been edited to allow them to be standalone and written in the form of an "action". For future iterations, these statements need to be written as requirements. See: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:1.4_req:00_aboutreq:07_reqspec | Specifying Requirements]] in the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra | Distributed Immutable Data Object - References Architecture (DIDO-RA)]]. |
| ==== Benefit Considerations ==== | ==== Benefit Considerations ==== | ||
| Line 66: | Line 66: | ||
| <caption>The Benefits identified in the **White Paper**</caption> | <caption>The Benefits identified in the **White Paper**</caption> | ||
| ^ Desirement No. ^ Page No. ^ Desirement(( | ^ Desirement No. ^ Page No. ^ Desirement(( | ||
| - | **Desirement** is a blended word combining the word **Desire** and **Requirement**. **Desirement** is something that is desired, but not absolutely required and is often used to caption the capabilities of a product or system before it has reached the formal requirements phase. | + | **Desirement** is a blended word combining the word **Desire** and **Requirement**. **Desirement** is something that is desired but not absolutely required and is often used to caption the capabilities of a product or system before it has reached the formal requirements phase. |
| Source: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:desirement | Desirement]] | Source: [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:desirement | Desirement]] | ||
| )) ^ | )) ^ | ||
cbdc/public/cbdc_omg/04_doc/12_summary/start.1652743390.txt.gz · Last modified: 2022/05/16 19:23 by terrance
