Merge pull request #833 from mandy-chessell/dev-dojo

Add RelationalDatabase type

site/docs/release-notes/4-3.md

@@ -8,7 +8,8 @@ _**These are DRAFT release notes.  The notes will be updated until & when 4.3 is
 
 ??? functional "Open Metadata Types"
     * The  [*HostClusterMember*](/types/0/0035-Complex-Hosts) relationship has new properties *memberRole* and *additionalProperties* to improve ability to describe a host cluster operation.
-    * The  [*DataSet*](/types/0/0010-Base-Model), [*DataStore*](/types/2/0210-Data-Stores), [*DeployedAPI*](/types/2/0212-Deployed-APIs), [*DeployedSoftwareComponent*](/types/2/0215-Software-Components) and [*DataFeed*](/types/2/0223-Events-and-Logs) entity types each have a new attribute called *deployedImplementationType* to describe the technology supporting the associated component.  This addition is to enable integration connectors to be more precise in describing the technology they are cataloguing.  This attribute is also used in [*SoftwareServerPlatform*](/types/0037-Software-Server-Platforms), [*SoftwareServer*](/types/0/0040-Software-Servers) and [*SoftwareCapability*](/types/0/0042-Software-Capabilities) entity types; along with the [ServerPurpose](/types/0/0041-Server-Purpose) and [*CloudPlatform*](/types/0/0090-Cloud-Platforms-and-Services) classification.  There are subtypes of *DataStore* (*LogFile*, *GraphStore*, *MetadataRepository*) have been modified because they already include the property and duplicate properties in the type hierarchy cause indexing problems in some repositories.  Similarly, there were duplicated *deployedImplementationType* properties in the [*ServerPurpose*](/types/0/0041-Server-Purpose) classification affecting *RepositoryProxy* and *MetadataServer* classifications. 
+    * The  [*DataSet*](/types/0/0010-Base-Model), [*DataStore*](/types/2/0210-Data-Stores), [*DeployedAPI*](/types/2/0212-Deployed-APIs), [*DeployedSoftwareComponent*](/types/2/0215-Software-Components) and [*DataFeed*](/types/2/0223-Events-and-Logs) entity types each have a new attribute called *deployedImplementationType* to describe the technology supporting the associated component.  This addition is to enable integration connectors to be more precise in describing the technology they are cataloguing.  This attribute is also used in [*SoftwareServerPlatform*](/types/0037-Software-Server-Platforms), [*SoftwareServer*](/types/0/0040-Software-Servers) and [*SoftwareCapability*](/types/0/0042-Software-Capabilities) entity types; along with the [ServerPurpose](/types/0/0041-Server-Purpose) and [*CloudPlatform*](/types/0/0090-Cloud-Platforms-and-Services) classification.  There are subtypes of *DataStore* (*LogFile*, *GraphStore*, *MetadataRepository*) have been modified because they already include the property and duplicate properties in the type hierarchy cause indexing problems in some repositories.  Similarly, there were duplicated *deployedImplementationType* properties in the [*ServerPurpose*](/types/0/0041-Server-Purpose) classification affecting *RepositoryProxy* and *MetadataServer* classifications.
+    * A new entity type called [*RelationalDatabase*](/types/2/0224-Databases) has been added to distinguish databases that follow the relational schema and can be accessed through JDBC.
 
 
 ??? functional "Integration Connector function"

site/docs/types/2/0224-Databases.md

@@ -8,16 +8,24 @@ A database is a structured store of data.  It is typically managed as a shared d
 ![UML](0224-Databases.svg)
 
 
-## Database
+## Database entity
 
 The *Database* entity represents the database store.  It inherits from [*DataStore*](/types/2/0210-Data-Stores) to indicate that the physical data is stored under this asset.  
 
-## DeployedDatabaseSchema
+## RelationalDatabase entity
+
+The *RelationalDatabase* entity defines a database that supports the relational schema that can be accessed via the Java Database Connectivity (JDBC) interface.
+
+## DeployedDatabaseSchema entity
 
 Often the data within the database is organized into distinct collections of data for use by the different applications or processes.  The structure of the data in each collection is called a database schema.  Such database schemas are used to limit the scope of data that a consuming application/process is exposed to.  Where this is the case, each database schema is represented by the *DeployedDatabaseSchema* entity.  *DeployedDatabaseSchema* inherits from [*DataSet*](/types/0/0010-Base-Model) to indicate that it is a logical collection of data.  The physical data is stored in the database.
 
 *DeployedDatabaseSchema* is linked to its *Database* using the [*DataContentForDataSet*](/types/2/0210-Data-Stores) relationship.
 
+## TableDatabase entity
+
+The *TableDataSet* can be used to identify an important table in a database that can be considered an asset in its own right.
+
 !!! info "Defining the structure of data within a database"
     The structure of the data stored in a database is represented by a subclass of [*RootSchemaType*](0530-Tabular-Schemas).  For example, if the database has a relational database structure (ie tables and columns) the root schema type used is [*RelationalDBSchemaType*](/types/5/0534-Relational-Schemas).