From 9e182c5aaea93562b63264aeaa2de675d0a39fcf Mon Sep 17 00:00:00 2001
From: Antonin Delpeuch <antonin@delpeuch.eu>
Date: Thu, 11 Jun 2026 16:15:52 +0200
Subject: [PATCH] Remove general statement about various multiple URIs being
 published about entities

This paragraph made sense as an introduction to why reconciliation existed as a task, but now that there are some earlier paragraphs that are more concrete (especially the second one in that section), it seems a bit odd to have that content at that point of the document. I think the motivation will be clear enough without this part.
If we want to keep it, I would rather integrate it to the 1st and 2nd paragraphs of that section.
---
 working_group_charter.html | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/working_group_charter.html b/working_group_charter.html
index 28d1cfe..7dba0ec 100644
--- a/working_group_charter.html
+++ b/working_group_charter.html
@@ -154,9 +154,6 @@ <h2>Motivation</h2>
         <p>
             With a standardized protocol, 1.) a single client implementation can integrate any conforming data service and 2.) a single data service implementation can be used in any conforming client application. So instead of implementing separate Excel add-ins or Grist importers for every data source, we can have a single reconciliation client in Excel or Grist that can talk to any data provider, and instead of implementing separate Wikidata extensions for every application, we can have a single Wikidata reconciliation service that can be used in any client application.
         </p>
-        <p>
-            Because the Web is decentralized, any service can publish a new URI for an entity or concept that already exists elsewhere. As a result, entities have multiple identifiers and varying attributes or descriptions across the web. Linked Open Data seeks to enable the integration of data from different publishers. To accomplish this for a specific entity, it is necessary to determine which URIs refer to the same entity across different services by comparing attributes (e.g. the name, country and mayor of a city), investigating discrepancies, and updating records accordingly.
-        </p>
         <p>
             Providing an API to support this reconciliation process, which includes matching, previewing, suggesting, and extending, is the primary motivation behind this working group. It aims to develop a protocol that 1.) a tool provider can implement, enabling its users to efficiently integrate external data sources, and 2.) a data provider can implement, enabling its consumers to efficiently match their own data to the entities represented by the provider.
         </p>