Jason Shao

I'd also like to upvote this. We have a number of use cases where our data-model is multi-valued, and it would be nice to represent each value as a tag....

I often use tags to group operations on entities (because I'm neurotic about doing batch operations on aggregate roots, and individual operations with a {id} path param) and think this...

any further thoughts on this? for *my* purposes, #88 is an approach I could also use to manage this case

I suspect I'd ask for a little more flexibility - in many respects I want to publish different documentation sets for different audiences - and in my head this is...

@marbemac curious where on the priority queue this kind of filtering is landing - or if there are any interim workarounds? For context - we currently treat one of our...

This would save a lot of editing complexity for my teams - much of the proliferation of model variations and inheritance is to allow for "system assigned" fields like `id`,...

Note: in particular in this use-case - it would be nice to simplify importing of JSON schemas that already exist - and so already have '#/definitions' references - similar to...

Wondering if this is still in the works

This behavior has become increasingly problematic for projects with multiple people trying to edit specs (esp. when doing bug squash / tech editing) to the point where we have started...

Left some comments in the field-breakout Google sheet - mostly around stats and whether we can align more closely with terms used either in OpenRTB or AdCOM - esp. terms...