Mike Ralphson

I'd not say primarily, as they predate the presence of links in the spec., but that is another use as a shorthand for path + method.

@ggirodda as you suspect, this is not currently possible up to OpenAPI 3.0.x (there is an issue for tracking the way `swagger-ui` allows `allOf` and other schema-combining keywords outside of...

I think your example has `enum` and `state` in the reversed positions? I'm not totally sure of the general usefulness of your proposed `attributeIsValue` property... Couldn't you just do: ```yaml...

@tedepstein did I mention `APIs.json` for this? Was it this week's call or a previous one? My intention is that the extensions registry **MUST** include a `schema` in the metadata...

An example of the metadata (+markdown) for an extension within the current registry is: https://raw.githubusercontent.com/OAI/OpenAPI-Specification/523ad5747c7be6e523bef8768fa13a8a37044ea0/registries/_extension/x-twitter.md There you can see we plan on holding: ```yaml owner: MikeRalphson issue: XXX description: Used...

Both - may I please make a plea for brevity and succinctness in GitHub issues? While it is a strength to be able to write at length and dig into...

@tedepstein re: `apis.json` > I could be mistaken. In any case, I think Erik is right that APIs.json is a good example to follow in the general sense, but probably...

@dret > if i use the API to read the registry content, do i get this metadata? or do i now have to use the github API to crawl it...

@tedepstein > I think this got published to OpenAPIs.org just after this week's TSC call. The draft registry was actually committed as PR https://github.com/OAI/OpenAPI-Specification/pull/1762 on 28 Nov 2018. > Overall...

> i'd recommend to couple it less tightly with the implementation and focus on designing an API that captures all necessary data, independent of your implementation choice. it's not that...