From 6eed11638ec1758b8b9fea31fd89111c53dfdf09 Mon Sep 17 00:00:00 2001 From: Ben Forge <74168521+BenCheung0422@users.noreply.github.com> Date: Wed, 25 Mar 2026 00:18:10 +0800 Subject: [PATCH] EFP: Create: Adaptions of External Stds & Specs EFP 12: Adaptions of External Standards and Specifications --- efp/efp012/main.xml | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 efp/efp012/main.xml diff --git a/efp/efp012/main.xml b/efp/efp012/main.xml new file mode 100644 index 0000000..9beddc9 --- /dev/null +++ b/efp/efp012/main.xml @@ -0,0 +1,38 @@ + + + + + + + + +
+ +

+ Highly rights-protected standards (regarded as closed standards) would be completely not + adapted or employed in our areas. In this Architecture, we shall draft open standards for + the uses within this open Community, and possibly even the industries, if possible. + Using such closed standards may risk violations of rights of other bodies or parties. +

+ +
+
+ +

+ This includes ALL International Organization for Standardization (ISO) standards as an example, + except for certain materials that are publicly available or widespread. + Most contents in such standards are highly copyrighted, and the targets of those are seemingly + to be commercial bodies and industrial people that are urged to follow certain standards. +

+

+ For such cases, when we are to draft standards for our own usages in our fields, our own versions + of standards and specifications may be produced regardless of those external (independent) + official recognitions, due to their complete uselessness for our states of affairs. + In other cases, we should do our best to adapt widely recognized standards and specifications + whenever they suit our perspectives, attitudes, policies and works. +

+ +
+ +