From 1812f84d7f34a8342c0b7f2899ef032bcad6601a Mon Sep 17 00:00:00 2001 From: Fabian Steeg Date: Mon, 18 Dec 2023 12:59:18 +0100 Subject: [PATCH] Update `match_qualifier` requirements as discussed in #131 Supported match qualifiers MUST be included in property suggestions, see https://github.com/reconciliation-api/specs/pull/131#discussion_r1426740869 --- draft/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft/index.html b/draft/index.html index 4bf51ec..d94a8f7 100644 --- a/draft/index.html +++ b/draft/index.html @@ -512,7 +512,7 @@

Structure of a Reconciliation Query

A string to indicate how to match the values in v. This can be used for general matching relations like "skos:exactMatch", "skos:closeMatch", etc. or for specific features like spatial matching with geo data (e.g. containment search with "schema:containsPlace" etc.) or custom matching on date fields (e.g. services supporting the [[EDTF]] specification could use "EDTF:Level-0" etc. - To allow discovery of supported qualifiers by clients, services that support match_qualifier SHOULD return the supported match_qualifiers for each property + To allow discovery of supported qualifiers by clients, services that support match_qualifier MUST return the supported match_qualifiers for each property in their property suggest responses.