Remove support for supplementary properties from SchemaElements

[mandy-chessell]

Signed-off-by: Mandy Chessell mandy.e.chessell@gmail.com

Description

Supplementary properties are used to add additional descriptive properties to technical metadata elements.

This capability is supported by Asset Manager OMAS, Stewardship Action OMAS, Governance Program OMAS. It is soon to be added to Asset Owner OMAS and Asset Consumer OMAS (via OCF) to allow the retrieval of ths information to owners and consumers.

Asset Manager OMAS supported this capability for Assets, SchemaElements, Endpoints and SoftwareCapabilities. This PR removes supplementary properties support for SchemaElements because the direct usage of the SchemaElements is typically done by technical users. Business users typically do not identify with a specific schema element. They would more likely be using glossary terms linked with Semantic Assignment to retrieve collections of schema elements that match their business understanding. Therefore the overhead of supporting business descriptions for schema elements is not justified.

Related Issue(s)

• Issue covering the development of - Create Asset Manager OMAS and Catalog Integrator OMIS #3562
• Issue covering the discussion of why removing supplementary properties from schema elements - [BUG] Data Manager OMAS and Asset Manager OMAS handle displayName and description differently #7230

Testing

FVT testing as much as it is. Asset Manager OMAS is still in its initial development phase and so the FVTs do not cover all of the features.

Release Notes & Documentation

There is a matching PR on egeria-docs to remove schema elements from the description of supplementary properties.

Additional notes

[mandy-chessell]

This is the PR to remove SchemaElements from the description of supplementary properties

odpi/egeria-docs#627