This repository was archived by the owner on Nov 18, 2024. It is now read-only.
Standard vs. Open Formats #7
ALRubinger
started this conversation in
General
Replies: 2 comments 3 replies
-
Agreed. My thoughts:
|
Beta Was this translation helpful? Give feedback.
2 replies
-
If there are standards efforts that cover the same things we need, we should be using/advancing those standards. Creating something random/divergent should be the last resort after lengthy review of existing standards options and initiatives. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In our discussion about decomposing the system and decentralization, @mistermoe proposed 5 aspects of decentralized systems, and encouraged us to view "decentralization" as a spectrum.
I'd like us to dig into one of them here: "standards-based formats". @mistermoe cites:
@csuwildcat also takes the stance:
I offer a tweak:
I propose making our message formats and protocols an open format. As we prove its worth in the field and assemble buy-in from the community, we may pursue parking it in a standards body to strengthen the portability guarantee.
IMO standards bodies are for hardening, not for innovation.
Some examples of open formats that preceded standards:
I think this approach will free us to move faster without dropping portability for our users.
Beta Was this translation helpful? Give feedback.
All reactions