Difference between revisions of "Open Format"
Jump to navigation
Jump to search
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Open Format]] is proposed by [[Yuan Xun]], which is a way to regulate the structures of [[Open Source]] | [[Open Format]] is proposed by [[Yuan Xun]], which is a way to regulate the structures of software resources. This is considered as a movement beyond the [[Open Source]] movement, since Yuan stated that just opening sources is not enough, the formats of software components must be meticulously documented and presented with design intent to reduce unnecessary rework and engineering. The idea of [[Open Format]] is being adopted to the design and implementation of [[PKC]]. | ||
=Relevant Implementations= | |||
One of the notable format is the [[Open API Specification]] format, also known as [[Swagger]]. | |||
<noinclude> | <noinclude> | ||
{{PagePostfix | {{PagePostfix | ||
|category_csd=Yuan Xun,Open Source,Systems Engineering | |category_csd=Yuan Xun,Open Source,Systems Engineering,Open Format | ||
}} | }} | ||
</noinclude> | </noinclude> | ||
Latest revision as of 14:04, 21 August 2022
Open Format is proposed by Yuan Xun, which is a way to regulate the structures of software resources. This is considered as a movement beyond the Open Source movement, since Yuan stated that just opening sources is not enough, the formats of software components must be meticulously documented and presented with design intent to reduce unnecessary rework and engineering. The idea of Open Format is being adopted to the design and implementation of PKC.
Relevant Implementations
One of the notable format is the Open API Specification format, also known as Swagger.
References
Related Pages