In May, we convened the Perseus Technical Advisory Group, chaired by Icebreaker One.

Date: 8th May 2025 10:00-11:30 BST

Location: online

Chair: Frank Wales, IB1

Secretariat: IB1

The meeting aims were as follows:

  1. Progress the plan for production release of Trust Framework by end 2025
  2. Review the process of withdrawal of permission
  3. How scheme rules are specified
  4. Discuss on-going shape and cadence of advisory and working groups
  5. Approve progress on 1. and 2. so far

Summary:

  • It was noted that the production release approach was shared with members, with diagrams of the production and pre-production environments discussed 
    • It was noted that the pre-production environment already exists, acting as a  preview of any functionality planned for the  production environment 
    • It was noted that a customer service portal to support users is expected with production
  • It was noted that there was a review of the permission withdrawal process 
    • It was noted that this process applies to withdrawal of permission from the Energy Data Provider notifying the Carbon Accounting Platform, and the CAP notifying the Financial Service Provider 
    • It was noted that there is a permission record per connection between platforms per user 
  • It was noted that the outcome of the Icebreaking process are Scheme Rules, followed by: legal agreements, policies, technical standards, access control, SLAs and licenses 
    • The Registry encodes these all in a single place, thus it was noted that this needs to be machine readable to ensure that automation can be used to increase trust in the ecosystem and operate the Trust Framework scalably. 
  • It was noted that the Registry uses Resource Description Framework (RDF) and files to completely describe the Scheme rules.
    • RDF is a W3C standard for describing graph structures
    • Used by DCAT, the standard for the Trust Framework data catalogue.
    • Formatted text files are used for documents (currently using PDF and Markdown).
    • There are OpenAPI definitions for the Registry’s API.
  • It was noted that members will use the Registry as: 
    • A definitive location for agreements and policies 
    • A list of technical standards that are used, with links to documentation
    • For “User guide” documentation
    • For OpenAPI tools to build for API servers and clients 
  • The Advisory and Working Group structures were discussed with a view to increasing engagement
    • It was agreed that a Slack channel will be created for early idea generation and discussion, to then feed into WGs
      • Note: All AG2 members will be added to the Slack channel using their contact email address. Please advise IB1 Secretariat if you do not wish to be added or if you have an alternate email address to be used.
    • It was noted that a common backlog with names against tasks could be helpful to provide an overview 

Next meeting: July 2025

Formal records are maintained by the secretariat. These are confidential to the Advisory Group Members.