Skip to content

Remove recommendation to use fully-qualified property names as queryables #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased] - TBD

### Changed

- Remove recommendation to use fully-qualified property names as queryables.

## [v1.0.0-rc.3] - 2023-10-18

### Added
Expand Down
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,9 @@
- [Example 14: Using the ACCENTI Accent-insensitive Comparison Function](#example-14-using-the-accenti-accent-insensitive-comparison-function)
- [Example 14: cql2-text (GET)](#example-14-cql2-text-get)
- [Example 14: cql2-json (POST)](#example-14-cql2-json-post)
- [Example 15: Using the IN List predicate](#example-15-using-the-in-list-predicate)
- [Example 15: cql2-text (GET)](#example-15-cql2-text-get)
- [Example 15: cql2-json (POST)](#example-15-cql2-json-post)

## Overview

Expand Down Expand Up @@ -278,7 +281,7 @@ returned according to OAFeat Part 3. It is recognized that this is a severe rest
and dynamic content, so this behavior may be modified by setting the `additionalProperties` attribute in the
queryables definition to `true`. As such, any syntactically-valid term for a property will be accepted, and the
matching semantics are such that, if an Item does not have an attribute by that name, the value is assumed to be
`null`. It is recommended to use fully-qualified property names (e.g., `properties.eo:cloud_cover`).
`null`.

Queryables are advertised via a JSON Schema document retrieved from the `/queryables` endpoint. This endpoint at the root
retrieves queryables that apply to all collections. When used as a subresource of the collection resource
Expand Down