Skip to content

Asset Evidence Profiles

Asset Evidence Profiles (AEP) define the information that participants exchange using Open Asset Evidence. They organise evidence by its purpose and asset type, so an implementer can start with one useful profile and combine it with others as a workflow grows.

For a property valuation, start with the Property Valuation Profile. It explains the required semantics; the associated Property Valuation Credential describes the signed statement an issuer produces. A lender then evaluates that statement using its own authority, freshness and acceptance rules.

flowchart TB
  AEP(["Asset Evidence Profiles"])

  AEP --> PCP["C-PP-001<br/>Property Condition Profile"]
  AEP --> PVP["V-PP-001<br/>Property Valuation Profile"]
  AEP -.-> MORE["Other asset profiles<br/>in development"]

  PVP --> PVC["V-PC-001<br/>Property Valuation Credential"]
  PCP --> PCC["C-PC-001<br/>Property Condition Credential"]

  class AEP rwGroup
  class PCP,PVP rwSoft
  class PVC,PCC rwOutline
  class MORE rwMuted
  class PCP,PVP,MORE,PVC,PCC rwEven

  click PVP href "../valuation/property-valuation-profile.html"
  click PVC href "../valuation/property-valuation-credential.html"
  click PCP href "../condition/property-condition-profile.html"
  click PCC href "../condition/property-condition-credential.html"
  click MORE href "../evidence/other-assets/index.html"

The building blocks

A profile defines a coherent set of information and checking rules. A credential specification describes the claims in a signed statement; a credential instance is the actual statement issued about a particular subject. A package brings relevant credentials and references together for a workflow. A presentation is the selected evidence and disclosed claims delivered to a recipient.

Packages compose evidence by reference. They do not merge every issuer's claims into one signature or require every document to be stored in one place. A shared identity and explicit relationships let a verifier check that the documents concern the right asset, loan and transaction.

Choose the evidence you need

  • Asset and lending evidence: identify the asset and connect it to offers, agreements, security and funding records. The Property Evidence Profile is the property entry point; other asset profiles describe additional asset types under development.
  • Valuation: express a value, its basis, date, purpose and the issuer's engagement.
  • Condition: describe observed condition with inspection scope, time and limitations. Condition and valuation are separate families, with asset-specific definitions.

Shared rules, different assets

All families use shared definitions for identifiers, provenance, observations, status and verification. Condition profiles for different assets, for example, share rules about who observed something and when, but use different technical vocabularies for the condition itself.

Policy overlays express jurisdiction, institution and transaction requirements. A folder in this documentation is a way to find a definition, not a requirement to submit every document inside it. A workflow specifies which evidence is mandatory, optional or required only when a particular event occurs.

Exchange only what is needed

Evidence presentation and disclosure separates selection of credentials from selective disclosure of claims within them. SD-JWT VC is the credential binding described here. Recipients still need sufficient evidence to verify relationships and satisfy their policy; withholding a required claim cannot produce a successful complete-package check.

Read and implement a profile

Each technical page identifies its current code, purpose, participants, key information, checking rules and related definitions. Codes such as V-PP-001 are compact document identifiers; the numeric suffix is not a release version. See the identifier reference when selecting a conformance target.

Start with the profile's claims and dependencies, choose the applicable policy, and check its implementation status before building an integration. A conceptual example illustrates the intended contract; it is not evidence that an end-to-end implementation has passed conformance tests.