From 70a45b68bf756e2db025712a34c2ad03d444a97d Mon Sep 17 00:00:00 2001 From: Yongjing Zhang <zhangyongjing@huawei.com> Date: Fri, 11 May 2018 09:55:40 +0200 Subject: [PATCH] fix the relationship between 'Module' & 'ModuleClass' --- SDT/schema3.0/docs/SDT_Components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SDT/schema3.0/docs/SDT_Components.md b/SDT/schema3.0/docs/SDT_Components.md index bac78e0..13c6dfc 100644 --- a/SDT/schema3.0/docs/SDT_Components.md +++ b/SDT/schema3.0/docs/SDT_Components.md @@ -185,7 +185,7 @@ The advantage of identifying a subset of generic *ModuleClasses*, described belo Every [Device](#Device) can then be described by a collection of *Modules* (functionality). In the simplest examples, where there are no extensions needed, each *ModuleClass* has exactly one "child" Module ... in such cases the software developer can consider the two terms to be the same. -The relationship between a *ModuleClass* and a *Module* is very similar to the specification of a class and an instantiated object in an object oriented programming language. +The relationship between a *ModuleClass* and a *Module* is very similar to the specification of a superclass and a subclass in an object oriented programming language. **ModuleClass** -- GitLab