User Tools

Site Tools


cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q22:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q22:start [2022/05/17 18:40]
nick
cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q22:start [2022/06/17 19:33] (current)
terrance
Line 3: Line 3:
 | [[cbdc:​public:​cbdc_omg:​04_doc:​20_comments:​dsn:​start| Return to Design Considerations ]]  |  <​WRAP>​ | [[cbdc:​public:​cbdc_omg:​04_doc:​20_comments:​dsn:​start| Return to Design Considerations ]]  |  <​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: ​
 Question: 22. Are there additional design principles that should be considered? Are there tradeoffs around any of the identified design principles, especially in trying to achieve the potential benefits of a CBDC? Question: 22. Are there additional design principles that should be considered? Are there tradeoffs around any of the identified design principles, especially in trying to achieve the potential benefits of a CBDC?
 ">​Provide Feedback</​a></​b>​ ">​Provide Feedback</​a></​b>​
Line 71: Line 71:
 [[cbdc:​public:​cbdc_omg:​04_doc:​20_comments:​dsn:​q22:​start| Return to Top]] [[cbdc:​public:​cbdc_omg:​04_doc:​20_comments:​dsn:​q22:​start| Return to Top]]
  
-Some of these **Non-Functional** requirements were alluded to in the White Paper, but not directly specified or defined. Table {{ref>​xreftable}} provides an example of cross-referencing the Non-Functional Requirements to the Benefits, Policy Considerations,​ Risks and Design requirements identified in the [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] done by the [[https://​www.omg.org/​ | Object Management Group ]]. +Some of these **Non-Functional** requirements were alluded to in the White Paper, but not directly specified or defined. Table {{ref>​xreftable}} provides an example of cross-referencing the Non-Functional Requirements to the Benefits, Policy Considerations,​ Risks and Design requirements identified in the [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] done by the [[https://​www.omg.org/​ | Object Management Group'​s ​]] CBDC WG
  
 <table xreftable>​ <table xreftable>​
-<​caption>​Example of mapping a subset of requirements identified during the White Paper Analysis conducted by the OMG.</​caption>​+<​caption>​Example of mapping a subset of requirements identified during the White Paper Analysis conducted by the OMG's CBDC WG.</​caption>​
 ^ Non-Functional Requirement ​ ^ Benefits, Policy Considerations,​ Risks and Design requirements ​ | ^ Non-Functional Requirement ​ ^ Benefits, Policy Considerations,​ Risks and Design requirements ​ |
 ^ [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​1.4_req:​2_nonfunc:​10_portability:​01_adapt ​       | Adaptability ]] | <​WRAP>​ ^ [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​1.4_req:​2_nonfunc:​10_portability:​01_adapt ​       | Adaptability ]] | <​WRAP>​
Line 101: Line 101:
 </​table>​ </​table>​
  
-  : **Note:** There should be no tradeoffs between **Non-Functional Requirements** and any existing requirements identified in [[https://​www.federalreserve.gov/​publications/​files/​money-and-payments-20220120.pdf | White Paper]] as determined by the OMG [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] ​+  : **Note:** There should be no tradeoffs between **Non-Functional Requirements** and any existing requirements identified in [[https://​www.federalreserve.gov/​publications/​files/​money-and-payments-20220120.pdf | White Paper]] as determined by the OMG's CBDC WG [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] ​
  
 === Discussion of Example === === Discussion of Example ===
Line 120: Line 120:
   * //​[[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​archdaptability | Architecture Adaptability]] - Connectors between software components change without having to change the components. This again comes down to having well-defined,​ stable APIs for the connectors. For example, the [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​xapend:​xapend.a_glossary:​u:​unix|Unix]] File System (UnixFS) is a connector between software components and the physical filesystem. The associated UnixFS library can be exchanged for the [[https://​ipfs.io/​ | InterPlanetary File System (IPFS) ]] UnixFS connector and the software component should have no to minimal impact.//   * //​[[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​archdaptability | Architecture Adaptability]] - Connectors between software components change without having to change the components. This again comes down to having well-defined,​ stable APIs for the connectors. For example, the [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​xapend:​xapend.a_glossary:​u:​unix|Unix]] File System (UnixFS) is a connector between software components and the physical filesystem. The associated UnixFS library can be exchanged for the [[https://​ipfs.io/​ | InterPlanetary File System (IPFS) ]] UnixFS connector and the software component should have no to minimal impact.//
  
-Obviously, this is just an example, and the Federal Reserve should adopt the information and update the information in the [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] and also perform their own assessment a similar to that presented in Table {{ref>​xreftable}}. The discussions and justifications for each requirement need to be captured for future reference. For example, **''​B00008''​** would have its own discussion area within the CBDC requirements document.+Obviously, this is just an example, and the Federal Reserve should adopt the information and update the information in the OMG's CBDC WG [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] and also perform their own assessment a similar to that presented in Table {{ref>​xreftable}}. The discussions and justifications for each requirement need to be captured for future reference. For example, **''​B00008''​** would have its own discussion area within the CBDC requirements document.
  
 ==== Functional Requirements Design Principles ​ ==== ==== Functional Requirements Design Principles ​ ====
Line 138: Line 138:
  2. [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​1.4_req:​1_func:​access ​  | Access Control ]]  2. [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​1.4_req:​1_func:​access ​  | Access Control ]]
  
-Some of these **Functional Requirements** were alluded to in the White Paper, but not directly specified or defined. The Table {{ref>​funcxreftable}} provides an example of cross-referencing the **Functional Requirements** to the Benefits, Policy Considerations,​ Risks and Design requirements identified in the [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] done by the [[https://​www.omg.org/​ | Object Management Group ]].+Some of these **Functional Requirements** were alluded to in the White Paper, but not directly specified or defined. The Table {{ref>​funcxreftable}} provides an example of cross-referencing the **Functional Requirements** to the Benefits, Policy Considerations,​ Risks and Design requirements identified in the [[cbdc:​public:​cbdc_omg:​04_doc:​12_summary:​start| White Paper Analysis]] done by the [[https://​www.omg.org/​ | Object Management Group'​s ​]] CBDC WG.
  
 === Examples === === Examples ===
Line 144: Line 144:
  
 <table funcxreftable>​ <table funcxreftable>​
-<​caption>​Example of mapping a subset of requirements identified during the White Paper Analysis conducted by the OMG.</​caption>​+<​caption>​Example of mapping a subset of requirements identified during the White Paper Analysis conducted by the OMG's CBDC WG.</​caption>​
 ^ Functional Requirement ​ ^ Benefits, Policy Considerations,​ Risks and Design requirements ​ | ^ Functional Requirement ​ ^ Benefits, Policy Considerations,​ Risks and Design requirements ​ |
 ^ [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​1.4_req:​1_func:​platform:​hw_arch ​  | Hardware Platforms ]] | <​WRAP>​ ^ [[https://​www.omgwiki.org/​dido/​doku.php?​id=dido:​public:​ra:​1.4_req:​1_func:​platform:​hw_arch ​  | Hardware Platforms ]] | <​WRAP>​
cbdc/public/cbdc_omg/04_doc/20_comments/dsn/q22/start.1652827218.txt.gz · Last modified: 2022/05/17 18:40 by nick