Add new information supply chain attributes

site/docs/guides/index.md

@@ -7,17 +7,19 @@ Egeria's guides provide practical guidance on different aspects of using Egeria
 
 --8<-- "snippets/getting-started.md"
 
+* [User Interfaces](/user-interfaces) - Illustrates different types of user interaction styles available in Egeria.
+* [Features](/features) - Provides a detailed guide to the governance features of Egeria.
 * [Planning Guide](/guides/planning) - The planning guide describes how to plan your Egeria installation and the development of the metadata definitions that will drive its use.  Part of this planning process makes use of the following catalogs:
 
     * [Content Pack Catalog](/content-packs) - the content pack catalog provides detailed information about the content packs available for Egeria.  These content pack provide metadata to bootstrap your deployment.
     * [Connector Catalog](/connectors) - the connector catalog provides a list of connectors available for Egeria.
+    * [Template Catalog](/catalog-templates) - details of the cataloguing templates prebuild in Egeria.
 
 * [Integration Guide](/guides/integration) - the integration guides describes how to set up integrations between Egeria and third party technologies.  It also makes use of the content packs and connector catalogs.
 * [Administration Guide](/guides/admin) - the administration guide describes how to mange Egeria's configuration.
 * [Migration Guide](/guides/migration/migrating-configuration-documents) - Egeria strives to maintain compatibility of APIs and file formats from release to release.  The migration guide covers techniques to migrate aspects of Egeria where compatibility between releases was not possible..
 * [Operations Guide](/guides/operations/overview) - Describes commands to control and monitor an Egeria deployment.
 * [Diagnostic Guide](/guides/diagnostic/overview) - Problem determination methods and guidance.
 * [Developer Guide](/guides/developer) - the developer covers how to build connectors, utilities that call Egeria, and open metadata archives.
-* [Features](/features) - Provides a detailed guide to the governance features of Egeria.
 
 --8<-- "snippets/abbr.md"

site/docs/types/0/0056-Resource-Managers.md

@@ -9,11 +9,18 @@ A resource manager is a software capability that manages one or more resources.
 
 ## FileSystem
 
-The `FileSystem` is a collection of stored files organized in a folder hierarchy.  They are managed by many resource managers as long as they have access privileges.
+The `FileSystem` is a collection of stored files organized in a folder hierarchy.  They are managed by many resource managers as long as they have access privileges.  Each resource manager may access these files through a different mount point.  The effect is that the full path name of the file may differ from resource manager to resource manager.  Therefore, the attributes captured for a file system are:
+
+* *encryption* - type of encryption used on the files.
+* *format* - format used to store the files.
+* *actualMountPoint* - root of the file path name that is due to the resource manager's view of the file system.
+* *canonicalMountPoint* - value to replace the actual mount point with when storing/retrieving metadata about a file within the file system.
+
+The use of the actualMountPoint and canonicalMountPoint is critical to allow different tools in the open metadata ecosystem to share metadata about the same files.
 
 ## FileManager
 
-The `FileManager` manages a collection of files - it is typically the owner of the files and they are access through its APIs.
+The `FileManager` manages a collection of files - it is typically the single owner of the files, and they are access through its APIs.  A photo management application is an example of such a file manager.
 
 ## AssetManager
 

site/docs/types/7/0720-Information-Supply-Chains.md

@@ -22,21 +22,21 @@ If additional processing is required to move the data between solution component
 
 ![UML](0720-Information-Supply-Chains.svg)
 
-## InformationSupplyChain
+## InformationSupplyChain entity
 
-An *InformationSupplyChain* entity identifies an information supply chain.  It contains the description of the purposes and scope of the information supply chain and the description of its importance to the business.
+An *InformationSupplyChain* entity is a [Referenceables](/types/0/0010-Base-Model) that identifies an information supply chain.  It contains the description of the purposes and scope of the information supply chain and the description of its importance to the business.
 
-## InformationSupplyChainComposition
+## InformationSupplyChainComposition relationship
 
 The *InformationSupplyChainComposition* relationship links an *InformationSupplyChain* entity to its segments.
 
-## InformationSupplyChainSegment
+## InformationSupplyChainSegment entity
 
-An *InformationSupplyChainSegment* entity identifies an information supply chain segment.  It contains the description of the segment and its scope.  It includes expected volumetrics to use in the governance processes that are monitoring the information supply chain segment.
+An *InformationSupplyChainSegment* entity is a [Referenceables](/types/0/0010-Base-Model) that identifies a significant prt of an information supply chain.  It contains the description of the segment and its scope.  It includes expected volumetrics to use in the governance processes that are monitoring the information supply chain segment.
 
 ## InformationSupplyChainLink
 
-The *InformationSupplyChainLink* relationship links the information supply chain segments, and descriptions of the data sources and destinations together into a graph.  This graph represents the highest level abstraction of the operation of the information supply chain.
+The *InformationSupplyChainLink* relationship links the information supply chain segments, and descriptions of the data sources and destinations together into a graph.  This graph represents the highest level abstraction of the operation of the information supply chain. The *label* and *description* attributes help to explain how/why the information supply chain progresses.
 
 ## Example
 

site/docs/types/7/0735-Solution-Ports-and-Wires.md

@@ -18,7 +18,7 @@ The structure of the requests/data provided by the port can be expressed as a [s
 
 ## SolutionLinkingWire
 
-The *SolutionLinkingWire* shows the linkage between solution components via their ports to other elements in the architecture.  The *informationSupplyChainSegmentGUIDs* property allows linkage to the [information supply chains](/types/7/0720-Information-Supply-Chains) that identify critical data flows for the organization.  Each identified information supply chain segment typically comes from a different information supply chain.
+The *SolutionLinkingWire* shows the linkage between solution components via their ports to other elements in the architecture.  The *informationSupplyChainSegmentGUIDs* property allows linkage to the [information supply chains](/types/7/0720-Information-Supply-Chains) that identify critical data flows for the organization.  Each identified information supply chain segment typically comes from a different information supply chain.  The *label* and *description* attributes help to explain how/why the lineage flow progresses.
 
 ## SolutionPortDelegation