Erik Wilde

On 2019-01-14 10:04, Mike Ralphson wrote: > Thanks @dret , that's all very helpful and I > really appreciate the offer of an extra set of eyes. > > The...

On 2019-01-16 16:11, Ted Epstein wrote: > I'm not clear yet on what a PR for a new registry entry should look > like, and I assume we don't yet...

a machine-readable registry definitely would be a good idea, if only for the reason that then it's easy to harvest and use the data without brittle screen-scraping. i think by...

On 2019-01-11 10:37, Ted Epstein wrote: > @dret , Again, Semoasa does not replace or > compete with the official OpenAPI registry; it serves a different purpose. i understand, and...

On 2019-01-11 11:28, Ted Epstein wrote: > @darrelmiller just pointed me to > http://spec.openapis.org/registry/extension/ > (https://twitter.com/darrel_miller/status/1083771084506304513) so i am > guessing this draft page and repo now have been incorporated...

On 2019-01-13 22:45, Mike Ralphson wrote: > @tedepstein did I mention |APIs.json| > for this? Was it this week's call or a previous one? not sure this is the best...

On 2019-01-14 10:16, Mike Ralphson wrote: > 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...

On 2019-01-14 12:06, Ted Epstein wrote: > * Is there a plan for our registry API to allow submission of new > registry listings? Would you want that API to...

On 2019-01-14 14:34, Mike Ralphson wrote: > @dret : > > my [advice] would be to not tightly couple this with github > > The TSC deliberately took a different...

and my immediate apologies for (once again) responding here, none of this has anything to do with semoasa. this all should be discussed in the OpenAPI context.