deploy: 992696c

404.html

@@ -72,9 +72,6 @@
         <li class="version">
           <a href="/specifications/specifications/1.3/index.html">1.3</a>
         </li>
-        <li class="version">
-          <a href="/specifications/specifications/1.1/index.html">1.1</a>
-        </li>
         <li class="version">
           <a href="/specifications/specifications/1.0/index.html">1.0</a>
         </li>
@@ -110,7 +107,6 @@ <h1 class="page">Page Not Found</h1>
     { name: "specifications", title: "C2PA Specifications", url: "/specifications/specifications/1.4/index.html", prefix: "/specifications/specifications" },
     { name: "specifications", title: "C2PA Specifications", version: "1.4", url: "/specifications/specifications/1.4/index.html", prefix: "/specifications/specifications/1.4" },
     { name: "specifications", title: "specifications", version: "1.3", url: "/specifications/specifications/1.3/index.html", prefix: "/specifications/specifications/1.3" },
-    { name: "specifications", title: "specifications", version: "1.1", url: "/specifications/specifications/1.1/index.html", prefix: "/specifications/specifications/1.1" },
     { name: "specifications", title: "specifications", version: "1.0", url: "/specifications/specifications/1.0/index.html", prefix: "/specifications/specifications/1.0" },
   ].reduce(function (accum, it) {
     var prefix = it.prefix

sitemap.xml

@@ -2,42 +2,42 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.4/attestations/attestation.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.4/decoupled/Decoupled.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.4/index.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.4/specs/C2PA_Specification.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
+</url>
+<url>
+<loc>https://c2pa.org/specifications/specifications/1.4/ux/UX_Recommendations.html</loc>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.3/ai-ml/ai_ml.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.3/explainer/Explainer.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.3/guidance/Guidance.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
-</url>
-<url>
-<loc>https://c2pa.org/specifications/specifications/1.1/ux/UX_Recommendations.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.0/security/Harms_Modelling.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 <url>
 <loc>https://c2pa.org/specifications/specifications/1.0/security/Security_Considerations.html</loc>
-<lastmod>2023-11-26T23:13:19.566Z</lastmod>
+<lastmod>2023-12-22T14:42:18.037Z</lastmod>
 </url>
 </urlset>

specifications/1.0/security/Harms_Modelling.html

@@ -78,9 +78,6 @@
         <li class="version">
           <a href="../../1.3/index.html">1.3</a>
         </li>
-        <li class="version">
-          <a href="../../1.1/index.html">1.1</a>
-        </li>
         <li class="version is-current">
           <a href="../index.html">1.0</a>
         </li>
@@ -102,7 +99,6 @@
   <div class="version-menu">
     <a class="version is-missing" href="../../1.4/index.html">1.4</a>
     <a class="version is-missing" href="../../1.3/index.html">1.3</a>
-    <a class="version is-missing" href="../../1.1/index.html">1.1</a>
     <a class="version is-current" href="Harms_Modelling.html">1.0</a>
   </div>
 </div>
@@ -498,7 +494,7 @@ <h3 id="_general_considerations_for_content_creators"><a class="anchor" href="#_
 <div class="ulist">
 <ul>
 <li>
-<p>Inadvertent disclosure of information: C2PA claim generators may automatically add, or require to add, information to manifests that may be sensitive. Specification-compliant implementations may intentionally or unintentionally hide this feature. <a href="../../1.1/ux/UX_Recommendations.html" class="xref page">User experience guidance</a> has been published alongside the specs to offer a clear acknowledgement of creator consent before a C2PA implementation can begin accumulating data.</p>
+<p>Inadvertent disclosure of information: C2PA claim generators may automatically add, or require to add, information to manifests that may be sensitive. Specification-compliant implementations may intentionally or unintentionally hide this feature. <a href="../../1.4/ux/UX_Recommendations.html" class="xref page">User experience guidance</a> has been published alongside the specs to offer a clear acknowledgement of creator consent before a C2PA implementation can begin accumulating data.</p>
 </li>
 <li>
 <p>Redacted (deleted) information from C2PA manifests may still be accessible: If a soft binding lookup is enabled or required by manifest stores, then previous versions of a manifest with sensitive information may be located.</p>
@@ -532,7 +528,7 @@ <h3 id="_general_considerations_for_content_consumers_manifest_consumers"><a cla
 <p>An invalid C2PA manifest could mean that either the digital content or the manifest has been tampered with, though this may not always be the case.</p>
 </li>
 <li>
-<p>The <a href="../../1.1/ux/UX_Recommendations.html" class="xref page">User Experience Guidance</a> is being designed to define best practices for presenting C2PA provenance to consumers. The recommendations strive to describe standard, readily recognizable experiences that provide asset consumers information and history about the content they are consuming, thereby empowering them to understand where it came from and decide how much to trust it.</p>
+<p>The <a href="../../1.4/ux/UX_Recommendations.html" class="xref page">User Experience Guidance</a> is being designed to define best practices for presenting C2PA provenance to consumers. The recommendations strive to describe standard, readily recognizable experiences that provide asset consumers information and history about the content they are consuming, thereby empowering them to understand where it came from and decide how much to trust it.</p>
 </li>
 <li>
 <p>If a content consumer trusts a particular signer, then they may be inclined to believe that the information provided in the manifest is authentic. In other words, a preexisting relationship of trust between a signer and a content consumer is the basis of the C2PA trust model. C2PA specifications are designed to provide signals for content consumers to know that the signer is in fact who they say they are and that the manifest is in fact connected to a particular asset.</p>

specifications/1.0/security/Security_Considerations.html

@@ -78,9 +78,6 @@
         <li class="version">
           <a href="../../1.3/index.html">1.3</a>
         </li>
-        <li class="version">
-          <a href="../../1.1/index.html">1.1</a>
-        </li>
         <li class="version is-current">
           <a href="../index.html">1.0</a>
         </li>
@@ -102,7 +99,6 @@
   <div class="version-menu">
     <a class="version is-missing" href="../../1.4/index.html">1.4</a>
     <a class="version is-missing" href="../../1.3/index.html">1.3</a>
-    <a class="version is-missing" href="../../1.1/index.html">1.1</a>
     <a class="version is-current" href="Security_Considerations.html">1.0</a>
   </div>
 </div>
@@ -674,7 +670,7 @@ <h6 id="_impact_analysis_2"><a class="anchor" href="#_impact_analysis_2"></a>4.2
 <div class="sect5">
 <h6 id="_security_guidance_2"><a class="anchor" href="#_security_guidance_2"></a>4.2.1.2.4. Security guidance</h6>
 <div class="paragraph">
-<p>The impact of this threat scenario is mitigated through explicit detection of missing metadata through the standard C2PA validation process and factoring this into system behaviour. For example, a user agent would display the affected asset differently than a non-modified asset.  (For more information about the user experience aspects, see <a href="../../1.1/ux/UX_Recommendations.html" class="xref page">C2PA&#8217;s UX Guidance</a>)</p>
+<p>The impact of this threat scenario is mitigated through explicit detection of missing metadata through the standard C2PA validation process and factoring this into system behaviour. For example, a user agent would display the affected asset differently than a non-modified asset.  (For more information about the user experience aspects, see <a href="../../1.4/ux/UX_Recommendations.html" class="xref page">C2PA&#8217;s UX Guidance</a>)</p>
 </div>
 <div class="paragraph">
 <p>The impact of this threat scenario could be also mitigated through use of manifest repositories, e.g., by making decoupled C2PA Manifests available to user agents when embedded metadata is missing.</p>
@@ -716,7 +712,7 @@ <h6 id="_impact_analysis_3"><a class="anchor" href="#_impact_analysis_3"></a>4.2
 <div class="sect5">
 <h6 id="_security_guidance_3"><a class="anchor" href="#_security_guidance_3"></a>4.2.2.1.4. Security guidance</h6>
 <div class="paragraph">
-<p>The impact of this threat scenario could be mitigated through explicit detection of incorrect metadata as described here, and factoring this into system behaviour.  For example, a user agent would display the affected asset differently than a non-modified asset.  (For more information about the user experience aspects, see <a href="../../1.1/ux/UX_Recommendations.html" class="xref page">C2PA&#8217;s UX Guidance</a>).</p>
+<p>The impact of this threat scenario could be mitigated through explicit detection of incorrect metadata as described here, and factoring this into system behaviour.  For example, a user agent would display the affected asset differently than a non-modified asset.  (For more information about the user experience aspects, see <a href="../../1.4/ux/UX_Recommendations.html" class="xref page">C2PA&#8217;s UX Guidance</a>).</p>
 </div>
 <div class="paragraph">
 <p>The impact of this threat scenario could be also mitigated through use of manifest repositories, e.g., by making decoupled C2PA Manifests available to user agents when embedded metadata is missing.</p>