Skip to content
This repository was archived by the owner on Aug 25, 2024. It is now read-only.

Commit edcf9ec

Browse files
Open Architecture Working Grouppdxjohnny
Open Architecture Working Group
authored andcommitted
docs: rfcs: Open Architecture: Initial commit
Signed-off-by: John Andersen <[email protected]>
1 parent 3018561 commit edcf9ec

File tree

1 file changed

+77
-0
lines changed

1 file changed

+77
-0
lines changed

Diff for: docs/rfcs/0000-Open-Architecture.txt

+77
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
Open Architecture Working Group
2+
Internet-Draft
3+
Intended status: Draft
4+
Expires: June 1, 2023
5+
March 12, 2022
6+
7+
8+
Open Architecture: Methodology for interpreting directed graphs as
9+
any system architecture.
10+
11+
Abstract
12+
13+
This document describes the Open Architecture a proxy format for domain
14+
specific representations of architecture.
15+
16+
Strategic plans work with the gatekeeper and prioritizer to negotiate and
17+
execute off chain contracts.
18+
19+
Models within strategic plans are involved in risk tolerance.
20+
21+
Smart contracts with understanding of risk are effectively entities making
22+
decisions based on models. This allows for mutation in implementation while
23+
maintaining principles.
24+
25+
The smart contract is able to make its own decisions based on learned
26+
experience (models) so as to continue to operate until its strategic goals
27+
are meet. As measured by oracle data ordained from trusted parties as is
28+
applicable to context. Where chains of trust are established via Peer DIDs
29+
between entities and data for provenance. Leveraging verifiable credentials
30+
(opencert) for review system to measure risk in absence of attestation.
31+
32+
The Open Architecture builds on the Open Digital Asset Protocol. We define a
33+
methodology for interpreting DIDs as directed graphs to describe any system
34+
architecture. We suggest methods for interpreting those graphs as software
35+
and hardware architectures.
36+
37+
Propose that the format which can be used to describe any system
38+
architecture be called the Open Architecture (aka Universal Blueprint,
39+
DataFlow, System Context). The Open Architecture describes assets using the
40+
Open Digital Asset Protocol. One option for definition of a system
41+
architecture via the Open Architecture is to link via directed graphs,
42+
component domain specific architectures, i.e. hardware, software, digital,
43+
physical, business process, or any combination thereof.
44+
45+
Status of This Memo
46+
47+
This Internet-Draft will be submitted in full conformance with the
48+
provisions of BCP 78 and BCP 79.
49+
50+
This draft will expire on June 1st, 2023.
51+
52+
Table of Contents
53+
54+
1. Introduction
55+
2. References
56+
57+
1. Introduction
58+
59+
The Open Architecture enables hybrid on/off chain smart contacts.
60+
61+
It does this by incorporating risk management into architecture definition /
62+
smart contract.
63+
64+
2. References
65+
66+
2.1. Normative References
67+
68+
[draft-hargreaves-odap-03]
69+
Internet Engineering Task Force, "Open Digital Asset Protocol"
70+
ODAP, November, 2021,
71+
<https://datatracker.ietf.org/doc/html/draft-hargreaves-odap-03>.
72+
73+
2.2. Informative References
74+
75+
[alice-discussion]
76+
DFFML Authors, "Alice", May 2022,
77+
<https://github.com/intel/dffml/discussions/1369>.

0 commit comments

Comments
 (0)