Skip to content

Commit 3b7267b

Browse files
committed
Move section on v2 actions
1 parent 8980dee commit 3b7267b

File tree

1 file changed

+10
-14
lines changed

1 file changed

+10
-14
lines changed

docs/manifest/writing/assertions-actions.md

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -37,20 +37,6 @@ Changes include:
3737
- `SoftwareAgent` is a [ClaimGeneratorInfo](../json-ref/manifest-def.mdx#claimgeneratorinfo) structure instead of a string.
3838
- Ingredients are now V3 ingredients
3939

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-
<a name="question1"></a>
45-
46-
<div class="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-
5440
## C2PA standard assertions
5541

5642
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.
138124
| `parameters` | No | Additional information describing the action; see [Parameters](#parameters) | Reference to ingredients in the `ingredientIds` array. |
139125
| `parameters` | No | Additional information describing the action; see [Parameters](#parameters) | Reference to ingredients in the `ingredientIds` array. |
140126

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+
<div class="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+
141137
### Action names
142138

143139
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

Comments
 (0)