Skip to content

fix language in 2.1 specification #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Brianthered wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix language in 2.1 specification #78

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,4 @@ node_modules/*
package-lock.json
alex-out.txt
links-out.txt
/.vscode
10 changes: 5 additions & 5 deletions build/site/specifications/2.1/specs/C2PA_Specification.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1095,10 +1095,10 @@ <h2 id="_versioning"><a class="anchor" href="#_versioning"></a>5. Versioning</h2
<div class="sect2">
<h3 id="_compatibility"><a class="anchor" href="#_compatibility"></a>5.1. Compatibility</h3>
<div class="paragraph">
<p>As the Content Credentials specification has evolved, constructs such as box labels, assertions (and their fields), claims and time-stamps have also evolved. New assertions have been added, and some existing assertions and the claim have newer versions with additional fields. In addition, some constructs have been deprecated. In this specification, when a construct is marked as deprecated, that means that a claim generator shall not write that construct (or value), but that a validator should read it.</p>
<p>As the Content Credentials specification has evolved, constructs such as box labels, assertions (and their fields), claims and time-stamps have also evolved. New assertions have been added, and some existing assertions and claims have newer versions with additional fields. In addition, some constructs have been deprecated. In this specification, when a construct is marked as deprecated, that means that a claim generator shall not write that construct (or value), but that a validator should read it.</p>
Copy link
Contributor

@lrosenthol lrosenthol Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is only ever a single claim in any C2PA Manifest.

</div>
<div class="paragraph">
<p>To facilitate interoperability between claim generators and validators, a claim generator declares which version of the specification it is using to generate the claim. When a claim generator declares that it is using a version of the specification, it is declaring that the active manifest of the asset is produced in accordance with that version of the specification and thus does not contain any deprecated constructs listed under that version of the specification in <a href="#deprecated_constructs_table">Table 19, &#8220;Deprecated Constructs&#8221;</a> of <a href="#versioning_annex">Appendix C, <em>Considerations for Deprecation</em></a>.</p>
<p>To facilitate interoperability between claim generators and validators, a claim generator declares which version of the specification it is using to generate the claim. When a claim generator declares that it is using a version of the specification, it is declaring that the active manifest of the asset is produced in accordance with that version of the specification and thus does not contain any deprecated constructs listed under that version of the specification in <a href="#deprecated_constructs_table">Table 19, &#8220;Deprecated Constructs&#8221;</a> of <a href="#versioning_annex">Appendix C, <em>Considerations for Deprecation</em></a>.</p>
</div>
<div class="admonitionblock note">
<table>
Expand Down Expand Up @@ -1331,7 +1331,7 @@ <h4 id="_2_1_september_2024"><a class="anchor" href="#_2_1_september_2024"></a>5
<div class="sect3">
<h4 id="_2_0_january_2024"><a class="anchor" href="#_2_0_january_2024"></a>5.2.2. 2.0 - January 2024</h4>
<div class="paragraph">
<p>This version represents a significant departure from previous versions. It reduces the use of the term "actor", which no longer represents humans and organisations. In addition to validator-configured trust lists, it also introduces a new default trust list, the "C2PA Trust List", which is intended to cover certificates issued to hardware and software. This philosophical change led to the following functional changes in the specification:</p>
<p>This version represents a significant departure from previous versions. It reduces the use of the term "actor", which no longer represents humans and organizations. In addition to validator-configured trust lists, it also introduces a new default trust list, the "C2PA Trust List", which is intended to cover certificates issued to hardware and software. This philosophical change led to the following functional changes in the specification:</p>
Copy link
Contributor

@lrosenthol lrosenthol Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use Int'l English (which uses s instead of z on many words) for our standard.

</div>
<div class="ulist">
<ul>
Expand Down Expand Up @@ -5044,10 +5044,10 @@ <h4 id="_decompression"><a class="anchor" href="#_decompression"></a>15.5.4. Dec
<div class="sect3">
<h4 id="_validating_a_match"><a class="anchor" href="#_validating_a_match"></a>15.5.5. Validating a Match</h4>
<div class="paragraph">
<p>A validator may wish to validate that the located C2PA Manifest Store is indeed the one associated with asset.</p>
<p>A validator may wish to validate that the located C2PA Manifest Store is indeed the one associated with the asset.</p>
</div>
<div class="paragraph">
<p>If the C2PA Manifest Store was located then the hard binding assertion present in its active manifest shall be used to validate that it is the matching manifest and whether the asset has been modified without manifest updates. If the hard binding does not match, it is unknown if that is because of (a) modification of the asset or (b) the wrong C2PA Manifest Store was located. Accordingly, the validator shall treat this as a non-matching hard binding and reject the manifest with a failure code of <code>assertion.dataHash.mismatch</code> if a data hash assertion is used, <code>assertion.boxesHash.mismatch</code> if a general boxes hash assertion is used, <code>assertion.collectionHash.mismatch</code> if a collection data hash assertion is used, or <code>assertion.bmffHash.mismatch</code> if a BMFF hash assertion is used.</p>
<p>If the C2PA Manifest Store was located, the hard binding assertion present in its active manifest shall be used to validate that the C2PA Manifest Store is the matching manifest. Additionally, the validator will check whether the asset has been modified without manifest updates. If the hard binding does not match, it is unknown if that is because of (a) modification of the asset or (b) the wrong C2PA Manifest Store was located. Accordingly, the validator shall treat this as a non-matching hard binding and reject the manifest with a failure code of <code>assertion.dataHash.mismatch</code> if a data hash assertion is used, <code>assertion.boxesHash.mismatch</code> if a general boxes hash assertion is used, <code>assertion.collectionHash.mismatch</code> if a collection data hash assertion is used, or <code>assertion.bmffHash.mismatch</code> if a BMFF hash assertion is used.</p>
Copy link
Contributor

@lrosenthol lrosenthol Oct 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This proposed change is not technically correct.

</div>
</div>
</div>
Expand Down