Skip to main content

Originator Profile Blueprint

This document is non-normative.

Aiming to document the technical specifications of the Originator Profile

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.

:::note[The old technical specification documents have been archived.] Previous specifications:

:::

note

All of these documents on this site are draft.

note

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 a Verifiable Credential (VC) and how it is distributed. Definitions of terms common throughout this specification are provided in the Glossary.

The OP defines the following specifications as common specifications for VC.

The OP defines the following as organization IDs and uses them in each VC:

The following documents define the data models for the three VCs that play a central role in OP:

  • Core Profile(CP): CP consists of an organization's OP ID and a VC of its public key.
  • Profile Annotation(PA): PA may include proof of the sender's entity identity, information about certificates granted by various certification authorities, and membership certificates from various organizations, each signed by the appropriate entity.
  • Content Attestation(CA): CA contains information about the Web Content created and managed by the CP holder, as well as information about the target content and verification methods, and is signed by the CP holder.

In addition to these, the following VCs are defined:

  • Web Media Profile(WMP): WMP is a VC that describes the information to be displayed to users when using the OP on the Web (such as the sender's policy statement, contact information, etc.) and is signed by the CP holder.
  • Web Site Profile(WSP): WSP is a VC that indicates that the sender owns a website. It is signed by the CP holder.

Profile Annotation(PA), Content Attestation When actually using PA and CA, it is necessary to define specific properties according to the application. The property definitions used in OP-CIP are defined in the following implementer's guide:

The following data formats are defined for distributing these VCs together.

CA has a mechanism to prevent content tampering called Content Integrity Descriptor. The following implementation guide is the specification for it.

The following documents ensure the security of the entire OP framework.

The JSON-LD context used throughout VC is documented in the following document: