Alignment of the simple edge discovery API as per the CAMARA commonality group guidelines

[gunjald]

Contribution from 6G-XR (https://www.6g-xr.eu/) towards the alignment of the simple edge discovery API as per the CAMARA commonality group guidelines for the REST API

[gunjald]

Accidentally raised the request hence closing.

[gunjald]

Contribution from 6G-XR (https://www.6g-xr.eu/) towards the alignment of the simple edge discovery API as per the CAMARA commonality group guidelin](#122)

[Kevsy]

Thanks @gunjald - in parallel I've been doing the same exercise, namely to align the data types and error types with those used in other CAMARA APIs (in particular the various device identifiers used in QOD and Device Status) and to ensure alignment with Commonalities API style guide. I also propose to simplify the API by removing the unused query parameters and datatypes (zone, region) which are rather part of the 'full' discovery API.

So: I propose I take the guidance from the commit here and look to combine it with my new version (the goal is the same).

[Kevsy]

This should be fixed with #127 which aligns the API with Commonalities

[Kevsy]

Hi @gunjald , the relevant changes are incorporated into PR #127, with the exception of 3-legged authorisation as we need to discuss whether Simple Edge Discovery should require end user consent, even if it is only the network IP range being used to determine the closest MEC platform. Overall this is part of a bigger discussion that encompasses all CAMARA APIs - so my proposal is to close this PR (since PR 127 incorporates most of the changes) and then we ask for the Steering Commitee position on exceptions to 3-legged auth.