Solid Community Group - Activity in 2020
No matches.
Participants
-
2 chairs appointed.
-
Sarven Capadisli became a chair.
-
Nicolas Seydoux became a chair.
-
-
2 chairs stepped down.
-
Nicolas Seydoux stepped down as a chair.
-
Sarven Capadisli stepped down as a chair.
-
-
11 participants joined.
-
bob bishop (JointSpace) joined.
-
Souen Mazouin joined.
-
Brian Kim joined.
-
Christoph Braun (Forschungszentrum Informatik (FZI)) joined.
-
Amy Guy (Digital Bazaar) joined.
-
Sarven Capadisli joined.
-
Tim Berners-Lee (W3C) joined.
-
Jan Schill joined.
-
Max Leonard (Inrupt Inc.) joined.
-
Michael Pelikan joined.
-
David Dabbs (Epsilon) joined.
-
-
3 participants left.
-
Mitzi László (Inrupt Inc.) left.
-
Sarven Capadisli left.
-
Tom Millross left.
-
-
3 organizations joined.
-
JointSpace joined.
-
British Broadcasting Corporation joined.
-
Epsilon joined.
-
GitHub
solid/specification
-
1 issue opened.
-
README links to https://solid.github.io/specification has been removed solid/specification#213, by @bourgeoa.
-
-
1 issue closed.
-
README links to https://solid.github.io/specification has been removed solid/specification#213.
-
-
1 issue reopened.
-
README links to https://solid.github.io/specification has been removed solid/specification#213, by @bourgeoa.
-
-
2 issues received 4 new comments.
-
Aligning representations of document and container resources with REST via single and compound state solid/specification#198 (3 comments by @TallTed)
-
README links to https://solid.github.io/specification has been removed solid/specification#213 (1 comment by @csarven)
-
-
1 pull request received 3 new comments.
Participants
-
1 chair stepped down.
-
Mitzi László stepped down as a chair.
-
-
7 participants joined.
-
Kai Gilb (Graphmetrix, Inc.) joined.
-
Roger Perry (Graphmetrix, Inc.) joined.
-
Frederick Gibson (Graphmetrix, Inc.) joined.
-
Michaël Dierick joined.
-
Hindia Mohammed (Ekseli Oy) joined.
-
Kevin Poulsen joined.
-
Owen Sacco (Malta College of Arts, Science and Technology) joined.
-
-
3 organizations joined.
-
Graphmetrix, Inc. joined.
-
Ekseli Oy joined.
-
Malta College of Arts, Science and Technology joined.
-
GitHub
solid/specification
-
3 issues opened.
-
POST/PUT in NSS allow multiple resource with same url and different content-type solid/specification#212, by @bourgeoa.
-
Content-Type - insisting on it as a MUST will create a barrier to adoption solid/specification#211, by @emmettownsend.
-
The case for a database instead of filesystem metaphor, and simpler schemas solid/specification#207, by @QuadrupleA.
-
-
6 issues closed.
-
POST/PUT in NSS allow multiple resource with same url and different content-type solid/specification#212.
-
Document the WAC-Allow header in the spec. solid/specification#181.
-
No way to find out if user is authorized to write to a container solid/specification#171.
-
Is WAC-Allow part of the solid spec? solid/specification#170.
-
Proposal: Accept-Put header for supported representations for PUT requests solid/specification#200.
-
The case for a database instead of filesystem metaphor, and simpler schemas solid/specification#207.
-
-
12 issues received 35 new comments.
-
Content-Type - insisting on it as a MUST will create a barrier to adoption solid/specification#211 (18 comments by @csarven, @emmettownsend, @jeff-zucker, @megoth, @TallTed, @timbl, @Vinnl)
-
Aligning representations of document and container resources with REST via single and compound state solid/specification#198 (4 comments by @acoburn, @csarven, @elf-pavlik)
-
Recursive deletion of members on deletion of container solid/specification#132 (2 comments by @acoburn, @csarven)
-
The case for a database instead of filesystem metaphor, and simpler schemas solid/specification#207 (2 comments by @QuadrupleA)
-
POST/PUT in NSS allow multiple resource with same url and different content-type solid/specification#212 (1 comment by @csarven)
-
solid/specification#171 (1 comment by @csarven)
-
Guidelines for publishing, discovering and using URI Persistence policies solid/specification#206 (1 comment by @csarven)
-
Proposal: Accept-Put header for supported representations for PUT requests solid/specification#200 (1 comment by @csarven)
-
Solid-Plugins: pod WASM runtime interface for plugins, running jobs unfit for browser client solid/specification#192 (1 comment by @joepio)
-
-
3 pull requests opened.
-
Add WAC-Allow definition and requirements solid/specification#210, by @csarven.
-
Use consistent dash solid/specification#209, by @janschill.
-
Requirements pertaining to storage solid/specification#208, by @csarven.
-
-
4 pull requests merged.
-
Add WAC-Allow definition and requirements solid/specification#210.
-
Use consistent dash solid/specification#209.
-
Requirements pertaining to storage solid/specification#208.
-
Adds definition for the Accept-Put response header solid/specification#201.
-
-
1 pull request closed.
-
clarify WebID-TLS solid/specification#140.
-
-
1 pull request reopened.
-
Add WAC-Allow definition and requirements solid/specification#210, by @csarven.
-
-
4 pull requests received 44 new comments.
-
Add WAC-Allow definition and requirements solid/specification#210 (27 comments by @acoburn, @bblfish, @csarven, @RubenVerborgh, @timbl)
-
Requirements pertaining to storage solid/specification#208 (13 comments by @csarven, @RubenVerborgh)
-
Participants
-
4 participants joined.
-
Aad Versteden (REDPENCIL) joined.
-
Tao Chen (Underwriters Laboratories - Transaction Security) joined.
-
kofi kyei joined.
-
Peter Zuiddam joined.
-
-
2 organizations joined.
-
REDPENCIL joined.
-
Underwriters Laboratories - Transaction Security joined.
-
GitHub
solid/specification
-
1 issue opened.
-
Guidelines for publishing, discovering and using URI Persistence policies solid/specification#206, by @csarven.
-
-
3 issues closed.
-
PUT RDFa, then GET turtle solid/specification#195.
-
Required RDF serializations for Solid solid/specification#45.
-
Representation URLs and interactions solid/specification#109.
-
-
9 issues received 36 new comments.
-
Aligning representations of document and container resources with REST via single and compound state solid/specification#198 (22 comments by @csarven, @elf-pavlik, @matthieubosquet, @TallTed)
-
Which permissions are required for deleting a resource? solid/specification#197 (5 comments by @bblfish, @csarven, @michielbdejong)
-
Guidelines for publishing, discovering and using URI Persistence policies solid/specification#206 (2 comments by @csarven, @d-a-v-i--)
-
Querying multiple subjects in one request solid/specification#162 (2 comments by @namedgraph, @RubenVerborgh)
-
solid/specification#154 (1 comment by @csarven)
-
Solid-Plugins: pod WASM runtime interface for plugins, running jobs unfit for browser client solid/specification#192 (1 comment by @joepio)
-
-
2 pull requests opened.
-
Restrict POST target to existing resources solid/specification#205, by @csarven.
-
Restrict POST target to existing resources solid/specification#204, by @csarven.
-
-
3 pull requests merged.
-
Restrict POST target to existing resources solid/specification#205.
-
Add section for acl Link relation type solid/specification#199.
-
Add payload and representations in RDF solid/specification#196.
-
-
1 pull request closed.
-
Restrict POST target to existing resources solid/specification#204.
-
-
1 pull request reopened.
-
Restrict POST target to existing resources solid/specification#205, by @csarven.
-
-
3 pull requests received 12 new comments.
-
Restrict POST target to existing resources solid/specification#205 (10 comments by @bourgeoa, @csarven, @nicolasmondada, @RubenVerborgh, @Vinnl)
-
Participants
-
1 participant joined.
-
Ricky White (The Migus Group) joined.
-
-
1 organization joined.
-
The Migus Group joined.
-
GitHub
solid/specification
-
4 issues opened.
-
Defining an OAuth scope in the spec for WebID-OIDC solid/specification#203, by @NSeydoux.
-
iana link relation type uris solid/specification#202, by @phtyson.
-
Proposal: Accept-Put header for supported representations for PUT requests solid/specification#200, by @csarven.
-
Aligning representations of document and container resources with REST via single and compound state solid/specification#198, by @RubenVerborgh.
-
-
1 issue closed.
-
iana link relation type uris solid/specification#202.
-
-
1 issue reopened.
-
Which permissions are required for deleting a resource? solid/specification#197, by @csarven.
-
-
11 issues received 57 new comments.
-
Which permissions are required for deleting a resource? solid/specification#197 (34 comments by @acoburn, @csarven, @d-a-v-i--, @justinwb, @michielbdejong, @RubenVerborgh, @timbl)
-
Discuss returning 404 for privacy reasons solid/specification#14 (7 comments by @csarven, @d-a-v-i--, @michielbdejong, @timbl)
-
Aligning representations of document and container resources with REST via single and compound state solid/specification#198 (4 comments by @acoburn, @csarven, @elf-pavlik)
-
Enable full use of relative URLs in Solid solid/specification#194 (2 comments by @bblfish, @csarven)
-
Proposal: Accept-Put header for supported representations for PUT requests solid/specification#200 (2 comments by @acoburn, @csarven)
-
Representation URLs and interactions solid/specification#109 (2 comments by @michielbdejong, @RubenVerborgh)
-
Specify/advise semantics of default Container resources (index.html/.ttl) solid/specification#69 (1 comment by @RubenVerborgh)
-
Does recursive container creation leak information? solid/specification#129 (1 comment by @michielbdejong)
-
-
3 pull requests opened.
-
Adds definition for the Accept-Put response header solid/specification#201, by @csarven.
-
Add section for acl Link relation type solid/specification#199, by @csarven.
-
Add payload and representations in RDF solid/specification#196, by @csarven.
-
-
1 pull request reopened.
-
Add section for acl Link relation type solid/specification#199, by @csarven.
-
-
3 pull requests received 25 new comments.
-
Add payload and representations in RDF solid/specification#196 (12 comments by @acoburn, @bblfish, @csarven, @michielbdejong, @RubenVerborgh)
-
Add section for acl Link relation type solid/specification#199 (11 comments by @bblfish, @csarven, @kidehen, @RubenVerborgh)
-
Remove server requirement to advertise container type in HTTP header solid/specification#190 (2 comments by @RubenVerborgh)
-
Participants
-
4 participants joined.
-
Dana Scott joined.
-
Edwin Steiner joined.
-
Hannah Short (CERN) joined.
-
Brent Hueth (University of Wisconsin-Madison) joined.
-
-
2 organizations joined.
-
CERN joined.
-
University of Wisconsin-Madison joined.
-
GitHub
solid/specification
-
4 issues opened.
-
Enable full use of relative URLs in Solid solid/specification#194, by @bblfish.
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193, by @Vinnl.
-
Solid-Plugins: pod WASM runtime interface for plugins, running jobs unfit for browser client solid/specification#192, by @joepio.
-
Basic resource typing through HTTP Link header solid/specification#191, by @csarven.
-
-
20 issues closed.
-
Handling URIs with a path component ending with the same segment term solid/specification#107.
-
Which LDP container types does a Solid server need to support solid/specification#47.
-
Clarify the lifecycle of an ACL resource solid/specification#58.
-
Use 410 Gone for deleted documents solid/specification#103.
-
Which permissions are required for deleting an ACL document? solid/specification#145.
-
What happens if there is no ACL? solid/specification#130.
-
Content-Type MUST be used on all PUT/POST/PATCH requests? solid/specification#70.
-
Should a Solid server limit the reuse of URLs? solid/specification#46.
-
Specify the semantics of DELETE solid/specification#41.
-
Should it be possible to create orphan resources? solid/specification#97.
-
405 for "other" methods? solid/specification#117.
-
Specify POST solid/specification#108.
-
Specify PATCH solid/specification#85.
-
Clarify recursive container creation on POST, PATCH and PUT solid/specification#68.
-
Implementation guidance on ETags solid/specification#60.
-
What are the semantics of Accept-Post solid/specification#43.
-
Methods for ACL resource creation solid/specification#42.
-
Specify semantics of resource creation via PUT solid/specification#40.
-
How does client apps know that certain ACL files cannot be deleted? solid/specification#37.
-
Is support for RFC7232 Conditional Requests mandatory? solid/specification#33.
-
-
12 issues received 32 new comments.
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193 (9 comments by @bourgeoa, @csarven, @megoth, @nicolasmondada)
-
Enable full use of relative URLs in Solid solid/specification#194 (7 comments by @bblfish, @csarven)
-
Specify container listing mechanism solid/specification#116 (5 comments by @acoburn, @csarven, @dmitrizagidulin)
-
Solid-Plugins: pod WASM runtime interface for plugins, running jobs unfit for browser client solid/specification#192 (2 comments by @acoburn, @joepio)
-
Is Solid containment strictly hierarchical? solid/specification#98 (2 comments by @akuckartz, @csarven)
-
Restrict linking and creation of extended auxiliary resources solid/specification#184 (1 comment by @bblfish)
-
-
1 pull request opened.
-
Remove server requirement to advertise container type in HTTP header solid/specification#190, by @csarven.
-
-
1 pull request merged.
-
Reading and Writing resources solid/specification#188.
-
-
2 pull requests received 5 new comments.
-
Remove server requirement to advertise container type in HTTP header solid/specification#190 (4 comments by @csarven, @emmettownsend, @RubenVerborgh)
-
Participants
-
3 participants joined.
-
Leon Porter joined.
-
Emmet Townsend (Inrupt Inc.) joined.
-
davi ottenheimer (Inrupt Inc.) joined.
-
GitHub
solid/specification
-
1 issue opened.
-
Strategy for test-suite solid/specification#189, by @justinwb.
-
-
4 issues closed.
-
Can one convert a non-container LDP-RS into an LDP-BC or vice versa? solid/specification#90.
-
Should you be allowed to submit overlapping resource and container URIs? solid/specification#104.
-
Is Solid containment strictly hierarchical? solid/specification#98.
-
Valid serializations of ACL resources solid/specification#150.
-
-
6 issues received 6 new comments.
-
Can one convert a non-container LDP-RS into an LDP-BC or vice versa? solid/specification#90 (1 comment by @csarven)
-
Should you be allowed to submit overlapping resource and container URIs? solid/specification#104 (1 comment by @csarven)
-
1 pull request opened.
-
Reading and Writing resources solid/specification#188, by @csarven.
-
-
1 pull request closed.
-
DELETE support and semantics solid/specification#187.
-
-
2 pull requests received 56 new comments.
-
Reading and Writing resources solid/specification#188 (55 comments by @acoburn, @csarven, @RubenVerborgh)
-
GitHub
solid/specification
-
2 issues opened.
-
Can a non-default ACL apply to a child resource ? solid/specification#186, by @NSeydoux.
-
Restrict linking and creation of extended auxiliary resources solid/specification#184, by @csarven.
-
-
8 issues closed.
-
Generalise error messages solid/specification#112.
-
Status messages for server errors solid/specification#111.
-
How does the server determine whether a resource is an ACL resource? solid/specification#31.
-
what is the scope of the Solid spec? solid/specification#29.
-
Add the semantics of slashes, which is shared by client and server solid/specification#35.
-
Handling requests without an interaction model solid/specification#105.
-
Handling resources and updates with conflicting interaction models solid/specification#121.
-
Clarify the heuristics to determine the interaction model if none is specified solid/specification#128.
-
-
16 issues received 27 new comments.
-
Handling resources and updates with conflicting interaction models solid/specification#121 (3 comments by @csarven)
-
Restrict linking and creation of extended auxiliary resources solid/specification#184 (2 comments by @csarven, @DaemonAlchemist)
-
How does the server determine whether a resource is an ACL resource? solid/specification#31 (1 comment by @csarven)
-
Add the semantics of slashes, which is shared by client and server solid/specification#35 (1 comment by @csarven)
-
Is support for RFC7232 Conditional Requests mandatory? solid/specification#33 (1 comment by @csarven)
-
Clarify the heuristics to determine the interaction model if none is specified solid/specification#128 (1 comment by @csarven)
-
2 pull requests opened.
-
DELETE support and semantics solid/specification#187, by @csarven.
-
Add constraint discovery for client errors solid/specification#185, by @csarven.
-
-
1 pull request merged.
-
Add heuristic to determine resource type solid/specification#160.
-
-
3 pull requests received 27 new comments.
-
DELETE support and semantics solid/specification#187 (17 comments by @acoburn, @csarven, @pmcb55, @timbl)
-
Add constraint discovery for client errors solid/specification#185 (7 comments by @csarven, @dmitrizagidulin, @justinwb)
-
Add heuristic to determine resource type solid/specification#160 (3 comments by @csarven, @justinwb)
-
Participants
-
2 participants joined.
-
Rahul Gupta joined.
-
Rishabh Gupta joined.
-
GitHub
solid/specification
-
3 issues opened.
-
README leads to confusion solid/specification#182, by @akuckartz.
-
Need clear specifications of POD access and usage controls solid/specification#180, by @sproffer.
-
Identify Solid Server and Spec Version solid/specification#179, by @CxRes.
-
-
1 issue reopened.
-
Document the WAC-Allow header in the spec. solid/specification#181, by @csarven.
-
-
14 issues received 51 new comments.
-
Explain the ACL inheritance algorithm for clients solid/specification#106 (19 comments by @acoburn, @csarven, @justinwb, @Vinnl)
-
Clarify the notion and mechanisms for server-managed information solid/specification#177 (8 comments by @csarven, @elf-pavlik, @jaxoncreed, @justinwb)
-
Identify Solid Server and Spec Version solid/specification#179 (6 comments by @csarven, @CxRes, @dmitrizagidulin)
-
Should it be possible to find controller of storage via resources? solid/specification#153 (2 comments by @csarven, @megoth)
-
Add ability to query resource access activity solid/specification#24 (2 comments by @csarven, @justinwb)
-
Address workarounds that undermine access control, data validation, server-managed resources solid/specification#175 (2 comments by @csarven, @justinwb)
-
How does client apps know that certain ACL files cannot be deleted? solid/specification#37 (1 comment by @csarven)
-
-
3 pull requests merged.
-
Update LICENSE.md solid/specification#89.
-
Initial auxiliary resources draft solid/specification#156.
-
Some criteria based on rough consensus solid/specification#157.
-
-
4 pull requests received 37 new comments.
-
Add heuristic to determine resource type solid/specification#160 (20 comments by @csarven, @dmitrizagidulin, @justinwb, @RubenVerborgh)
-
Initial auxiliary resources draft solid/specification#156 (12 comments by @csarven, @dmitrizagidulin, @justinwb)
-
Participants
-
2 participants joined.
-
Nicolas Seydoux (Inrupt Inc.) joined.
-
Josh Collins (Janeiro Digital) joined.
-
-
1 participant left.
-
Miel Vander Sande (VIAA) left.
-
GitHub
solid/specification
-
13 issues opened.
-
Auxiliary resource type for configuration solid/specification#178, by @justinwb.
-
Clarify the notion and mechanisms for server-managed information solid/specification#177, by @csarven.
-
Address workarounds that undermine access control, data validation, server-managed resources solid/specification#175, by @csarven.
-
Specifying permission sets for auxiliary resource types solid/specification#174, by @justinwb.
-
Allowing multiple descriptive auxiliary resources for a single resource solid/specification#173, by @justinwb.
-
Link relation URIs for Auxiliary Resource types solid/specification#172, by @justinwb.
-
Shape of ACL solid/specification#169, by @csarven.
-
What does a delete operation imply? solid/specification#165, by @csarven.
-
Webhooks solid/specification#164, by @michielbdejong.
-
Indicate Solid protocol to the WebSocket interface solid/specification#163, by @csarven.
-
Querying multiple subjects in one request solid/specification#162, by @joepio.
-
Standardizing state changes in resources (history, undo, sync) solid/specification#161, by @joepio.
-
Need server-side within-pod MOVE directory tree (for Trash) solid/specification#159, by @timbl.
-
-
1 issue closed.
-
Ensure the scope of this repository is accurate and clear to the public solid/specification#133.
-
-
15 issues received 35 new comments.
-
Specifying permission sets for auxiliary resource types solid/specification#174 (5 comments by @acoburn, @csarven, @dmitrizagidulin, @justinwb)
-
Methods for ACL resource creation solid/specification#42 (5 comments by @acoburn, @csarven, @jaxoncreed, @justinwb)
-
Is WAC-Allow part of the solid spec? solid/specification#170 (4 comments by @csarven, @Otto-AA, @RubenVerborgh)
-
Should it be possible to find controller of storage via resources? solid/specification#153 (4 comments by @csarven, @dmitrizagidulin, @megoth)
-
Allowing multiple descriptive auxiliary resources for a single resource solid/specification#173 (3 comments by @csarven, @justinwb)
-
Link relation URIs for Auxiliary Resource types solid/specification#172 (3 comments by @csarven, @justinwb)
-
Standardizing state changes in resources (history, undo, sync) solid/specification#161 (3 comments by @joepio, @RubenVerborgh)
-
Which permissions are required for deleting an ACL document? solid/specification#145 (1 comment by @csarven)
-
solid/specification#171 (1 comment by @csarven)
-
Will WebSocket support be part of the Solid specification solid/specification#50 (1 comment by @elf-pavlik)
-
Need server-side within-pod MOVE directory tree (for Trash) solid/specification#159 (1 comment by @elf-pavlik)
-
-
1 pull request opened.
-
Add heuristic to determine resource type solid/specification#160, by @csarven.
-
-
1 pull request closed.
-
Rename WebID-OIDC to Solid-OIDC. solid/specification#114.
-
-
4 pull requests received 45 new comments.
-
Initial auxiliary resources draft solid/specification#156 (29 comments by @acoburn, @csarven, @dmitrizagidulin, @justinwb, @RubenVerborgh)
-
Some criteria based on rough consensus solid/specification#157 (13 comments by @csarven, @dmitrizagidulin, @justinwb, @RubenVerborgh)
-
Participants
-
4 participants joined.
-
Bart Hanssens (FPS BOSA) joined.
-
Takeo Nishikata (Massachusetts Institute of Technology (MIT)) joined.
-
Alice Poggioli (Startin'blox) joined.
-
Dirk Roeleveld (X-Line Consulting) joined.
-
-
2 participants left.
-
Bart Hanssens (FPS BOSA) left.
-
Takeo Nishikata (Massachusetts Institute of Technology (MIT)) left.
-
-
3 organizations joined.
-
FPS BOSA joined.
-
Massachusetts Institute of Technology (MIT) joined.
-
X-Line Consulting joined.
-
-
1 organization left.
-
Fedict - Federal Public Service ICT left.
-
GitHub
solid/specification
-
5 issues opened.
-
prefer 307 to 302? solid/specification#158, by @ericprud.
-
Should it be possible to find controller of storage via resources? solid/specification#153, by @megoth.
-
Specifying a registration endpoint for the Pod Provider solid/specification#152, by @NSeydoux.
-
Addressing data cascading solid/specification#151, by @csarven.
-
Valid serializations of ACL resources solid/specification#150, by @kjetilk.
-
-
11 issues received 45 new comments.
-
Specifying a registration endpoint for the Pod Provider solid/specification#152 (10 comments by @elf-pavlik, @kjetilk, @NSeydoux, @RubenVerborgh)
-
Should it be possible to find controller of storage via resources? solid/specification#153 (10 comments by @csarven, @elf-pavlik, @kjetilk, @megoth, @RubenVerborgh)
-
WebSockets and HTTP/2 solid/specification#122 (9 comments by @acoburn, @elf-pavlik, @kjetilk, @michielbdejong)
-
Should a Solid server limit the reuse of URLs? solid/specification#46 (5 comments by @csarven, @ericprud, @kjetilk)
-
Valid serializations of ACL resources solid/specification#150 (3 comments by @bourgeoa, @csarven, @RubenVerborgh)
-
Document changelog from "roughly-0.8" to "Dec-2019" solid/specification#135 (1 comment by @michielbdejong)
-
Which permissions are required for deleting an ACL document? solid/specification#145 (1 comment by @justinwb)
-
-
2 pull requests opened.
-
Some criteria based on rough consensus solid/specification#157, by @csarven.
-
Initial auxiliary resources draft solid/specification#156, by @justinwb.
-
-
2 pull requests received 94 new comments.
-
Initial auxiliary resources draft solid/specification#156 (62 comments by @csarven, @ericprud, @justinwb, @RubenVerborgh)
-
Some criteria based on rough consensus solid/specification#157 (32 comments by @csarven, @dmitrizagidulin, @RubenVerborgh)
-
Participants
-
2 participants joined.
-
Ali Siragedien (Ali Method) joined.
-
david faveris joined.
-
-
1 organization joined.
-
Ali Method joined.
-
GitHub
solid/specification
-
4 issues opened.
-
What does a read operation imply? solid/specification#149, by @csarven.
-
WebID-TLS specification solid/specification#148, by @namedgraph.
-
Complete Self-Review Questionnaire: Security and Privacy solid/specification#147, by @csarven.
-
Precedence of response codes solid/specification#146, by @kjetilk.
-
-
15 issues received 52 new comments.
-
Clarify the heuristics to determine the interaction model if none is specified solid/specification#128 (10 comments by @csarven, @kjetilk)
-
Which permissions are required for deleting an ACL document? solid/specification#145 (9 comments by @csarven, @justinwb, @kjetilk)
-
Resource creation behaviour when using the `Slug` header solid/specification#96 (7 comments by @csarven, @elf-pavlik, @kjetilk, @RubenVerborgh)
-
What does a read operation imply? solid/specification#149 (5 comments by @csarven, @justinwb, @kjetilk)
-
Specify/advise semantics of default Container resources (index.html/.ttl) solid/specification#69 (4 comments by @csarven, @elf-pavlik, @kjetilk)
-
Should a Solid server limit the reuse of URLs? solid/specification#46 (2 comments by @csarven, @kjetilk)
-
Specify semantics of resource creation via PUT solid/specification#40 (2 comments by @kjetilk, @RubenVerborgh)
-
Which LDP container types does a Solid server need to support solid/specification#47 (1 comment by @csarven)
-
Assumptions around Disclosure of Sensitive Information in URIs solid/specification#142 (1 comment by @kjetilk)
-
Participants
-
2 participants joined.
-
Søren Grauslund joined.
-
Charity Langley joined.
-
GitHub
solid/specification
-
7 issues opened.
-
Container Data Augmentation solid/specification#144, by @kjetilk.
-
Handling Capability URLs solid/specification#143, by @csarven.
-
Assumptions around Disclosure of Sensitive Information in URIs solid/specification#142, by @kjetilk.
-
Determine the URIs for the specifications solid/specification#141, by @csarven.
-
Make any deviation of SPARQL UPDATE explicit solid/specification#139, by @RubenVerborgh.
-
Variability in Solid specs solid/specification#138, by @csarven.
-
Global atomicity requirements solid/specification#137, by @csarven.
-
-
1 issue closed.
-
Gap Analysis of Milestone solid/specification#134.
-
-
23 issues received 150 new comments.
-
Specify POST solid/specification#108 (40 comments by @acoburn, @csarven, @elf-pavlik, @ericprud, @kjetilk, @TallTed)
-
Specify/advise semantics of default Container resources (index.html/.ttl) solid/specification#69 (18 comments by @csarven, @elf-pavlik, @kjetilk, @TallTed)
-
Assumptions around Disclosure of Sensitive Information in URIs solid/specification#142 (12 comments by @acoburn, @csarven, @d-a-v-i--, @elf-pavlik, @kjetilk, @RubenVerborgh)
-
Clarify the heuristics to determine the interaction model if none is specified solid/specification#128 (12 comments by @csarven, @kjetilk, @TallTed)
-
Specify container listing mechanism solid/specification#116 (11 comments by @csarven, @ericprud, @kjetilk, @simonstey)
-
Level of SPARQL Update support solid/specification#125 (9 comments by @kjetilk, @rubensworks, @RubenVerborgh)
-
Container Data Augmentation solid/specification#144 (7 comments by @acoburn, @csarven, @elf-pavlik, @kjetilk)
-
Global atomicity requirements solid/specification#137 (7 comments by @csarven, @kjetilk, @michielbdejong)
-
Document changelog from "roughly-0.8" to "Dec-2019" solid/specification#135 (5 comments by @elf-pavlik, @kjetilk, @michielbdejong, @timbl)
-
Determine the URIs for the specifications solid/specification#141 (2 comments by @justinwb, @kjetilk)
-
Handling URIs with a path component ending with the same segment term solid/specification#107 (1 comment by @csarven)
-
Resource creation behaviour when using the `Slug` header solid/specification#96 (1 comment by @csarven)
-
-
1 pull request opened.
-
clarify WebID-TLS solid/specification#140, by @elf-pavlik.
-
-
1 pull request received 3 new comments.