Schema registry's "format" attribute

duglin commented 2 months ago

Today "format" is a required attribute on the Schema Resource. I'd like to make it optional for 2 reasons:

the doc uploaded may not actually adhere to any formal schema format, it could just be pseudo schema, or an outline. It's not our job to really care what format it is - until we add schema validation, which I'll open up another issue about. So, forcing them to put a value that could just be gibberish is silly.
when creating a new schema people may want to do a PUT w/o any xRegistry headers. In order to set the "format" field (and have the schema be the HTTP body) they would need to know about and set the xRegistry-format header. Possible in most cases I assume, but it is a burden that some people may not want to deal with unless they really do want to set "format"

duglin commented 2 months ago

Proposal:

make "format" in Schema spec optional on Resource
make it clear in the spec that many spec defined attributes can have their constraints modified. So, it's valid for an impl to make "format" required if they wish but they MUST say so in the model

duglin commented 1 month ago

Agreed on 9/13

xregistry / spec