---
# System prepended metadata

title: Untitled

---

Hi everyone,

Per some [recent discussions](https://forum.solidproject.org/t/updates-on-spec-related-activities-in-the-forum/3107), we're trying to do a better job relaying information about active work in flight. Here's an update on what we've been up to in the [Interoperability Panel](https://github.com/solid/data-interoperability-panel) in June. 

As a bit of background - it may be helpful to check out [this forum post](https://forum.solidproject.org/t/problems-and-goals-for-interoperability/3184/3) to understand the problems we're aiming to solve through our work.

In pursuit of solving those problems, we've needed to spend a bit of time on intersecting portions of the core protocol specification like [auxiliary resources](https://github.com/solid/specification/pull/156), and also work on some new things like [shape trees](https://github.com/shapetrees).

From the [Shape Trees Primer](https://shapetrees.github.io/specification/primer):

> A shape tree defines a prospective tree of related resources which can be read and written by applications. The shape tree associates each of these resources with a shape. This allows one to treat a set of related resources as a single grouping, and apply that to a range of operations including access control, data organization, data validation, and data migration. Since the shape tree boundaries that establish these groupings are easily understood by humans, it allows them to perform these operations intuitively.

All of this ultimately leads to our main focus - a _very much still in progress_ draft proposal for how to power an interoperable ecosystem of applications and data, which we're making substantial progress on daily.

Keep in mind that this material is pretty technical in nature. It's meant for the developers who are making the tools and libraries that the majority of the developer population will use. It's also a draft that's partially complete, so it's missing some of the glue and polish that will make it more readable and digestible.

A lot of work so far has gone towards iterating on the fundamentals, like establishing our reference use case, data model, shapes, shape trees, and patterns for incorporating all of that into practical mechanisms. We [recently published](https://github.com/solid/data-interoperability-panel/pull/54) a draft iteration of Application Registration, which is the first section of several to pull all of those fundamentals together.

While we iterate on feedback and continue to tune Application Registration, we're heads down on Data Registration and Data Authorization, which are arguably the most important sections in the proposal. We anticipate substantial submissions for these to start rolling in by the end of next week :slightly_smiling_face: 

Here are some links to the draft if you'd like to follow our progress... or even better - [join in and contribute](https://github.com/solid/data-interoperability-panel#meetings)!

- [Rendered Editor's Draft](https://solid.github.io/data-interoperability-panel/ecosystem/)
- [Source](https://github.com/solid/data-interoperability-panel/tree/master/proposals/ecosystem) _using [Bikeshed](https://github.com/tabatkins/bikeshed) spec preprocessor templates_

Feel free to raise issues, make pull requests, make forum topics, or ping us in gitter with any thoughts, concerns, questions, or ideas!

Thanks!