Sebastian Wilzbach

@matthewhudson: no it's not resolved. The user is asking for `enum` to behave like `range` (i.e. allowing a custom type).

> Presently, the Storyscript Hub allows developers to submit services with special "meta" data such as; tags, category (w/ our own custom taxonomy), docker tag, service name, and description. Other...

Imho all output should be immutable as the data needs to be serialized and send over the wire. So the service needs to make a "immutable copy" of it anyhow...

Nice idea, but it probably also needs to be able to express more: - port (maybe port-ranges and port shorthands like `http` for `80`) - hostname regex (e.g. (`api*.slack.com`) -...

Note that having a `date` type is also interesting.

> Note that having a date type is also interesting. For the record: - `date`: RFC 3339 timestamp (https://www.ietf.org/rfc/rfc3339.txt) - `time` should probably be called `duration` and be represented as...

> It's intentional. We use it to describe something user defined, such as an action name. A single dollar typically means end of stream. Using it for anything else is...

> How about actions..http? Of course. I prefer that even over `${actionName}`. If we have to use a single symbol, use the established wildcard symbol `actions.*.http` (though this is a...

AFAICT the spec doesn't allow binary data as of now, so I think we first should add this to the spec before. ```yaml actions: my_action: http: contentType: multipart/form-data arguments: my_file:...

My vote goes for YAML as well :+1: