mpostol · mpostol · Jun 20, 2019 · May 13, 2019 · May 14, 2019 · May 15, 2019
diff --git a/CommonResources/Media/DataManagementExternalLibraries.png b/CommonResources/Media/DataManagementExternalLibraries.png
diff --git a/CommonResources/Media/MessageCentricCommunication.Domain.png b/CommonResources/Media/MessageCentricCommunication.Domain.png
diff --git a/CommonResources/Media/Networking/StackDomainModel.png b/CommonResources/Media/Networking/StackDomainModel.png
diff --git a/CommonResources/Media/PubSubMainComponents.png b/CommonResources/Media/PubSubMainComponents.png
diff --git a/Networking/ReferenceApplication/README.MD b/Networking/ReferenceApplication/README.MD
@@ -2,9 +2,10 @@
 
 ## Introduction
 
-The topics contained in the document [Getting Started Tutorial](../../Networking/SemanticData/READMEGettingStartedTutorial.md) are intended to give you quick exposure to the `OOI Reactive Application` network-based data exchange programming experience. Working through this tutorial gives you an introductory understanding of the steps required to customize existing  `OOI Reactive Application`.
+The topics contained in the document [Getting Started Tutorial](../../Networking/SemanticData/READMEGettingStartedTutorial.md) are intended to give you quick exposure to the `OOI Reactive Application` network-based data exchange programming experience. Working through this tutorial gives you an introductory understanding of the steps required to customize existing `OOI Reactive Application`.
 
 This project is aimed at implementation of an example of the `OOI Reactive Application` supporting producer and consumer roles simultaneously. The purpose of the `ReferenceApplication` is to demonstrate the concepts and architecture of the reactive networking application implementation, rather than to necessarily provide a realistic scenario for its use. For more extensive examples, see the [Semantic-Data Processing Architecture](../../SemanticData/README.MD).
+
 The `ReferenceApplication` hosts parts offering `Producer` and `Consumer` functionality. Both roles are implemented as independent threads that have a common graphical user interface (GUI) for diagnostic and configuration purpose.
 
 The `Producer` sends messages containing the fields defined in the configuration file using UDP communication stack. The values are simulated. The `Consumer` is configured to receive these messages from the UDP protocol stack. The `Consumer`to correctly decode the messages must have configuration defining the same set of fields. The data is encoded using *Variant* encoding.

diff --git a/Networking/SemanticData/Networking.SemanticData.csproj b/Networking/SemanticData/Networking.SemanticData.csproj
@@ -25,6 +25,7 @@
   </PropertyGroup>
   <ItemGroup>
     <None Remove="DataRepository\IBinding.cd" />
+    <None Remove="EthernetMapping.md" />
   </ItemGroup>
   <ItemGroup>
     <PackageReference Include="System.ComponentModel.Composition" Version="4.5.0" />

diff --git a/Networking/SemanticData/README.MD b/Networking/SemanticData/README.MD
@@ -10,7 +10,7 @@ For more in-depth information about creating `OOI Reactive Application` exchangi
 
 To promote interoperability this library is a collection of types aimed at implementation of the [Part 14 PubSub](README.PubSubMTF.md) standard.
 
-The code is tested using the Unit Tests located in the project: [Networking.SemanticData.UnitTest][OPC-UA-OOI.Networking.Tests.SemanticDatalUnitTest]
+The code is tested using the Unit Tests located in the project: [Networking.SemanticData.UnitTest][Networking.SemanticData.UnitTest]
 
 The preliminary code help documentation is here: [API Browser](http://www.commsvr.com/download/OPC-UA-OOI/index.html)
 

diff --git a/Networking/SemanticData/README.PubSubMTF.md b/Networking/SemanticData/README.PubSubMTF.md
diff --git a/Networking/SemanticData/README_EthernetMapping.md b/Networking/SemanticData/README_EthernetMapping.md
diff --git a/REFERENCES.md b/REFERENCES.md
@@ -135,3 +135,9 @@
 - [ISO/IEC 20922:2016: Message Queuing Telemetry Transport (MQTT) v3.1.1][ISO.MQTT]
 
 [ISO.MQTT]: https://www.iso.org/standard/69466.html
+
+## IEEE
+
+- [IEEE 802.3 ETHERNET WORKING GROUP][IEEE]
+
+[IEEE]:http://www.ieee802.org/3/
diff --git a/SemanticData/DesignDeploymentSupport.md b/SemanticData/DesignDeploymentSupport.md
@@ -82,9 +82,9 @@ An example of the tool meeting all this requirements is [OPC UA Address Space Mo
 - [1] [OPC UA Address Space Model Designer, 2019][CAS.ASMD]
 - [2] [OPC Unified Architecture Specification Part 3: Address Space Model, OPC Foundation, Rel. 1.04, 2017-11-22][Opc.UA.Part3]
 - [3] [OPC Unified Architecture Specification Part 5: Information Model, OPC Foundation, Rel. 1.04, 2017-11-22][OPC.UA.Part5]
-- [4] [Address Space Model Life-cycle]
-- [5] [Address Space and Address Space Model]
-- [6] [UA Information Model - Concept]
+- [4] [Address Space Model Life-cycle][Address Space Model Life-cycle]
+- [5] [Address Space and Address Space Model][Address Space and Address Space Model]
+- [6] [UA Information Model - Concept][UA Information Model - Concept]
 
 [CAS.ASMD]: http://www.commsvr.com/Products/OPCUA/UAModelDesigner.aspx
 [Opc.UA.Part3]:https://opcfoundation.org/developer-tools/specifications-unified-architecture/part-3-address-space-model/