You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-14Lines changed: 16 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
We must be able to support data interoperability across applications while enabling secure collaboration and query using intuitive data boundaries.
8
8
9
-
Diversity in how the same data will be accessed and manipulated by different entities and applications exacerbates the need for reliable mechanisms that protect against data corruption, data leakage, or broken workflows
9
+
Diversity in how the same data will be accessed and manipulated by different entities and applications increases the need for reliable mechanisms that protect against data corruption, data leakage, or broken workflows
10
10
11
11
Standard methods and mechanisms for interoperability, collaboration, and security of data in a Solid Pod must realize these needs, and it must be done without changing the fundamentals of Solid.
12
12
@@ -16,14 +16,15 @@ Read our stated [Problems and Goals](problems-and-goals.md) for an in-depth unde
@@ -47,20 +49,20 @@ Read our stated [Problems and Goals](problems-and-goals.md) for an in-depth unde
47
49
48
50
## Completed Initiatives
49
51
50
-
[Resource Metadata](https://github.com/solid/data-interoperability-panel/tree/master/archive/resource-metadata)- Resource Metadata was [submitted](solid/specification#156) as a candidate proposal to the solid/specification. It was renamed to Auxiliary Resources during Editorial Review.
52
+
[Resource Metadata](https://github.com/solid/data-interoperability-panel/tree/master/archive/resource-metadata)— Resource Metadata was [submitted](https://github.com/solid/specification/pull/156) as a candidate proposal to the [`solid/specification`](https://github.com/solid/specification/). It was renamed to Auxiliary Resources during Editorial Review.
51
53
52
54
## Meetings
53
55
54
-
Panel meetings are held every other Monday at 3:00PM UTC (10:00AM Eastern / 4:00PM Central European). This bi-weekly schedule started on November 21st 2022; the latest meeting date can be found in the [minutes](https://github.com/solid/data-interoperability-panel/blob/master/meetings/). Every meeting will be announced on [gitter](https://gitter.im/solid/data-interoperability-panel), together with its agenda.
56
+
Panel meetings are held every other Monday at 3:00PM UTC (10:00AM Eastern / 4:00PM Central European). This bi-weekly schedule started on November 21st 2022; the latest meeting date can be found in the [minutes](https://github.com/solid/data-interoperability-panel/blob/master/meetings/). Every meeting is announced on [Gitter/Matrix](https://gitter.im/solid/data-interoperability-panel), together with its agenda.
Panel meeting minutes are recorded live and are [available here](https://github.com/solid/data-interoperability-panel/blob/master/meetings/)
60
+
Panel meeting minutes are recorded live (barring objection by any participant) and are [available here](https://github.com/solid/data-interoperability-panel/blob/master/meetings/).
59
61
60
62
## Process
61
63
62
64
Initiative proposals must be [submitted as issues](https://github.com/solid/data-interoperability-panel/issues/new), and receive support from members of the panel. At least three panelists (not including the panelist proposing the project) must support creation of the project, with no panel members actively rejecting it. Initiative proposals with support will be prioritized and undertaken by the panel.
63
65
64
-
Substantive changes submitted to active panel initiatives should be submitted as pull requests, and should receive at least two approved reviews from panelists, with no one actively rejecting.
66
+
Substantive changes submitted to active panel initiatives should be submitted as pull requests, and should receive at least two review approvals from panelists, with no one actively rejecting.
65
67
66
-
Panel members should work together to settle deadlocks. It may be helpful to request the perspective of a Solid Editor that would ultimately be responsible for accepting submitted candidate proposals to settle deadlocks.
68
+
Panel members should work together to settle deadlocks. It may be helpful to request the perspective of a Solid Editor who would ultimately be responsible for accepting submitted candidate proposals to settle deadlocks.
0 commit comments