You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/manifest/writing/assertions-actions.md
+10-14Lines changed: 10 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,20 +37,6 @@ Changes include:
37
37
-`SoftwareAgent` is a [ClaimGeneratorInfo](../json-ref/manifest-def.mdx#claimgeneratorinfo) structure instead of a string.
38
38
- Ingredients are now V3 ingredients
39
39
40
-
#### V2 actions
41
-
42
-
The [C2PA Technical Specification](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_actions) describes expanded v2 actions. While v1 actions are fully specified in the actions array v2 actions may either be specified by an element of the actions array or from an element in the templates array with the same action name.
43
-
44
-
<aname="question1"></a>
45
-
46
-
<divclass="review-comment">
47
-
The CAI APIs can read all v2 actions and write most v2 actions. What v2 actions can it NOT write?
48
-
</div>
49
-
50
-
V1 actions have a label of `c2pa.actions` v2 actions have a label of `c2pa.actions.v2`. Actions are modelled after XMP ResourceEvents, but with a number of C2PA-specific adjustments.
51
-
52
-
V1 actions are fully specified in its actions array. However, a v2 action may either be fully specified in an element of the actions array or it may be derived from an element in the templates array with the same action name.
53
-
54
40
## C2PA standard assertions
55
41
56
42
The C2PA Technical Specification defines a [set of standard assertions](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_standard_c2pa_assertion_summary) and their corresponding labels. In addition, you can define [custom assertions](#custom-assertions) for your specific application.
@@ -138,6 +124,16 @@ Each object in the `actions` array has the following standard properties.
138
124
|`parameters`| No | Additional information describing the action; see [Parameters](#parameters)| Reference to ingredients in the `ingredientIds` array. |
139
125
|`parameters`| No | Additional information describing the action; see [Parameters](#parameters)| Reference to ingredients in the `ingredientIds` array. |
140
126
127
+
### V2 actions
128
+
129
+
The [C2PA Technical Specification](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_actions) describes expanded v2 actions. V1 actions have a label of `c2pa.actions` v2 actions have a label of `c2pa.actions.v2`. Actions are modelled after XMP ResourceEvents, but with a number of C2PA-specific adjustments.
130
+
131
+
V1 actions are fully specified in the `actions` array. However, a v2 action may either be fully specified in an element of the `actions` array or it may be derived from an element in the `templates` array with the same action name.
132
+
133
+
<divclass="review-comment">
134
+
The CAI APIs can read all v2 actions and write most v2 actions. What v2 actions can it NOT write?
135
+
</div>
136
+
141
137
### Action names
142
138
143
139
The value of the `action` property must be either one of the pre-defined [standard C2PA action strings](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_actions) of the form `c2pa.*` or a custom action name. The set of standard C2PA actions includes fundamental ones as `c2pa.created` for when an asset is first created, and others (`c2pa.cropped`, `c2pa.resized`, and so on) for when an asset's content is modified in some way.
0 commit comments