You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section 2. "SHOULD publish the /.well-known/api-catalog URI at a predictable
location." This section is troublesome. RFC 8615, which you cite, begins "This memo defines a path prefix for "well-known locations", "/.well-known/".
So if someone is trying to conform to this draft, your api-catalog pretty well MUST
be at the /.well-known. So maybe it would be simpler to say something like "The
API Catalog MUST be named "api-catalog" in a well-known location as described
by [RFC8615]?
The text was updated successfully, but these errors were encountered:
From Tim Bray's ARTART last call review:
Section 2. "SHOULD publish the /.well-known/api-catalog URI at a predictable
location." This section is troublesome. RFC 8615, which you cite, begins "This memo defines a path prefix for "well-known locations", "/.well-known/".
So if someone is trying to conform to this draft, your api-catalog pretty well MUST
be at the /.well-known. So maybe it would be simpler to say something like "The
API Catalog MUST be named "api-catalog" in a well-known location as described
by [RFC8615]?
The text was updated successfully, but these errors were encountered: