Comments for discussion on Edge Terminology

[Kevsy]

@Kevsy posted a starting point draft for Edge Terminology using Mahesh's email contribution

Inital comment from @maheshc01
Agree with you that we can use the Definitions in OPG requirements as a reference.
We would still need to identify terminology which might be specific to the usecases we are trying to cover and not available in the OPG document.
An example would be "Optimal Edge Cloud'', While "Edge Cloud" is defined in OPG, during the discovery process we would refer to subset of the Edge Clouds as "Optimal Edge Cloud" and we would need to create the definition for what we mean by "Optimal Edge Cloud"

Below are the definitions as used by 5GFF, we could reword some of them as required and include them in the definitions we have from OPG.
Similarly, we would need to identify terms specific to workload orchestration, for example, if we say "Workload", what do we really mean by it.
I dont have any terms or references to share on workload orchestration at the moment, will look it up and share.

Response from @gunjald

1. At the start of the taxonomy evolution we may keep the references to keywords that are not yet agreed in EdgeCloud for later stages. For example reference to “MEC Exposure and Experience Management APIs” can be delayed while we may propose abstract terms to indicate to the functionality they refer to
2. The term “Density” I am not sure how explainable it will be from developer perspective. Or we may consider something like number of application clients or user clients an application instance can serve in a region/zone etc
3. “Optimal MEC Platforms”: It should also consider the reference to the application client/user clients which are primary consumer of the edge applications hosted on optimal MEC platforms. Also note that in OPG, the OP PRD has detailed on the what is an optimal MEC platform but a definition is not present in the section 1.4
4. Region and Zone: Are also available in the OPG. Zone is referred as “Availability Zone” in OPG
5. Service Profile: Similar to Optimal MEC Platform, the application meta is defined in OPG in “Table 3: Information elements in the Application Manifest data model”. The Service Profile may refer to set of attributes for an edge application e.g., application name, version, application images, QoS profiles, scaling policy, availability zone information etc
6. Also, I think we should add application clients (AC) or User Clients(UC) to refer to the device side of the elements
7. Similarly NBI, UNI which refers to external users interfaces should also be defined