Ted Epstein
Ted Epstein
The draft [registry](http://spec.openapis.org/registry/) is built with [Jekyll collections](https://jekyllrb.com/docs/collections/). Each item in the collection, representing a registry entry, is a markdown file containing machine-readable properties in [YAML front matter](https://jekyllrb.com/docs/front-matter/), followed by...
Semoasa == Specification Extension Metadata for OAS **Annotations**
I think the title case is a little easier on the eye, easier on the fingers, and makes the acronym seem a bit less forced.
The current spec uses a namespace and a property name to establish unique identity. So the fully qualified name of an extension property would be `namespace.property`. In the [readme example](https://github.com/RepreZen/SEMOASA/blob/master/README.md#user-content-examples),...
I have so far resisted using `namespaces` to group the Namespace Objects. Since namespace properties use reverse-DNS notation, the SEMOASA schema (when we get around to creating it) can use...
The spec says that extension property schemas should be OpenAPI [Schema Objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-schemaObject). At first blush, this seems consistent with this stated design goal: > **Common Technology Stack with OpenAPI**, so...
Right now, the [structure](https://github.com/RepreZen/SEMOASA/blob/master/README.md#user-content-structure) section in the README serves as a placeholder for a specification. Once this starts to settle, I would want to write that formal spec. We might...
I'm reading about [Server Objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#server-object) and [Server Variables](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#server-variable-object), and trying to understand how resolution/expansion is supposed to work. The OpenAPI document can specify any number of servers, each with zero...