From 7392b1a740065512f2fed2415f2374431689b99b Mon Sep 17 00:00:00 2001 From: Fabian Steeg Date: Tue, 10 Sep 2024 12:22:52 +0200 Subject: [PATCH 1/2] Specify defaults for `required` and `matchQuantifier` (#155) In a reconciliation query's condition object --- draft/index.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft/index.html b/draft/index.html index 26fb207..ddbea16 100644 --- a/draft/index.html +++ b/draft/index.html @@ -523,18 +523,18 @@

Structure of a Reconciliation Query

is defined are determined by the service.
required
An optional boolean indicating if a match for the property is required for an entity to enter the list of candidates (i.e. acting like a filter or a WHERE clause in SQL) - or optional (i.e. only effecting the entity's rank in the list of candidates);
+ or optional (i.e. only effecting the entity's rank in the list of candidates). If omitted, the service SHOULD assume the requested value to be false;
matchQuantifier
-
An optional string to indicate which of the values in v to match. MUST be any (equivalent to boolean OR), all (equivalent to boolean AND), or none (equivalent to boolean NOT);
+
An optional string to indicate which of the values in v to match. MUST be any (equivalent to boolean OR), all (equivalent to boolean AND), or none (equivalent to boolean NOT). If omitted, the service SHOULD assume the requested value to be any;
matchQualifier
An optional 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 matchQualifier MUST return the supported matchQualifiers for each property - in their property suggest responses.

+ in their property suggest responses. If omitted, the exact matching behavior is up to the service.

- A reconciliation service that supports property assignments SHOULD provide a suggest service for discovering these properties. If the optional fields are omitted, the exact behavior ("must match all", "should match some", etc.) is up to the service. + A reconciliation service that supports property assignments SHOULD provide a suggest service for discovering these properties.

A reconciliation query batch is an array of reconciliation queries. From 94956780e3082b8130b61212830a3e372f148699 Mon Sep 17 00:00:00 2001 From: Fabian Steeg Date: Wed, 11 Sep 2024 09:44:57 +0200 Subject: [PATCH 2/2] Update draft/index.html Co-authored-by: Thad Guidry --- draft/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft/index.html b/draft/index.html index ddbea16..521a0e4 100644 --- a/draft/index.html +++ b/draft/index.html @@ -531,7 +531,7 @@

Structure of a Reconciliation Query

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 matchQualifier MUST return the supported matchQualifiers for each property - in their property suggest responses. If omitted, the exact matching behavior is up to the service.

+ in their property suggest responses. If omitted, the matching behavior is up to the service.

A reconciliation service that supports property assignments SHOULD provide a suggest service for discovering these properties.