# Live shared Pod Data – making it happen

**URL:** <https://forum.solidproject.org/t/live-shared-pod-data-making-it-happen/4061>\
**Category:** Connection to Other Initiatives\
**Created:** [March 5, 2021, 4:53pm UTC](https://forum.solidproject.org/t/live-shared-pod-data-making-it-happen/4061 "2021-03-05T16:53:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gsvarovsky](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/gsvarovsky/32/1973_2.png) [@gsvarovsky](https://forum.solidproject.org/u/gsvarovsky)\
**Post date:** [March 10, 2021, 10:46am UTC](https://forum.solidproject.org/t/live-shared-pod-data-making-it-happen/4061/4 "2021-03-10T10:46:47Z")

</div>

Thanks to Sarven Capadisli’s prompt on solid/chat, I have scraped more of the Solid community for motivation and prior work on this area. I’m sure the references below are not yet comprehensive, but it’s a start.

# Opinion

Support for live collaborative editing of Pod data in the corpus of documented use-cases and requirements is found only in allusion, and not called out as motivating for the Solid specification. However, engineers have made calls for patch-passing data distribution mechanisms, for strong reasons which do include enablement of user features. This is a disconnect.

There is an accelerating trend towards remote collaboration in software, including live collaborative editing becoming table stakes for many kinds of user content; as well as version control with branching and merging, for others. I think engineers are aware of this, but it’s hard to capture feature requirements for new applications that users don’t have in front of them yet. This is especially a problem when other motivations for patch-passing are to do with performance and resilience, things that are only perceived by the user when they’re broken.

# Data

## solid/user-stories

[As a developer, I want to be able to subscribe to a stream of pod events #22](https://github.com/solid/user-stories/issues/22) – Open

- “Event-driven architectures are very powerful in that they allow to create loosely coupled reactive systems.”
- This is marginal as a _user_ story, but refers to other feature requests:
  - As a user I want to be able to have an audit log of what happened to my data #12
  - As a user I want to be able to restore previous data #10

## solid/specification

[Standardizing state changes in resources (history, undo, sync) #161](https://github.com/solid/specification/issues/161) – Open

- Ruben V: “but then we should probably have collaborative editing as an issue/use case”

[Act on the latest version of the resource state #91](https://github.com/solid/specification/issues/91) – Open

- “This discussion is re-discovering wiki edit conflicts, and source code change management, and ACID-style databasing, among other things.”

[What server-based notification support is required? #49](https://github.com/solid/specification/issues/49) – Open

## solid/data-interoperability-panel

[Problems and Goals for Interoperability, Collaboration, and Security in a Solid Pod](https://github.com/solid/data-interoperability-panel/blob/master/problems-and-goals.md)

- “data will be manipulated not only by different applications, but also by different people or automated agents.”
- Does not mention live or realtime manipulations

## w3

Collaboration cases in [pwp-ucr](https://www.w3.org/TR/pwp-ucr/), but live collaboration is not specified:

- [UC 72](https://www.w3.org/TR/pwp-ucr/#uc_pwp_single_unit): “Andreas is working on his first collaborative research paper with a fellow student.”
- [UC 20](https://www.w3.org/TR/pwp-ucr/#uc_identify-const-resources_sections): “Tanya and Kelly are collaborating on curriculum for the upcoming school year.”

Annotation cases for ‘live’ data in [dpub-annotation-uc](https://www.w3.org/TR/dpub-annotation-uc/):

- [2.3.5 Recording State of Changing, Online Resources](https://www.w3.org/TR/dpub-annotation-uc/#recording-state-of-changing-online-resources) (focuses on representation change)
- Further allusions in the following cases

Open Data collaboration in [dwbp-ucr](https://www.w3.org/TR/dwbp-ucr/):

- [2.23 UK Open Research Data Forum](https://www.w3.org/TR/dwbp-ucr/#UC-UKOpenResearchForum): “data sharing and collaboration are encouraged, facilitated and rewarded.”
- Also [Dutch National Centre of Expertise and Repository for Research Data](https://dans.knaw.nl/en/): ‘In opposition to “frozen” data sets, linked data can be qualified as “live” data’

[Socialwg/Social API/User stories - W3C Wiki](https://www.w3.org/wiki/Socialwg/Social_API/User_stories)

- [2.70 Fork from and Request Merge of Remote Content](https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Fork_from_and_Request_Merge_of_Remote_Content): this is Git-style branch/merge.

---

_[View the full topic](https://forum.solidproject.org/t/live-shared-pod-data-making-it-happen/4061)._
