Dan Hudlow

@DavidBiesack Thanks for the work tracking this down. I ran into it independently in case another test case is useful: https://github.com/stoplightio/spectral/issues/2140

For what it's worth, we use `x-ibm-release-level` with possible values of `experimental`, `beta`, and `preview`. It seems like it would be worth considering whether to combine this kind of annotation...

@brentsimmons Any thought on this? It seems impractical/imprudent to implement JSON Feed without it being explicitly licensed.

@mikekistler > I suppose this clarifies to implementers how they should treat undefined query parameters, but this assumes that the API description is written by someone other than the team...

If possible, I'd like to follow up on https://github.com/OAI/OpenAPI-Specification/issues/3572, but unfortunately I can only join at the bottom of the hour.

There's something strange here: > If there is no canonical unit, the service **should** use a `string` field with [ISO 8601][] duration values, such as `P3Y6M4DT12H30M5S`. The field name **should**...

One could possibly argue that as long as leap seconds are smeared, and as long as durations only interact with ISO 8601 dates (_not_ civil time) then you could accept...

@jskeet thanks for popping in! A few observations that seem to me to make it a little more complex than civil time vs machine time: 1. ISO 8601 / RFC...

@rofrankel wouldn't it also be worthwhile to define a proto type for ISO 8601 durations?

I think there's a case to be made that we should reserve "property" for a subschema of an object schema: a subschema that defines valid members for a conforming object...