You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Collection validation accepts invalid renders as long as one render is valid #38
In Collections, the schema accepts a renders object as long as at least one of its renders is valid, so every render but one can be invalid, yet still pass validation.
For example, the following Collection passes the render schema's validation (v2.1.0 here, and v1.0.0 behaves the same), but shouldn't because its invalid render assigns bidx an integer instead of an array:
Remove the valid render, and the Collection fails validation, as expected.
The schema's oneOf alternative for Collections wraps the render check in a double negation, which reads as "not every render fails", i.e., at least one passes:
The Collection rule, $comment included, matches the one the extension template used for Collection assets from stac-extensions/template@c0f506b until stac-extensions/template#36 replaced it. For assets, "at least one" made sense, because not every asset has to use an extension. Every entry in renders is a render object, though.
Suggested fix: Use the Items alternative's renders rule for Collections too.
Activity
chuckwondo commentedon Nov 10, 2026
@emmanuelmathot, @vincentsarago, or @m-mohr, any thoughts on this one?