Add OptimalEdgeDiscovery enhancement proposal: pre-deployment viability discovery

[dimitrisgiannopoulos]

What type of PR is this?

enhancement/feature

What this PR does / why we need it:

This PR introduces an enhancement proposal for Optimal Edge Discovery (OED) to support pre-deployment viability discovery.

It extends the current runtime-focused model of OED to allow developers to assess which edge options are viable in a target area before deployment.

Which issue(s) this PR fixes:

Related to #311

Special notes for reviewers:

This is a scope enhancement proposal. Feedback is especially welcome on whether this functionality should be integrated into OED or addressed as a separate API.

Additional documentation

Presentation: CAMARA_EDP_API_presentation.pdf

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: dimitrisgiannopoulos / name: Dimitrios Giannopoulos (6468f23)
• ✅ login: dimitrisgiannopoulos / name: Dimitris Giannopoulos (29487e8, 7a640db, f184b80)

[albertoramosmonagas]

Hi @dimitrisgiannopoulos, you're changing the API-Scope-Enhacement-Template.md instead of creating a new one document for your proposal.

[dimitrisgiannopoulos]

Hi @albertoramosmonagas, thanks for pointing that out. I restored the template file and moved my proposal into a new document under documentation/APIBacklog/.

[albertoramosmonagas]

Hi @dimitrisgiannopoulos, Thanks for the update. This is a much stronger version of the proposal. The added delimitation table and the minimal API contract sketch make the intent much clearer.

That said, the updated text also reinforces the main concern from the backlog side: the proposal now looks even more like a distinct capability than a natural extension of OED, since it changes timing, input context, functional objective, and response semantics.

So the key question for discussion is no longer whether the proposal is understandable, but whether OED is really the right home for it. As this is being proposed as an enhancement of an existing API, input from the OED maintainers will be essential for backlog evaluation.

[hdamker]

@dimitrisgiannopoulos Is this proposal based on an issue / discussion within the EdgeCloud Sub Project? Do you have references to the issues/minutes of this discussion? I would consider this as the right path before the API Backlog working group is considering the proposal.