Skip to content

c2pa-soft-binding-resolution #96

Description

@mrappard

This is a placeholder issue while we are discussing this in C2PA. Please review.


  • You have read and understood the requirements for registration (https://tools.ietf.org/html/rfc8615#section-3.1).

  • You have checked the registry (https://www.iana.org/assignments/well-known-uris/) and found no current value that meets your needs.

  • Your specification reference URL is stable; ideally, managed by a widely-recognised standards development organisation (e.g., published as an RFC). Otherwise, please give additional information.

  • URI suffix: c2pa-soft-binding-resolution

  • Change controller: C2PA (Coalition for Content Provenance and Authenticity) — https://c2pa.org

  • Specification document(s): C2PA Soft Binding Resolution API Specification, §Soft Binding Resolution API —
    https://c2pa.org/specifications

Additional information:

The c2pa-soft-binding-resolution well-known URI is defined by the C2PA (Coalition for Content Provenance and Authenticity), a Joint Development Foundation project whose members include Adobe, BBC, Google, Microsoft, Sony, and others. C2PA develops open technical specifications for content provenance and authenticity.

This well-known URI is used for service discovery of a C2PA Soft Binding Resolution API endpoint. A soft binding (such as an invisible watermark or content fingerprint) is a mechanism for recovering a C2PA provenance manifest when it has become decoupled from the asset it describes. The well-known URI allows clients to locate the API endpoint for a given host without prior out-of-band configuration. A GET request to the well-known URI returns a JSON document containing the API base endpoint, API version, and links to the service's status and capabilities endpoints.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions