Overview
A service sends content for review. The recipient can submit feedback or record approval of the revision they received. Editing the draft and sending or publishing it remain separate service operations.
Read the Content Review definition →
Operations
Target: Service-owned content identified by its exact revision.
- Request changes
- Record feedback on the identified revision.
- Approve
- Record approval of that revision.
Inputs and results
Inputs. The target revision and, for a change request, review feedback.
Results. Feedback recorded or approval recorded, with the revision identified. Requests without permission or against stale revisions leave the current review decision unchanged.
Permissions. The service checks the caller’s review permission. Editing and any later sending or publication require their own permissions.
Human participation. A review page showing the same content and revision.
The behaviour is described here. A machine-readable representation has not yet been selected.
Review a campaign draft
- The service emails a review request for revision 3 of a campaign.
- A reviewer asks for a timezone to be added to the opening paragraph.
- The service records the feedback. An editor prepares revision 4.
- The reviewer approves revision 4 and the service records that decision.
An approval request for revision 3 is refused once that revision is stale. Approval of revision 4 does not send the campaign.
Existing standards
- Schema.org Actions
Candidate vocabulary for describing available operations and their routes.
- Schema.org ReviewAction
Describes an opinion about an object. It is not equivalent to the revision approval in Content Review.
Versions and open questions
0.1 · Working draft
The MAP draft describes review feedback and revision approval. The browser example illustrates the exchange.
- Wire representation and operation identifiers.
- Revision references and retry behaviour.
Contribute to this definition →
Implementations
No implementation evidence has been published for this version.
Support declarations and test reports are supplied by their contributors. Listing them does not certify compatibility. Each targets a type version, execution profile and exact record.