We currently have a single RESERVED property (descriptor data) and are probably about to add more (#672), but the spec doesn't explain what the RESERVED keyword means. The current context includes:
The following field keys are reserved and MUST NOT be used by other specifications.
and:
This key is RESERVED for future versions of the specification.
neither of which impact neither JSON authors nor JSON consumers.
So what happens to the JSON handlers? Are JSON authors free to set those properties? Are JSON consumers free to act on those properties as long as they don't specify how they interpret them?
Will making platform.features reserved make the current Docker docs (which are fairly spec-like) non-compliant for breaking the MUST NOT be used by other specifications? Or are they ok because they define a different media type? What happens for backwards-compat?
I think we need to define RESERVED here, and expect there's prior art we can lean on. Does anyone have a good reference off hand? I'll dig around as well and report back if I find anything.
We currently have a single RESERVED property (descriptor
data) and are probably about to add more (#672), but the spec doesn't explain what the RESERVED keyword means. The current context includes:and:
neither of which impact neither JSON authors nor JSON consumers.
So what happens to the JSON handlers? Are JSON authors free to set those properties? Are JSON consumers free to act on those properties as long as they don't specify how they interpret them?
Will making
platform.featuresreserved make the current Docker docs (which are fairly spec-like) non-compliant for breaking theMUST NOT be used by other specifications? Or are they ok because they define a different media type? What happens for backwards-compat?I think we need to define RESERVED here, and expect there's prior art we can lean on. Does anyone have a good reference off hand? I'll dig around as well and report back if I find anything.