Mike Ralphson

> still not in there, though, are registration metadata such as who registered (if non-github identity/info should be supported) and when. As above, a GitHub user id will be required,...

@tedepstein That does sound cleaner, I just wasn't sure if you wanted to keep SEMOASA as 'pure' OAS-centric.

Hmm, as the `schema` doesn't vary by `context`, should the `example(s)` ? 👍 for listing documentation as a concrete use-case.

Yes, I was mainly thinking of [generated human-readable documentation](https://mermade.github.io/shins/apisguru.html). :smile: I don't think `title` need be required.

I'd love to say shins could automagically derive such documentation from an arbitrary yaml file, but no, it's just a port of [slate](https://github.com/lord/slate/) to node.js - the 'clever' bit is...

As the markdown might perhaps be being rendered into HTML to make the links useful, do such renderers often provide the ability to specify the base URL?

Have you seen the Android app Hash-It? It's compatible with passhash. Here

Pinging @fmvilas from [AsyncAPI](https://github.com/asyncapi/asyncapi) and @IvanGoncharov from [GraphQL-wg](https://github.com/graphql/graphql-wg) to see if they have input on making this type of document more widely applicable to different kinds of APIs. @kinlane I...

It would be useful to be able to determine whether a change should trigger a major, minor or patch version number change according to semver. A 'semantic OpenAPI version' spec/guidance...

shields.io badges are custom configurable.