Solid Community Group - Activity in 2021
No matches.
Participants
-
1 participant joined.
-
Phil Sawatsky joined.
-
GitHub
solid/specification
-
4 issues opened.
-
Mechanics to publish EDs separately from releases solid/specification#370, by @kjetilk.
-
Specify resource naming constraints unambiguously solid/specification#368, by @damooo.
-
Specification release automation solid/specification#367, by @kjetilk.
-
Complete Self-Review Questionnaire: Societal Impact solid/specification#359, by @csarven.
-
-
4 issues closed.
-
Specify container listing mechanism solid/specification#116.
-
Alternative update support with N3 patch solid/specification#332.
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220.
-
Specify existing practice for Container data about contents solid/specification#343.
-
-
10 issues received 25 new comments.
-
Use inclusive language in Solid technical reports solid/specification#244 (8 comments by @csarven, @elf-pavlik, @jeff-zucker, @justinwb, @KyraAssaad, @langsamu, @TallTed)
-
Servers responding to request targets using the asterisk-form or the origin-form solid/specification#356 (4 comments by @acoburn, @csarven, @kjetilk)
-
Mechanics to publish EDs separately from releases solid/specification#370 (3 comments by @elf-pavlik, @kjetilk)
-
Add the semantics of slashes, which is shared by client and server solid/specification#35 (2 comments by @kjetilk, @pietercolpaert)
-
Specify metadata mechanism for Containers, RDFResources, NonRDFResources solid/specification#63 (1 comment by @Potherca)
-
-
9 pull requests opened.
-
Remove server-options-asterisk-accept-headers. Add OPTIONS to server-accept-headers solid/specification#369, by @csarven.
-
Update my homepage URL solid/specification#366, by @kjetilk.
-
Use storage or server in place of data pod solid/specification#365, by @csarven.
-
Allow Allow headers in DELETE requests to other resources solid/specification#364, by @kjetilk.
-
Update websockets solid/specification#363, by @csarven.
-
Auxiliary resource for container metadata as alternative solid/specification#362, by @kjetilk.
-
Create solid-webid-profiles.md solid/specification#361, by @jeff-zucker.
-
Add societal-impact-questionnaire stub solid/specification#360, by @csarven.
-
Refer to WAC. Remove duplicate requirements solid/specification#358, by @csarven.
-
-
9 pull requests merged.
-
Add societal-impact-questionnaire stub solid/specification#360.
-
Update my homepage URL solid/specification#366.
-
Update websockets solid/specification#363.
-
Use storage or server in place of data pod solid/specification#365.
-
Allow Allow headers in DELETE requests to other resources solid/specification#364.
-
Describe N3 Patch solid/specification#346.
-
Authoritative Contained Resource Data solid/specification#352.
-
W3C Solid Community Group Meeting Guidelines solid/specification#319.
-
Refer to WAC. Remove duplicate requirements solid/specification#358.
-
-
1 pull request closed.
-
Create solid-webid-profiles.md solid/specification#361.
-
-
10 pull requests received 79 new comments.
-
Authoritative Contained Resource Data solid/specification#352 (41 comments by @acoburn, @csarven, @kjetilk, @NoelDeMartin, @RubenVerborgh)
-
Describe N3 Patch solid/specification#346 (14 comments by @csarven, @kjetilk, @RubenVerborgh, @timbl)
-
Add societal-impact-questionnaire stub solid/specification#360 (6 comments by @bourgeoa, @jeff-zucker, @TallTed)
-
Remove server-options-asterisk-accept-headers. Add OPTIONS to server-accept-headers solid/specification#369 (5 comments by @acoburn, @csarven, @TallTed)
-
Create solid-webid-profiles.md solid/specification#361 (5 comments by @csarven, @matthieubosquet, @TallTed)
-
Auxiliary resource for container metadata as alternative solid/specification#362 (3 comments by @kjetilk, @TallTed)
-
Restriction to only respond to authorized with Allow et al solid/specification#353 (1 comment by @csarven)
-
Participants
-
1 participant joined.
-
Beatriz Esteves (imec) joined.
-
GitHub
solid/specification
-
7 issues opened.
-
Servers responding to request targets using the asterisk-form or the origin-form solid/specification#356, by @csarven.
-
Server Description solid/specification#355, by @csarven.
-
Add references for "triple" (and "triple pattern") to the protocol document solid/specification#348, by @RubenVerborgh.
-
Use IRIs for resource identification solid/specification#347, by @jakubklimek.
-
Where to make write requests for resources that return 303 for retrieval? solid/specification#344, by @csarven.
-
Specify existing practice for Container data about contents solid/specification#343, by @timbl.
-
Content of Turtle and RDFa documents should be wholly and entirely preserved solid/specification#342, by @TallTed.
-
-
1 issue closed.
-
Add references for "triple" (and "triple pattern") to the protocol document solid/specification#348.
-
-
15 issues received 121 new comments.
-
Content of Turtle and RDFa documents should be wholly and entirely preserved solid/specification#342 (29 comments by @csarven, @damooo, @elf-pavlik, @kidehen, @kjetilk, @rubensworks, @TallTed)
-
Use IRIs for resource identification solid/specification#347 (15 comments by @damooo, @elf-pavlik, @joachimvh, @kjetilk)
-
Specify existing practice for Container data about contents solid/specification#343 (12 comments by @bourgeoa, @csarven, @jeff-zucker, @justinwb, @kjetilk, @TallTed, @timbl)
-
Use inclusive language in Solid technical reports solid/specification#244 (10 comments by @csarven, @jeff-zucker, @KyraAssaad, @TallTed, @VirginiaBalseiro)
-
Specify container description solid/specification#227 (10 comments by @gibsonf1, @jeff-zucker, @kjetilk, @TallTed, @timbl)
-
Where to make write requests for resources that return 303 for retrieval? solid/specification#344 (10 comments by @csarven, @gibsonf1, @ThisIsMissEm, @timbl)
-
Server Description solid/specification#355 (8 comments by @acoburn, @csarven, @kjetilk, @langsamu, @ThisIsMissEm)
-
Add references for "triple" (and "triple pattern") to the protocol document solid/specification#348 (7 comments by @csarven, @ericprud, @justinwb, @kjetilk)
-
Slash semantics and conflicting requests on resource creation solid/specification#301 (7 comments by @csarven, @kjetilk)
-
Servers responding to request targets using the asterisk-form or the origin-form solid/specification#356 (6 comments by @acoburn, @csarven, @kjetilk, @timbl)
-
Clarify the notion and mechanisms for server-managed information solid/specification#177 (2 comments by @justinwb, @kjetilk)
-
-
8 pull requests opened.
-
Remove optional advisement relying on delegation of authority solid/specification#357, by @csarven.
-
Restriction to only respond to authorized with Allow et al solid/specification#353, by @kjetilk.
-
Authoritative Contained Resource Data solid/specification#352, by @csarven.
-
Alternative references for triple and triple pattern solid/specification#351, by @kjetilk.
-
Add definitions for triples and triple patterns solid/specification#350, by @kjetilk.
-
Introduce constraint on PATCH to only patch target resource solid/specification#349, by @kjetilk.
-
Describe N3 Patch solid/specification#346, by @RubenVerborgh.
-
Add .editorconfig solid/specification#345, by @RubenVerborgh.
-
-
6 pull requests merged.
-
Remove optional advisement relying on delegation of authority solid/specification#357.
-
Clarify 409 on containment triples solid/specification#298.
-
Alternative references for triple and triple pattern solid/specification#351.
-
Add .editorconfig solid/specification#345.
-
Write methods as requirements solid/specification#304.
-
Remove server requirement to advertise container type in HTTP header solid/specification#190.
-
-
1 pull request closed.
-
Add definitions for triples and triple patterns solid/specification#350.
-
-
12 pull requests received 202 new comments.
-
Describe N3 Patch solid/specification#346 (83 comments by @csarven, @justinwb, @kjetilk, @RubenVerborgh, @TallTed)
-
Authoritative Contained Resource Data solid/specification#352 (39 comments by @acoburn, @csarven, @justinwb, @kjetilk, @RubenVerborgh, @timbl)
-
Clarify 409 on containment triples solid/specification#298 (28 comments by @csarven, @kjetilk, @TallTed)
-
Introduce constraint on PATCH to only patch target resource solid/specification#349 (17 comments by @csarven, @justinwb, @kjetilk, @RubenVerborgh, @TallTed)
-
Tighten consistency requirements for resource types solid/specification#341 (15 comments by @csarven, @kjetilk, @RubenVerborgh, @TallTed)
-
Restriction to only respond to authorized with Allow et al solid/specification#353 (7 comments by @acoburn, @kjetilk, @ThisIsMissEm)
-
Add definitions for triples and triple patterns solid/specification#350 (3 comments by @damooo, @kjetilk)
-
W3C Solid Community Group Meeting Guidelines solid/specification#319 (2 comments by @dmitrizagidulin, @elf-pavlik)
-
Behavior for other SPARQL Update operations solid/specification#323 (2 comments by @dmitrizagidulin, @TallTed)
-
Trust between owners on same origin with multiple storages solid/specification#290 (1 comment by @dmitrizagidulin)
-
Remove server requirement to advertise container type in HTTP header solid/specification#190 (1 comment by @csarven)
-
Participants
-
8 participants joined.
-
Jackson Morgan (O.team) joined.
-
Kevin Howard (Inrupt Inc.) joined.
-
Christopher Prince (Google LLC) joined.
-
Osmar Olivo (Inrupt Inc.) joined.
-
Tom Haegemans (Digita) joined.
-
Vivien Kraus joined.
-
Michiel Bellens joined.
-
Soheil Roshankish (Università della Svizzera italiana) joined.
-
-
2 organizations joined.
-
Digita joined.
-
Università della Svizzera italiana joined.
-
GitHub
solid/specification
-
7 issues opened.
-
ETag might need a weak validator instead solid/specification#340, by @RubenVerborgh.
-
Server should partially encode Slug header values solid/specification#339, by @langsamu.
-
Alternative update support with N3 patch solid/specification#332, by @RubenVerborgh.
-
Allow non-rdf resources as auxiliary resources solid/specification#329, by @damooo.
-
"acl" should = Active Control List solid/specification#326, by @bblfish.
-
Coin and document effective ACL URI solid/specification#325, by @bblfish.
-
Implications of semaphore mechanism for SPARQL Update solid/specification#322, by @kjetilk.
-
-
1 issue reopened.
-
Proposal: Support COPY use case solid/specification#19, by @kjetilk.
-
-
17 issues received 91 new comments.
-
Specify container description solid/specification#227 (18 comments by @bblfish, @csarven, @jeff-zucker, @kjetilk, @timbl)
-
Coin and document effective ACL URI solid/specification#325 (13 comments by @acoburn, @bblfish, @csarven)
-
Level of SPARQL Update support solid/specification#125 (11 comments by @jeff-zucker, @kjetilk, @rubensworks, @RubenVerborgh)
-
Slash semantics and conflicting requests on resource creation solid/specification#301 (9 comments by @kjetilk, @langsamu, @TallTed)
-
Allow non-rdf resources as auxiliary resources solid/specification#329 (9 comments by @bourgeoa, @csarven, @damooo, @kjetilk)
-
Implications of semaphore mechanism for SPARQL Update solid/specification#322 (8 comments by @csarven, @kjetilk, @rubensworks)
-
Alternative update support with N3 patch solid/specification#332 (5 comments by @bourgeoa, @jeff-zucker, @timbl)
-
Specify metadata mechanism for Containers, RDFResources, NonRDFResources solid/specification#63 (3 comments by @csarven, @kjetilk, @phochste)
-
Conformance critieria for headers with multiple field values solid/specification#71 (1 comment by @csarven)
-
-
17 pull requests opened.
-
Tighten consistency requirements for resource types solid/specification#341, by @kjetilk.
-
Update 2021-10-27.md solid/specification#338, by @bblfish.
-
clarifications of meetings notes for TPAC 2021-10-27 solid/specification#337, by @bblfish.
-
fork/meeting/2021 10 27 minutes2 solid/specification#336, by @bblfish.
-
meeting/2021 10 27 minutes solid/specification#335, by @bblfish.
-
Correct line to what I think I said solid/specification#334, by @kjetilk.
-
Add 2021-10-27 minutes solid/specification#333, by @csarven.
-
Some links to issues solid/specification#331, by @crspybits.
-
Alternative SPARQL Update support solid/specification#330, by @kjetilk.
-
Agenda for Solid Implementer Feedback Session solid/specification#328, by @justinwb.
-
2021-10-27 meeting agenda solid/specification#327, by @csarven.
-
Add possible semaphore mechanism wording solid/specification#324, by @kjetilk.
-
Behavior for other SPARQL Update operations solid/specification#323, by @kjetilk.
-
Simplify the SPARQL subset BNF solid/specification#321, by @kjetilk.
-
Drafting SPARQL Update support solid/specification#320, by @kjetilk.
-
W3C Solid Community Group Meeting Guidelines solid/specification#319, by @csarven.
-
Add definitions: uri resources agent origin solid/specification#318, by @csarven.
-
-
8 pull requests merged.
-
Add 2021-10-27 minutes solid/specification#333.
-
clarifications of meetings notes for TPAC 2021-10-27 solid/specification#337.
-
Correct line to what I think I said solid/specification#334.
-
Some links to issues solid/specification#331.
-
Agenda for Solid Implementer Feedback Session solid/specification#328.
-
2021-10-27 meeting agenda solid/specification#327.
-
Simplify the SPARQL subset BNF solid/specification#321.
-
Add definitions: uri resources agent origin solid/specification#318.
-
-
3 pull requests closed.
-
Update 2021-10-27.md solid/specification#338.
-
meeting/2021 10 27 minutes solid/specification#335.
-
fork/meeting/2021 10 27 minutes2 solid/specification#336.
-
-
15 pull requests received 172 new comments.
-
Add 2021-10-27 minutes solid/specification#333 (55 comments by @acoburn, @bblfish, @csarven, @TallTed)
-
W3C Solid Community Group Meeting Guidelines solid/specification#319 (45 comments by @bblfish, @csarven, @elf-pavlik, @justinwb, @kjetilk, @TallTed, @VirginiaBalseiro)
-
Drafting SPARQL Update support solid/specification#320 (34 comments by @csarven, @ericprud, @kjetilk, @RubenVerborgh)
-
Clarify 409 on containment triples solid/specification#298 (8 comments by @acoburn, @csarven, @kjetilk)
-
Add definitions: uri resources agent origin solid/specification#318 (7 comments by @csarven, @RubenVerborgh, @TallTed)
-
Tighten consistency requirements for resource types solid/specification#341 (4 comments by @acoburn, @RubenVerborgh)
-
Add possible semaphore mechanism wording solid/specification#324 (4 comments by @csarven, @kjetilk, @RubenVerborgh)
-
Add that all RDF representations should represent the same graph solid/specification#309 (1 comment by @kjetilk)
-
Participants
-
6 participants joined.
-
Angel Araya (Janeiro Digital) joined.
-
Hua-Rong Chu (Chunghwa Telecom Company, Ltd.) joined.
-
Barath Raghavan joined.
-
Adams Gravitis joined.
-
Wendell Baker (Yahoo Holdings Inc.) joined.
-
Zixuan Chen joined.
-
-
3 participants left.
-
Alex Preukschat (Evernym) left.
-
Wendell Baker (Yahoo Holdings Inc.) left.
-
Andy Seaborne (Apache Software Foundation) left.
-
-
3 organizations joined.
-
Chunghwa Telecom Company, Ltd. joined.
-
University of Southern California joined.
-
Yahoo Holdings Inc. joined.
-
GitHub
solid/specification
-
6 issues opened.
-
Storage provisioning solid/specification#317, by @csarven.
-
Define creator solid/specification#315, by @csarven.
-
How to use the WAC-Allow header on auxiliary resources? solid/specification#313, by @RubenVerborgh.
-
Security considerations for status codes solid/specification#311, by @csarven.
-
Discovery of storage solid/specification#310, by @kjetilk.
-
Prefixes for Solid specs solid/specification#308, by @csarven.
-
-
1 issue closed.
-
Determine the URIs for the specifications solid/specification#141.
-
-
20 issues received 131 new comments.
-
Specify container description solid/specification#227 (62 comments by @acoburn, @bblfish, @bourgeoa, @csarven, @elf-pavlik, @gibsonf1, @jeff-zucker, @justinwb, @kjetilk, @timbl)
-
Discovery of storage solid/specification#310 (21 comments by @acoburn, @csarven, @elf-pavlik, @kjetilk)
-
Storage provisioning solid/specification#317 (5 comments by @acoburn, @dmitrizagidulin, @elf-pavlik, @justinwb, @NSeydoux)
-
Define creator solid/specification#315 (5 comments by @bblfish, @dmitrizagidulin, @elf-pavlik, @justinwb)
-
Security considerations for status codes solid/specification#311 (5 comments by @csarven, @kjetilk, @timbl)
-
Clarify the notion and mechanisms for server-managed information solid/specification#177 (4 comments by @csarven, @kjetilk)
-
Append operations on RDF bearing resources solid/specification#305 (4 comments by @csarven, @kjetilk)
-
Does the protocol spec govern exact status codes? solid/specification#288 (3 comments by @jeff-zucker, @kjetilk)
-
How to use the WAC-Allow header on auxiliary resources? solid/specification#313 (2 comments by @csarven)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (1 comment by @kjetilk)
-
-
4 pull requests opened.
-
Update identifiers and describe specification requirements solid/specification#316, by @csarven.
-
W3C Solid Community Group meeting minutes template solid/specification#312, by @csarven.
-
Add that all RDF representations should represent the same graph solid/specification#309, by @kjetilk.
-
Add minutes from editorial sessions solid/specification#307, by @justinwb.
-
-
3 pull requests merged.
-
W3C Solid Community Group meeting minutes template solid/specification#312.
-
Update identifiers and describe specification requirements solid/specification#316.
-
Add minutes from editorial sessions solid/specification#307.
-
-
4 pull requests received 31 new comments.
-
Add that all RDF representations should represent the same graph solid/specification#309 (3 comments by @kjetilk, @RubenVerborgh)
-
Update identifiers and describe specification requirements solid/specification#316 (1 comment by @csarven)
Participants
-
1 participant joined.
-
Akshay Kanthi joined.
-
GitHub
solid/specification
-
4 issues opened.
-
Dimensions of Auxiliary Resource Types solid/specification#306, by @kjetilk.
-
Append operations on RDF bearing resources solid/specification#305, by @kjetilk.
-
deprecate wac:Control solid/specification#303, by @bblfish.
-
Slash semantics and conflicting requests on resource creation solid/specification#301, by @kjetilk.
-
-
2 issues closed.
-
Which LDP features are required by Solid solid/specification#39.
-
Act on the latest version of the resource state solid/specification#91.
-
-
1 issue reopened.
-
Which LDP features are required by Solid solid/specification#39, by @kjetilk.
-
-
12 issues received 38 new comments.
-
Specify container description solid/specification#227 (6 comments by @bblfish, @dmitrizagidulin, @jeff-zucker, @kjetilk)
-
Append operations on RDF bearing resources solid/specification#305 (6 comments by @csarven, @jeff-zucker, @kjetilk, @rubensworks)
-
Act on the latest version of the resource state solid/specification#91 (6 comments by @elf-pavlik, @kjetilk, @michielbdejong)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (3 comments by @csarven, @kjetilk)
-
Slash semantics and conflicting requests on resource creation solid/specification#301 (1 comment by @kjetilk)
-
Does the protocol spec govern exact status codes? solid/specification#288 (1 comment by @jeff-zucker)
-
-
6 pull requests opened.
-
Write methods as requirements solid/specification#304, by @kjetilk.
-
Add id attributes to server-side requirements that can be tested solid/specification#302, by @kjetilk.
-
Clarify 409 on containment triples solid/specification#298, by @RubenVerborgh.
-
Clarify that the required predicate for creation is acl:default solid/specification#297, by @RubenVerborgh.
-
Adjust URL for Solid-OIDC specification solid/specification#293, by @acoburn.
-
Put the If-None-Match: * requirement on the server solid/specification#292, by @kjetilk.
-
-
3 pull requests merged.
-
Add id attributes to server-side requirements that can be tested solid/specification#302.
-
Adjust URL for Solid-OIDC specification solid/specification#293.
-
Put the If-None-Match: * requirement on the server solid/specification#292.
-
-
1 pull request closed.
-
Clarify that the required predicate for creation is acl:default solid/specification#297.
-
-
8 pull requests received 23 new comments.
-
Write methods as requirements solid/specification#304 (5 comments by @acoburn, @csarven, @kjetilk, @pmcb55)
-
Add id attributes to server-side requirements that can be tested solid/specification#302 (5 comments by @acoburn, @csarven, @kjetilk)
-
Clarify 409 on containment triples solid/specification#298 (3 comments by @acoburn, @csarven, @kjetilk)
-
Trust between owners on same origin with multiple storages solid/specification#290 (3 comments by @acoburn, @elf-pavlik, @justinwb)
-
Add constraint discovery for client errors solid/specification#185 (3 comments by @csarven, @kjetilk)
-
Put the If-None-Match: * requirement on the server solid/specification#292 (2 comments by @csarven, @kjetilk)
-
Clarify that the required predicate for creation is acl:default solid/specification#297 (1 comment by @csarven)
-
Participants
-
6 participants joined.
-
Geongyu Bae (Sakak) joined.
-
James Randall (Department for Work and Pensions) joined.
-
bin ke joined.
-
lin ye joined.
-
Alessio Nobile joined.
-
Arijit Basu joined.
-
-
1 participant left.
-
Mike O'Neill (Baycloud Systems) left.
-
-
2 organizations joined.
-
Sakak joined.
-
Department for Work and Pensions joined.
-
-
1 organization left.
-
Baycloud Systems left.
-
GitHub
solid/specification
-
6 issues opened.
-
Quad support in Solid solid/specification#291, by @kjetilk.
-
Does the protocol spec govern exact status codes? solid/specification#288, by @RubenVerborgh.
-
Server management of data solid/specification#275, by @gford1000.
-
Ownership structure within a data pod solid/specification#274, by @gford1000.
-
Addition of Delegateable Owner solid/specification#273, by @gford1000.
-
Definition of Owner solid/specification#272, by @gford1000.
-
-
13 issues closed.
-
Assumptions around Disclosure of Sensitive Information in URIs solid/specification#142.
-
Should PUT-to-create c/r in existing container be allowed with only accessTo Write c/? solid/specification#246.
-
ACL Inheritance Algorithm problem solid/specification#257.
-
Clarify use of and requirement for acl:origin predicate solid/specification#59.
-
Which permissions are required for deleting a resource? solid/specification#197.
-
Clarify use of acl:default in the WebAC inheritance algorithm solid/specification#55.
-
acl:Authorization for multiple agents/targets solid/specification#251.
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193.
-
Can a non-default ACL apply to a child resource ? solid/specification#186.
-
Shape of ACL solid/specification#169.
-
Explain the ACL inheritance algorithm for clients solid/specification#106.
-
Does the acl:Authorization need to be materialized in an ACL resource solid/specification#57.
-
Clarify what happens with semantically invalid WebAC resources solid/specification#56.
-
-
25 issues received 46 new comments.
-
Level of SPARQL Update support solid/specification#125 (12 comments by @jeff-zucker, @joachimvh, @kjetilk, @rubensworks, @RubenVerborgh)
-
Does the protocol spec govern exact status codes? solid/specification#288 (5 comments by @acoburn, @csarven, @gibsonf1, @kjetilk)
-
What is the domain of the solid:owner relation? solid/specification#265 (3 comments by @csarven, @gibsonf1)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (2 comments by @kjetilk)
-
Should there be trust between owners when a server supports multiple storages on the same origin solid/specification#267 (2 comments by @kjetilk, @timbl)
-
Assumptions around Disclosure of Sensitive Information in URIs solid/specification#142 (1 comment by @timbl)
-
solid/specification#286 (1 comment by @RubenVerborgh)
-
solid/specification#283 (1 comment by @csarven)
-
If two URIs differ only in the trailing slash, what is the status code for the other one? solid/specification#219 (1 comment by @csarven)
-
Should PUT-to-create c/r in existing container be allowed with only accessTo Write c/? solid/specification#246 (1 comment by @csarven)
-
Clarify use of and requirement for acl:origin predicate solid/specification#59 (1 comment by @csarven)
-
Which permissions are required for deleting a resource? solid/specification#197 (1 comment by @csarven)
-
Clarify use of acl:default in the WebAC inheritance algorithm solid/specification#55 (1 comment by @csarven)
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193 (1 comment by @csarven)
-
Does the acl:Authorization need to be materialized in an ACL resource solid/specification#57 (1 comment by @csarven)
-
Clarify what happens with semantically invalid WebAC resources solid/specification#56 (1 comment by @csarven)
-
-
4 pull requests opened.
-
Trust between owners on same origin with multiple storages solid/specification#290, by @csarven.
-
Publish TR/wac solid/specification#284, by @csarven.
-
Editorial: update with the WAC spec as authoritative solid/specification#277, by @csarven.
-
Fix a defunct link to Shape Trees specification solid/specification#276, by @mrkvon.
-
-
3 pull requests merged.
-
Publish TR/wac solid/specification#284.
-
Editorial: update with the WAC spec as authoritative solid/specification#277.
-
Fix a defunct link to Shape Trees specification solid/specification#276.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant joined.
-
soonkuk kang joined.
-
GitHub
solid/specification
-
6 issues opened.
-
Auxillary Resources Hypermedia Idea solid/specification#270, by @kjetilk.
-
Firefox always uses heuristic freshness unless Cache-Control is given solid/specification#269, by @kjetilk.
-
(dup issue) The domain of solid:owner should be more open than Storage solid/specification#268, by @timbl.
-
Should there be trust between owners when a server supports multiple storages on the same origin solid/specification#267, by @justinwb.
-
Should the server always advertise the owner link relation? solid/specification#266, by @kjetilk.
-
What is the domain of the solid:owner relation? solid/specification#265, by @kjetilk.
-
-
5 issues closed.
-
WebSockets and HTTP/2 solid/specification#122.
-
Will WebSocket support be part of the Solid specification solid/specification#50.
-
(dup issue) The domain of solid:owner should be more open than Storage solid/specification#268.
-
Should it be possible to find controller of storage via resources? solid/specification#153.
-
Establish versioned or living standard model for specs solid/specification#8.
-
-
16 issues received 51 new comments.
-
Should the server always advertise the owner link relation? solid/specification#266 (14 comments by @csarven, @d-a-v-i--, @justinwb, @kjetilk, @timbl)
-
Should there be trust between owners when a server supports multiple storages on the same origin solid/specification#267 (6 comments by @csarven, @d-a-v-i--, @kjetilk)
-
Level of SPARQL Update support solid/specification#125 (5 comments by @justinwb, @kjetilk, @rubensworks, @RubenVerborgh)
-
Enable full use of relative URLs in Solid solid/specification#194 (5 comments by @bblfish, @kjetilk)
-
Will WebSocket support be part of the Solid specification solid/specification#50 (1 comment by @timbl)
-
If two URIs differ only in the trailing slash, what is the status code for the other one? solid/specification#219 (1 comment by @kjetilk)
-
(dup issue) The domain of solid:owner should be more open than Storage solid/specification#268 (1 comment by @timbl)
-
Clarify what happens with semantically invalid WebAC resources solid/specification#56 (1 comment by @kjetilk)
-
Does the acl:Authorization need to be materialized in an ACL resource solid/specification#57 (1 comment by @kjetilk)
-
Establish versioned or living standard model for specs solid/specification#8 (1 comment by @kjetilk)
-
-
1 pull request opened.
-
Update notification-protocol-data-flows.md solid/specification#271, by @emmettownsend.
-
-
2 pull requests merged.
-
Update notification-protocol-data-flows.md solid/specification#271.
-
Add notion of "owner" and requirements solid/specification#264.
-
-
2 pull requests closed.
-
Add server Cache-Control requirement forcing revalidation solid/specification#254.
-
Break lines at column 100 solid/specification#261.
-
-
4 pull requests received 10 new comments.
-
Add notion of "owner" and requirements solid/specification#264 (6 comments by @csarven, @justinwb, @kjetilk)
-
Remove server requirement to advertise container type in HTTP header solid/specification#190 (2 comments by @kjetilk, @TallTed)
-
Add server Cache-Control requirement forcing revalidation solid/specification#254 (1 comment by @kjetilk)
-
Participants
-
3 participants joined.
-
Timea Turdean (Inrupt Inc.) joined.
-
Sheff Engi joined.
-
Wim Tobback (Cronos Groep NV) joined.
-
-
1 participant left.
-
Benjamin Goering left.
-
-
1 organization joined.
-
Cronos Groep NV joined.
-
GitHub
solid/specification
-
2 issues opened.
-
can LDP let a client know that it does not support PUT on creation? solid/specification#262, by @bblfish.
-
Language and aref hooks for other specs solid/specification#260, by @kjetilk.
-
-
1 issue closed.
-
Why is defaultForNew deprecated? solid/specification#258.
-
-
14 issues received 30 new comments.
-
can LDP let a client know that it does not support PUT on creation? solid/specification#262 (6 comments by @bblfish, @csarven, @kjetilk)
-
Which permissions are required for deleting an ACL document? solid/specification#145 (3 comments by @csarven, @kjetilk)
-
Is support for Prefer headers required by Solid? solid/specification#48 (3 comments by @kjetilk, @RubenVerborgh)
-
Need clear specifications of POD access and usage controls solid/specification#180 (1 comment by @kjetilk)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (1 comment by @michielbdejong)
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193 (1 comment by @michielbdejong)
-
Should PUT-to-create c/r in existing container be allowed with only accessTo Write c/? solid/specification#246 (1 comment by @michielbdejong)
-
-
3 pull requests opened.
-
Add notion of "owner" and requirements solid/specification#264, by @csarven.
-
Make resource creation more exact and testable solid/specification#263, by @RubenVerborgh.
-
Break lines at column 100 solid/specification#261, by @kjetilk.
-
-
1 pull request merged.
-
Make resource creation more exact and testable solid/specification#263.
-
-
3 pull requests received 66 new comments.
-
Add notion of "owner" and requirements solid/specification#264 (47 comments by @acoburn, @bblfish, @csarven, @elf-pavlik, @justinwb, @kidehen, @kjetilk, @matthieubosquet, @RubenVerborgh)
-
Break lines at column 100 solid/specification#261 (15 comments by @acoburn, @csarven, @kjetilk, @pmcb55)
-
Participants
-
9 participants joined.
-
Aaron Coburn (Inrupt Inc.) joined.
-
Kevin Weber (Airbnb Inc) joined.
-
Marco Neumann (KONA) joined.
-
Tory Clasen joined.
-
Maico Oliveira Buss joined.
-
Ricardo Usbeck joined.
-
Onur Yüksel joined.
-
Woods Denny joined.
-
Gary Murphy joined.
-
-
4 participants left.
-
Aaron Coburn (Inrupt Inc.) left.
-
Max Leonard (Inrupt Inc.) left.
-
Ricardo Usbeck left.
-
Gary Murphy left.
-
-
2 organizations joined.
-
Airbnb Inc joined.
-
KONA joined.
-
-
2 organizations left.
-
British Broadcasting Corporation left.
-
Hunch Manifest Inc left.
-
GitHub
solid/specification
-
5 issues opened.
-
how does one create an Access Control Resource? solid/specification#259, by @bblfish.
-
Why is defaultForNew deprecated? solid/specification#258, by @bblfish.
-
ACL Inheritance Algorithm problem solid/specification#257, by @bblfish.
-
Horizontal and Wide Reviews for Technical Reports solid/specification#256, by @csarven.
-
All new headers should be RFC8941 Structured Field Values solid/specification#255, by @bblfish.
-
-
9 issues received 14 new comments.
-
how does one create an Access Control Resource? solid/specification#259 (4 comments by @bblfish, @csarven)
-
Explain the ACL inheritance algorithm for clients solid/specification#106 (3 comments by @bblfish, @csarven)
-
All new headers should be RFC8941 Structured Field Values solid/specification#255 (1 comment by @bblfish)
-
Aligning representations of document and container resources with REST via single and compound state solid/specification#198 (1 comment by @kjetilk)
-
If two URIs differ only in the trailing slash, what is the status code for the other one? solid/specification#219 (1 comment by @kjetilk)
-
Does the Solid project have a set of stated architecture principles that are helping to guide the Specification? solid/specification#223 (1 comment by @kjetilk)
-
-
2 pull requests opened.
-
Add server Cache-Control requirement forcing revalidation solid/specification#254, by @csarven.
-
Add Inbox Discovery on Client Error solid/specification#253, by @csarven.
-
-
1 pull request merged.
-
Add security consideration about information exposure solid/specification#228.
-
-
3 pull requests received 67 new comments.
-
Add Inbox Discovery on Client Error solid/specification#253 (41 comments by @bblfish, @csarven, @kidehen, @matthieubosquet, @RubenVerborgh)
-
Add server Cache-Control requirement forcing revalidation solid/specification#254 (25 comments by @acoburn, @csarven, @kjetilk, @Vinnl)
-
Add security consideration about information exposure solid/specification#228 (1 comment by @csarven)
-
Participants
-
1 chair stepped down.
-
Philip Laszkowicz stepped down as a chair.
-
-
8 participants joined.
-
Jeeth Garageshwara (27th Cross LLC) joined.
-
Jeeth Garageshwara (27th Cross LLC) joined.
-
deb daniel joined.
-
Simon Grant (Cetis LLP) joined.
-
Wouter Kok joined.
-
Andrea Cimmino (Universidad Politécnica de Madrid) joined.
-
Víctor Rodríguez-Doncel (Universidad Politécnica de Madrid) joined.
-
James Birmingham joined.
-
-
2 participants left.
-
Jeeth Garageshwara (27th Cross LLC) left.
-
Alex Giurgiu left.
-
-
3 organizations joined.
-
27th Cross LLC joined.
-
Cetis LLP joined.
-
Universidad Politécnica de Madrid joined.
-
GitHub
solid/specification
-
3 issues opened.
-
acl:Authorization for multiple agents/targets solid/specification#251, by @tpluscode.
-
Should PUT-to-create c/r in existing container be allowed with only accessTo Write c/? solid/specification#246, by @michielbdejong.
-
Process list of disputes that CRUD and WAC tests uncovered solid/specification#245, by @michielbdejong.
-
-
4 issues closed.
-
Why MUST `/foo` and `/foo/` be the same ? solid/specification#242.
-
Which permissions are required for PUT to create? solid/specification#236.
-
Process list of disputes that CRUD and WAC tests uncovered solid/specification#245.
-
Require server ability to convert RDFa -> JSON-LD and RDFa -> Turtle? solid/specification#243.
-
-
13 issues received 49 new comments.
-
Make any deviation of SPARQL UPDATE explicit solid/specification#139 (15 comments by @acoburn, @justinwb, @kjetilk, @michielbdejong)
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193 (10 comments by @michielbdejong, @TallTed, @timbl, @Vinnl)
-
Should PUT-to-create c/r in existing container be allowed with only accessTo Write c/? solid/specification#246 (4 comments by @csarven, @michielbdejong)
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217 (3 comments by @bblfish, @dmitrizagidulin)
-
Which permissions are required for PUT to create? solid/specification#236 (3 comments by @michielbdejong)
-
Standardizing state changes in resources (history, undo, sync) solid/specification#161 (3 comments by @gsvarovsky, @joepio, @TallTed)
-
acl:Authorization for multiple agents/targets solid/specification#251 (2 comments by @acoburn, @tpluscode)
-
Why MUST `/foo` and `/foo/` be the same ? solid/specification#242 (2 comments by @bblfish, @csarven)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (1 comment by @kjetilk)
-
Process list of disputes that CRUD and WAC tests uncovered solid/specification#245 (1 comment by @michielbdejong)
-
Require server ability to convert RDFa -> JSON-LD and RDFa -> Turtle? solid/specification#243 (1 comment by @michielbdejong)
-
-
4 pull requests opened.
-
Clarify discovery, reading, and writing auxiliary resources solid/specification#252, by @csarven.
-
reading of ACL resource should be reduced to requiring client to have Read rights. solid/specification#250, by @bblfish.
-
Allow ACL doc discovery without acl:Control solid/specification#248, by @michielbdejong.
-
Adjusted copy to site script to look at main rather than master solid/specification#247, by @jaxoncreed.
-
-
1 pull request merged.
-
Clarify discovery, reading, and writing auxiliary resources solid/specification#252.
-
-
3 pull requests closed.
-
reading of ACL resource should be reduced to requiring client to have Read rights. solid/specification#250.
-
Allow ACL doc discovery without acl:Control solid/specification#248.
-
Adjusted copy to site script to look at main rather than master solid/specification#247.
-
-
4 pull requests received 26 new comments.
-
Allow ACL doc discovery without acl:Control solid/specification#248 (16 comments by @bblfish, @csarven, @elf-pavlik, @justinwb, @michielbdejong, @RubenVerborgh, @TallTed)
-
reading of ACL resource should be reduced to requiring client to have Read rights. solid/specification#250 (4 comments by @bblfish, @csarven, @gibsonf1)
-
Clarify discovery, reading, and writing auxiliary resources solid/specification#252 (4 comments by @matthieubosquet, @TallTed)
-
Adjusted copy to site script to look at main rather than master solid/specification#247 (2 comments by @jaxoncreed)
-
Participants
-
15 participants joined.
-
Pete Edwards (Inrupt Inc.) joined.
-
Eamonn Costello joined.
-
diego pacheco (reconoser ID) joined.
-
Richard Marshall joined.
-
Zongyan Li joined.
-
Leonard Rosenthol (Adobe) joined.
-
Miguel Ceriani joined.
-
David Waite (Ping Identity) joined.
-
Carlo Tosoni joined.
-
Virginia Balseiro joined.
-
Billy Wilson Arante (Tuitt Philippines, Inc.) joined.
-
Bert Jehoul joined.
-
Michael Dundas joined.
-
Matthew Fowle joined.
-
Gordana Halavanja joined.
-
-
3 organizations joined.
-
reconoser ID joined.
-
Ping Identity joined.
-
Tuitt Philippines, Inc. joined.
-
GitHub
solid/specification
-
15 issues opened.
-
Use inclusive language in Solid technical reports solid/specification#244, by @csarven.
-
Require server ability to convert RDFa -> JSON-LD and RDFa -> Turtle? solid/specification#243, by @michielbdejong.
-
Why MUST `/foo` and `/foo/` be the same ? solid/specification#242, by @bblfish.
-
Is /foo != /foo/ ? solid/specification#240, by @bblfish.
-
Does acl:default imply acl:accessTo? solid/specification#239, by @michielbdejong.
-
PUT to overwrite with different Content-Type solid/specification#238, by @michielbdejong.
-
File system to Solid mapping solid/specification#237, by @bblfish.
-
Which permissions are required for PUT to create? solid/specification#236, by @michielbdejong.
-
OTW: SPS2003 XML Import-Export “Operation” Attribute - 8 content operations solid/specification#235, by @mwherman2000.
-
Dealing with non-matching DELETE+INSERT sparql-update solid/specification#234, by @michielbdejong.
-
Clarify container notifications for websockets-pubsub solid/specification#233, by @michielbdejong.
-
Header for create container with PUT solid/specification#232, by @bourgeoa.
-
PATCH to create solid/specification#231, by @michielbdejong.
-
Resource paging solid/specification#230, by @csarven.
-
Specify container description solid/specification#227, by @csarven.
-
-
9 issues closed.
-
Is /foo != /foo/ ? solid/specification#240.
-
Does acl:default imply acl:accessTo? solid/specification#239.
-
PUT to overwrite with different Content-Type solid/specification#238.
-
OTW: SPS2003 XML Import-Export “Operation” Attribute - 8 content operations solid/specification#235.
-
Clarify container notifications for websockets-pubsub solid/specification#233.
-
Dealing with non-matching DELETE+INSERT sparql-update solid/specification#234.
-
Header for create container with PUT solid/specification#232.
-
PATCH to create solid/specification#231.
-
WebID-TLS specification solid/specification#148.
-
-
20 issues received 110 new comments.
-
Specify container description solid/specification#227 (19 comments by @acoburn, @bblfish, @bourgeoa, @csarven, @gibsonf1, @jeff-zucker, @namedgraph, @NoelDeMartin)
-
Require server ability to convert RDFa -> JSON-LD and RDFa -> Turtle? solid/specification#243 (10 comments by @acoburn, @michielbdejong, @TallTed)
-
Which permissions are required for PUT to create? solid/specification#236 (9 comments by @acoburn, @csarven, @joachimvh, @michielbdejong)
-
Why MUST `/foo` and `/foo/` be the same ? solid/specification#242 (8 comments by @bblfish, @bourgeoa, @mwherman2000, @TallTed)
-
PUT to overwrite with different Content-Type solid/specification#238 (8 comments by @acoburn, @csarven, @joachimvh, @michielbdejong)
-
Clarify container notifications for websockets-pubsub solid/specification#233 (7 comments by @csarven, @michielbdejong)
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217 (7 comments by @bblfish, @rhiaro)
-
Decision: Access Rule with `acl:default` does not imply `acl:accessTo` solid/specification#193 (6 comments by @acoburn, @michielbdejong)
-
PATCH to create solid/specification#231 (5 comments by @acoburn, @bourgeoa, @csarven, @michielbdejong)
-
OTW: SPS2003 XML Import-Export “Operation” Attribute - 8 content operations solid/specification#235 (4 comments by @csarven, @mwherman2000)
-
Make any deviation of SPARQL UPDATE explicit solid/specification#139 (2 comments by @michielbdejong, @timbl)
-
Dealing with non-matching DELETE+INSERT sparql-update solid/specification#234 (2 comments by @acoburn, @michielbdejong)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (1 comment by @michielbdejong)
-
-
2 pull requests opened.
-
Fix typo in protocol.html solid/specification#241, by @TallTed.
-
Add security consideration about information exposure solid/specification#228, by @csarven.
-
-
1 pull request merged.
-
Fix typo in protocol.html solid/specification#241.
-
-
1 pull request received 8 new comments.
-
Add security consideration about information exposure solid/specification#228 (8 comments by @csarven, @d-a-v-i--, @justinwb, @RubenVerborgh, @TallTed)
-
Participants
-
24 participants joined.
-
Taekhoon Kim joined.
-
Fong An (日照鲜购电子商务有限公司) joined.
-
John Yu joined.
-
Andreas Prieß joined.
-
Pavlos Pseftoyiannis joined.
-
Lauernce Zhang joined.
-
Fredric Landqvist (Findwise) joined.
-
Pol Alvarez joined.
-
Jegan Davies-Jones joined.
-
Martin Tews joined.
-
Philippe Duchesne (Datavillage) joined.
-
Devaraj Muthuvelmanickam joined.
-
Christophe R Patraldo joined.
-
Syed Ali Raza Zaidi joined.
-
Santi Lozano joined.
-
Michael Herman joined.
-
Michael Paduch joined.
-
Kai Chen joined.
-
Marrelle Bailey (Inrupt Inc.) joined.
-
Rami Rustom joined.
-
Ashish S Sharma joined.
-
Ashish S Sharma joined.
-
Matthieu Bosquet joined.
-
Han Su joined.
-
-
1 participant left.
-
Ashish S Sharma left.
-
-
3 organizations joined.
-
日照鲜购电子商务有限公司 joined.
-
Findwise joined.
-
Datavillage joined.
-
GitHub
solid/specification
-
10 issues opened.
-
CORS proxy support solid/specification#226, by @csarven.
-
keep track of divergences with LDP solid/specification#224, by @bblfish.
-
Self-Sovereign Identity Model Principles: Identifier and Identity Data Usage Licensing solid/specification#222, by @mwherman2000.
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220, by @bourgeoa.
-
If two URIs differ only in the trailing slash, what is the status code for the other one? solid/specification#219, by @RubenVerborgh.
-
Cookie related security considerations for solid storage (RS) implementations solid/specification#218, by @elf-pavlik.
-
Management of github.io spec URLs after transition solid/specification#215, by @csarven.
-
cannot find reference to OWS in solid protocol document solid/specification#214, by @sideshowtom.
-
-
1 issue closed.
-
cannot find reference to OWS in solid protocol document solid/specification#214.
-
-
13 issues received 55 new comments.
-
Loss of Control Mitigation solid/specification#67 (21 comments by @csarven, @elf-pavlik, @gibsonf1, @RubenVerborgh)
-
Self-Sovereign Identity Model Principles: Identifier and Identity Data Usage Licensing solid/specification#222 (9 comments by @bblfish, @elf-pavlik, @justinwb, @mwherman2000)
-
Management of github.io spec URLs after transition solid/specification#215 (5 comments by @csarven, @elf-pavlik, @justinwb)
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217 (4 comments by @bblfish, @elf-pavlik, @mwherman2000)
-
Cookie related security considerations for solid storage (RS) implementations solid/specification#218 (4 comments by @acoburn, @elf-pavlik)
-
Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (3 comments by @acoburn, @csarven)
-
Discuss and align definitions of data pod, app, etc. solid/specification#16 (2 comments by @mwherman2000)
-
cannot find reference to OWS in solid protocol document solid/specification#214 (2 comments by @csarven)
-
Solid infrastructure for managing all my pods as well as pod-to-pod interlinks? [Support for Subsidiary Ledgers and Business Documents] solid/specification#221 (1 comment by @mwherman2000)
-
Indicate Solid protocol to the WebSocket interface solid/specification#163 (1 comment by @WhyINeedToFillUsername)
-
-
2 pull requests opened.
-
Update WAC-Allow access-modes syntax solid/specification#225, by @csarven.
-
Created automated push to site action solid/specification#216, by @jaxoncreed.
-
-
2 pull requests merged.
-
Update WAC-Allow access-modes syntax solid/specification#225.
-
Created automated push to site action solid/specification#216.
-
-
1 pull request received 6 new comments.