Merge branch 'master' into lifecycle

REQUIREMENTS/link-relation-types.md

@@ -22,9 +22,8 @@ Results of the brainstorming discussion in arch call on Sept 17th.
 
 ### Requirements:
 
-
-Describe a topology of things that are combined in a mashup.
-Connect a thing description with a thing model.
+- Describe a topology of things that are combined in a mashup.
+- Connect a thing description with a thing model.
 
 ### Types of relationships:
 
@@ -34,24 +33,24 @@ If the type is a URL, a link is the natural chice for represnting it.
 
 when you think about how you model things in UML: inheritance, implementation, aggregation
 
-"Source"/"Search", to identify the source from which the TD was obtained (e.g. a device, database, directory)
-"Inheritance/implements" for Thing Model - TD relationship
-"Containment": "contained by" or "is contained" - system components
-"Aggregation": set of entities
-"Collection": 
-"Metadata", e.g. company, maintainer, license ...
-"Documentation": 
-("Current")
-"Previous": version of the document
-"member", "Item"
-"manifest": point to SW implementing the TD
-"Profile": denote compliance
+- "Source"/"Search", to identify the source from which the TD was obtained (e.g. a device, database, directory)
+- "Inheritance/implements" for Thing Model - TD relationship
+- "Containment": "contained by" or "is contained" - system components
+- "Aggregation": set of entities
+- "Collection": 
+- "Metadata", e.g. company, maintainer, license ...
+- "Documentation": 
+- ("Current")
+- "Previous": version of the document
+- "member", "Item"
+- "manifest": point to SW implementing the TD
+- "Profile": denote compliance
 
 #### Not in IANA list:
-"proxy-to" (security or protocol proxy or both)
-"twin-of"
-"shadow": caching data
-"simulation", could be a shadow or a twin
+- "proxy-to" (security or protocol proxy or both)
+- "twin-of"
+- "shadow": caching data
+- "simulation", could be a shadow or a twin
 
 ### Entity types:
 * Thing model
@@ -68,8 +67,8 @@ when you think about how you model things in UML: inheritance, implementation, a
 * More than one link of the same type? (Example is a TD that implements multiple TMs)
 * Is a "TD implements TM" relationship inclusive or exclusive?
 * When to use links and when to use semantic relationships?
-- not use a link if the linked entity is not dereferencable
-- if it is primarily a concept, a semantic realtionship is more appropriate
+* not use a link if the linked entity is not dereferencable
+* if it is primarily a concept, a semantic realtionship is more appropriate
 
 ### Related standards:
 
@@ -78,7 +77,6 @@ Any more IoT specific link relation types: Platform Industry 4.0?
 
 ### Other references:
 
-
 https://www.iana.org/go/rfc8288
 
 Link relations: