Originator Profile Blueprint
This document is non-normative.
Aiming to document the technical specifications of the Originator Profile (OP)
These documents on this site describe the technical aspects of Originator Profile. Originator Profile technology does not provide a value judgment of the correctness, falsity, or inaccuracy of any particular piece of content, but aims to provide a cryptographically verifiable means by which anyone can assess its trustworthiness.
The old technical specification documents have been archived.
Previous specifications:
All of these documents on this site are draft.
Our technical specification documents, previously known as "Originator Profile RFC (OP RFC)", have been renamed to "Originator Profile Blueprint (OPB)". This new title emphasizes our independent management of these documents, from standadization process of IETF or W3C.
Overview of Originator Profile
The OP specification defines Verifiable Credentials (VCs) and how it is distributed. Definitions of terms common throughout this specification are provided in the Terminology.
The OP defines the following specifications as common specifications for VCs.
- OP VC Data Model: VC-compliant data model defined in OP
- Securing Mechanism: Securing Mechanism of VCs as defined in OP
This document defines a data model for VCs to indicate keys that can verify an organization is the originator.
This document defines a data model for VCs to assert additional information about the originator, where that information has been validated by an appropriate entity.
The following documents define a data model for PA corresponding to various use cases.
- Certificate Data Model: The Certificate PA Data Model
- Organization Existence Certificate: Data model for organization existence certificate.
- Advertising Certification Certificate: Data model for advertising certification certificate.
- News Media Registration Certificate: Data model for news media registration certificate.
- Municipality Certification Certificate: Data model for municipality certification certificate.
This document defines a data model for VCs to indicate the content originated by the originator.
- Content Attestation (CA)
- Allowed URL: Verifies that the CA is placed on a website with a valid URL
The following documents define a data model for CA corresponding to various use cases.
- Article Data Model: CA data model linked to articles on the Internet.
- Online Ad Data Model: CA data model linked to Online advertising.
- Advertorial: CA data model linked to advertorials on the Internet.
Furthermore, the following documents define the specification for the Content Integrity Descriptor, which is a mechanism to prevent tampering with the content indicated by the CA.
- Content Integrity Type Registry: Registry server for Content Integrity Descriptor
- HTML Target: Verifies the integrity of the target DOM element as an HTML string.
- Text Target: Verifies the integrity of the text content of the target DOM element
- Visible Text Target: Verifies the integrity of the rendered text of the target element
- External Resource Target: Verifies the integrity of external resources.
This document defines a data model for VCs to assert the name and other identifiers that the originator claims as a web publisher.
This document defines a data model for VCs to indicate the website operated by the originator.
- Web Site Profile (WSP)
- Allowed Origin: Verifies that the WSP is placed on a website of a legitimate origin
The following data formats are defined for the collective distribution of the VCs as defined by the OP.
- Originator Profile Set（OPS): OPS is a distribution format for CP, PA, and WMP.
- Content Attestation Set(CAS): CAS is the distribution format of CA.
- Site Profile(SP): SP is the distribution format of WSP
- Linking: This is how to link CAS and OPS to HTML pages.
The OP defines the following as organization IDs and uses them in each VC:
- Originator Profile Identifier (OP ID): Organization IDs
- DNS URI OP ID: OP ID using a domain name
The JSON-LD context used throughout VCs is documented in the following document:
The following documents ensure the security of the entire OP framework.
- Cryptographic algorithm: The cryptographic algorithm recommended by the OP
Model Classification
Please refer to the data models belonging to the model defined in the Architectural Overview via the following link.