Subject: Request for well-known URI: openapi

From: Anatoli Babenia <[email-masked]>
Date: Wed, 10 Jul 2019 09:21:37 +0300

URI suffix:  openapi

   Change controller:  [email-masked],
https://github.com/yakshaveinc/tasks/issues/48

   Specification document(s):  The field returns URL to OpenAPI
specification. For example, http://example.com/.well-known/openapi
could return https://api.example.com/v2/openapi.json

   Related information:  https://en.wikipedia.org/wiki/OpenAPI_Specification

-- 
Anatoli Babenia

+1 (650) 605-3365
+375 (29) 320-4241

---

From: Mark Nottingham <[email-masked]>
Date: Wed, 10 Jul 2019 16:36:01 +1000

Hi Anatoli,

The "specification document" field needs to point to a stable specification; here, part of the OpenAPI specification, presumably.

Cheers,

> On 10 Jul 2019, at 4:21 pm, Anatoli Babenia <[email-masked]> wrote:
> 
>   URI suffix:  openapi
> 
> _______________________________________________
> wellknown-uri-review mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/wellknown-uri-review

--
Mark Nottingham   https://www.mnot.net/

---

From: Anatoli Babenia <[email-masked]>
Date: Wed, 10 Jul 2019 10:06:49 +0300

Hi Mark.

Unfortunately, the discovery mechanism is out of scope of OpenAPI specification.
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md

-- 
Anatoli Babenia

+1 (650) 605-3365
+375 (29) 320-4241