camaraproject / Commonalities

Repository to describe, develop, document and test the common guidelines and assets for CAMARA APIs
Apache License 2.0
14 stars 28 forks source link

Add rules in design guideline about multi-endpoint API design & implementation requirement #246

Open bigludo7 opened 4 months ago

bigludo7 commented 4 months ago

Problem description In discussion #160 and #212 we have long thread of discussion about implementation of multi-endpoint API.

Several opinions are provided but we have not a clear decision/pattern on how we manage this.

  1. Do we decide that an API must be fully implemented (all endpoints have to be able to provide 2xx response) in order to be "certified"* ?
  2. (if 1. answer is yes) If we decide that an API must be fully implemented in order to be "certified" do we add a rule to enforce multi-yaml definition when distinct endpoint tackles independent data?
  3. (if 1.answer is no) If we allow partial implementation do we mandate use of 501 for non implemented endpoint? As suggested in the design guideline and outcome of discussion #160

Additionally mention of Runtime Restriction API should be probably in the mix for partial implementation but as we cannot assume it will be used by all API provider & consumer.

(* as we have a GSMA certification but not CAMARA certification we can assume here GSMA certification but this point should be discussed with @MarkCornall and @trehman-gsma)

Expected action Get a decision on these questions once for all and write some rules about it in the design guideline document

Additional context @rartych please do not hesitate to provide comments if I wrongly translate commonalities discussion we had July 8th

hdamker commented 4 months ago

As of TSC Minutes https://wiki.camaraproject.org/display/CAM/2024-07-18+TSC+Minutes:

gmuratk commented 1 month ago

Is there a PR in progress for this issue?