From 167f7f1b4ff907ab589bbc667c74a9c396c867b0 Mon Sep 17 00:00:00 2001 From: Esben Haabendal <esben.haabendal@huawei.com> Date: Fri, 8 Jul 2022 13:34:33 +0200 Subject: [PATCH] Add section on OpenHarmony compatibility in Vision and Aims chapter Signed-off-by: Esben Haabendal <esben.haabendal@huawei.com> --- overview/oniroproject-vision.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/overview/oniroproject-vision.rst b/overview/oniroproject-vision.rst index b96ca60..e3c3804 100644 --- a/overview/oniroproject-vision.rst +++ b/overview/oniroproject-vision.rst @@ -44,6 +44,24 @@ able to choose from Java, Extensible Markup Language (XML), C/C++, JavaScript (JS), Cascading Style Sheets (CSS), and HarmonyOS Markup Language (HML) to develop applications for |main_project_name|. +OpenHarmony Compatibility +------------------------- + +|main_project_name| will be OpenHarmony compatible. It will include the services +and frameworks required by OpenHarmony specification, and provide the APIs +required by OpenHarmony specification, so that you can develop products that can +interoperate with other OpenHarmony products and be certified as OpenHarmony +compatible. + +OpenHarmony compatibility will enable required OpenHarmony features in the +kernel layer, system services layer and framework layer, allowing the addition +of OpenHarmony compatible applications. + +Due to the inherent modularity of the Oniro build system (OpenEmbedded), +individual projects will be able to pick and choose from the OpenHarmony +compatibility features, allowing to build products with just the parts that are +needed. + Technical Architecture ---------------------- -- GitLab