Better mention format support

Signed-off-by: Juan Cruz Viotti <jv@jviotti.com>

Author: jviotti

content/_index.html

@@ -301,6 +301,16 @@ <h3 class="display-6 fw-bold mb-3">How We Compare</h3>
             <td class="text-center bg-success-subtle border-start border-end border-3 border-primary"><i class="bi bi-check-lg text-success"></i><br><small class="text-muted">all dialects through 2020-12, via <a href="https://github.com/sourcemeta/blaze">Blaze</a></small></td>
           </tr>
 
+          <tr>
+            <td class="fw-semibold">Standards-compliant <code>format</code> validation across dialects</td>
+            <td class="text-center bg-danger bg-opacity-10"><i class="bi bi-x-lg text-danger"></i><br><small class="text-muted"><a href="https://github.com/everit-org/json-schema">Everit</a> asserts <code>format</code> by default for Draft 4/6/7 instead of treating it as annotation per spec, with <a href="https://github.com/confluentinc/schema-registry/issues/3877">no opt-in exposed</a></small></td>
+            <td class="text-center bg-danger bg-opacity-10"><i class="bi bi-x-lg text-danger"></i><br><small class="text-muted"><a href="https://github.com/everit-org/json-schema">Everit</a> asserts <code>format</code> by default for Draft 4/6/7 instead of treating it as annotation per spec, with no opt-in exposed</small></td>
+            <td class="text-center bg-danger bg-opacity-10"><i class="bi bi-x-lg text-danger"></i><br><small class="text-muted"><a href="https://github.com/networknt/json-schema-validator">networknt</a> asserts <code>format</code> by default for Draft 4 to 7 instead of annotation per spec, and 2020-12 schemas <a href="https://github.com/Apicurio/apicurio-registry/blob/main/serdes/generic/serde-common-jsonschema/src/main/java/io/apicurio/registry/serde/jsonschema/JsonSchemaValidationUtil.java">force-cast to Draft 7</a> ignoring the <a href="https://www.learnjsonschema.com/2020-12/format-assertion/format/">Format Assertion</a> vocabulary</small></td>
+            <td class="text-center">—<br><small class="text-muted">static catalog, not a validator</small></td>
+            <td class="text-center bg-danger bg-opacity-10"><i class="bi bi-x-lg text-danger"></i><br><small class="text-muted"><a href="https://github.com/networknt/json-schema-validator">networknt</a> asserts <code>format</code> by default for Draft 4 instead of treating it as annotation per spec, with no opt-in exposed</small></td>
+            <td class="text-center bg-success-subtle border-start border-end border-3 border-primary"><i class="bi bi-check-lg text-success"></i><br><small class="text-muted">annotation by default with optional assertion opt-in for Draft 3 through 2019-09, and honors the <a href="https://www.learnjsonschema.com/2020-12/format-assertion/format/">Format Assertion</a> vocabulary on 2020-12</small></td>
+          </tr>
+
           <tr>
             <td class="fw-semibold">Full Model Context Protocol (MCP) support</td>
             <td class="text-center bg-danger bg-opacity-10"><i class="bi bi-x-lg text-danger"></i><br><small class="text-muted">Schema Registry exposed via only <a href="https://docs.confluent.io/cloud/current/ai/ai-tools/managed-mcp-server.html">two read-only Cloud MCP tools</a>, schemas not exposed as MCP resources</small></td>
@@ -470,7 +480,7 @@ <h4 class="h3 my-0 fw-bold">Free</h4>
           </div>
           <div class="card-body d-flex flex-column p-3 p-md-4">
             <ul class="list-unstyled mt-3 mb-4 flex-grow-1">
-              <li class="mb-3"><i class="bi bi-check-circle-fill text-success me-2"></i>Draft 3, 4, 6, 7, 2019-09 and 2020-12 support</li>
+              <li class="mb-3"><i class="bi bi-check-circle-fill text-success me-2"></i>Draft 3, 4, 6, 7, 2019-09 and 2020-12 support, with standards-compliant opt-in <code class="text-body">format</code> validation</li>
               <li class="mb-3"><i class="bi bi-check-circle-fill text-success me-2"></i>Custom meta-schema support <i class="bi bi-info-circle text-muted" data-bs-toggle="tooltip" data-bs-title="The registry rejects any schema that does not validate against its meta-schema, whether official or custom. No invalid schemas make it in"></i></li>
               <li class="mb-3"><i class="bi bi-check-circle-fill text-success me-2"></i>Flexible directory structure <i class="bi bi-info-circle text-muted" data-bs-toggle="tooltip" data-bs-title="Organize schemas by team, department, domain, or any hierarchy that fits your organisation. Most alternatives force a flat or rigid structure"></i></li>
               <li class="mb-3"><i class="bi bi-check-circle-fill text-success me-2"></i><a href="https://one.sourcemeta.com/api/">Full HTTP API access</a></li>