Is "application" relevant for Camara?

[shilpa-padgaonkar]

Problem description The concept of application identifier is discussed in the Camara QoD subproject QoD-issue .

• Do we need to represent application in the common schema file under commonalities artifacts or
• Do we need to also have a developer facing Camara application API (including its implicit subscriptions)?
• Do we think this is out of Camara scope?

Possible evolution Decide if application is relevant for Camara or not.

Alternative solution

Additional context

[eric-murray]

The Edge Cloud sub-project already makes extensive use of application identifiers.

See, for example:

• https://github.com/camaraproject/EdgeCloud/blob/main/code/API_definitions/Traffic%20Influence/Traffic_Influence.yaml#L56
• https://github.com/camaraproject/EdgeCloud/blob/main/code/API_definitions/Resource%20Management/EdgeCloudApi_v0.0.5.yaml#L110
• https://github.com/camaraproject/EdgeCloud/blob/main/code/API_definitions/Workload%20Orchestration/App.yaml#L293

[SyeddR]

Thanks @shilpa-padgaonkar for bringing this issue to commonalities. Application identifiers are useful and required in various use cases such as QOD issue. And as @eric-murray pointed out the construct is heavily used in edge cloud working group.

We also need to define if client-id could serve the purpose. Is client-id an application identifier or owner identifier? I created the issue 126 in identity work stream.