Solid Community Group - Activity in 2019
No matches.
GitHub
solid/specification
-
9 issues opened.
-
configurable redirecting and remapping solid/specification#136, by @elf-pavlik.
-
Document changelog from "roughly-0.8" to "Dec-2019" solid/specification#135, by @michielbdejong.
-
Gap Analysis of Milestone solid/specification#134, by @Mitzi-Laszlo.
-
Ensure the scope of this repository is accurate and clear to the public solid/specification#133, by @RubenVerborgh.
-
What happens if there is no ACL? solid/specification#130, by @csarven.
-
Does recursive container creation leak information? solid/specification#129, by @RubenVerborgh.
-
Clarify the heuristics to determine the interaction model if none is specified solid/specification#128, by @RubenVerborgh.
-
server-side author annotation solid/specification#127, by @michielbdejong.
-
What does a Write operation imply solid/specification#126, by @kjetilk.
-
-
1 issue closed.
-
server-side author annotation solid/specification#127.
-
-
1 issue reopened.
-
Document changelog from "roughly-0.8" to "Dec-2019" solid/specification#135, by @kjetilk.
-
-
31 issues received 168 new comments.
-
Specify/advise semantics of default Container resources (index.html/.ttl) solid/specification#69 (62 comments by @acoburn, @csarven, @elf-pavlik, @kjetilk, @TallTed)
-
Handling URIs with a path component ending with the same segment term solid/specification#107 (18 comments by @csarven, @elf-pavlik, @kjetilk, @TallTed)
-
Clarify the heuristics to determine the interaction model if none is specified solid/specification#128 (16 comments by @acoburn, @csarven, @kjetilk, @TallTed)
-
Specify semantics of resource creation via PUT solid/specification#40 (10 comments by @acoburn, @csarven, @kjetilk, @TallTed)
-
Gap Analysis of Milestone solid/specification#134 (8 comments by @csarven, @elf-pavlik, @kjetilk, @michielbdejong, @Mitzi-Laszlo)
-
Document changelog from "roughly-0.8" to "Dec-2019" solid/specification#135 (6 comments by @kjetilk, @michielbdejong)
-
Handling of resources which did not go through the HTTP interface solid/specification#119 (4 comments by @csarven, @kjetilk, @TallTed)
-
Methods for ACL resource creation solid/specification#42 (3 comments by @csarven, @justinwb, @kjetilk)
-
Ensure the scope of this repository is accurate and clear to the public solid/specification#133 (3 comments by @csarven, @RubenVerborgh)
-
Handling requests without an interaction model solid/specification#105 (3 comments by @csarven, @kjetilk, @RubenVerborgh)
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217 (2 comments by @csarven, @RubenVerborgh)
-
Resource creation behaviour when using the `Slug` header solid/specification#96 (2 comments by @csarven, @kjetilk)
-
Specify metadata mechanism for Containers, RDFResources, NonRDFResources solid/specification#63 (2 comments by @kjetilk)
-
Clarify the lifecycle of an ACL resource solid/specification#58 (2 comments by @csarven, @RubenVerborgh)
-
Clarify recursive container creation on POST, PATCH and PUT solid/specification#68 (2 comments by @csarven, @RubenVerborgh)
-
Does the acl:Authorization need to be materialized in an ACL resource solid/specification#57 (1 comment by @Otto-AA)
-
Recursive deletion of members on deletion of container solid/specification#132 (1 comment by @kjetilk)
-
Handling resources and updates with conflicting interaction models solid/specification#121 (1 comment by @RubenVerborgh)
-
Which LDP container types does a Solid server need to support solid/specification#47 (1 comment by @RubenVerborgh)
-
Which permissions are required for deleting an ACL document? solid/specification#145 (1 comment by @csarven)
-
Participants
-
1 participant joined.
-
Daniel Zuckerman joined.
-
-
1 organization joined.
-
Wallscope joined.
-
GitHub
solid/specification
-
16 issues opened.
-
Level of SPARQL Update support solid/specification#125, by @kjetilk.
-
Support for MS-Author-Via: SPARQL solid/specification#124, by @kjetilk.
-
Response headers solid/specification#123, by @csarven.
-
Handling resources and updates with conflicting interaction models solid/specification#121, by @kjetilk.
-
Mental model for resource lifecycle solid/specification#120, by @kjetilk.
-
Handling of resources which did not go through the HTTP interface solid/specification#119, by @csarven.
-
What does an append operation imply? solid/specification#118, by @kjetilk.
-
405 for "other" methods? solid/specification#117, by @kjetilk.
-
Specify container listing mechanism solid/specification#116, by @csarven.
-
Commitments to requests solid/specification#115, by @csarven.
-
Generalise error messages solid/specification#112, by @csarven.
-
Status messages for server errors solid/specification#111, by @csarven.
-
This repo - 'default' vs 'master' branches? solid/specification#110, by @dmitrizagidulin.
-
Representation URLs and interactions solid/specification#109, by @csarven.
-
Specify POST solid/specification#108, by @csarven.
-
Handling URIs with a path component ending with the same segment term solid/specification#107, by @csarven.
-
-
1 issue closed.
-
This repo - 'default' vs 'master' branches? solid/specification#110.
-
-
1 issue reopened.
-
Discuss returning 404 for privacy reasons solid/specification#14, by @csarven.
-
-
31 issues received 149 new comments.
-
Representation URLs and interactions solid/specification#109 (26 comments by @csarven, @dmitrizagidulin, @kjetilk, @mikeadams1, @RubenVerborgh)
-
Handling requests without an interaction model solid/specification#105 (11 comments by @acoburn, @csarven, @kjetilk)
-
Handling resources and updates with conflicting interaction models solid/specification#121 (10 comments by @csarven, @kjetilk)
-
Commitments to requests solid/specification#115 (8 comments by @acoburn, @csarven, @kjetilk, @michielbdejong)
-
Handling URIs with a path component ending with the same segment term solid/specification#107 (8 comments by @acoburn, @csarven, @kjetilk, @mikeadams1, @TallTed)
-
Discuss returning 404 for privacy reasons solid/specification#14 (7 comments by @csarven, @dmitrizagidulin, @kjetilk, @TallTed)
-
Which permissions are required for deleting a resource? solid/specification#197 (5 comments by @csarven, @kjetilk)
-
Specify/advise semantics of default Container resources (index.html/.ttl) solid/specification#69 (5 comments by @csarven, @JordanShurmer, @kjetilk, @mikeadams1)
-
Act on the latest version of the resource state solid/specification#91 (5 comments by @kjetilk, @michielbdejong)
-
Specify semantics of resource creation via PUT solid/specification#40 (3 comments by @csarven, @JordanShurmer, @kjetilk)
-
Mental model for resource lifecycle solid/specification#120 (3 comments by @csarven, @kjetilk, @TallTed)
-
Clarify recursive container creation on POST, PATCH and PUT solid/specification#68 (2 comments by @kjetilk)
-
Clarify use of acl:default in the WebAC inheritance algorithm solid/specification#55 (2 comments by @acoburn, @kjetilk)
-
This repo - 'default' vs 'master' branches? solid/specification#110 (2 comments by @dmitrizagidulin, @RubenVerborgh)
-
Should you be allowed to submit overlapping resource and container URIs? solid/specification#104 (2 comments by @csarven, @jaxoncreed)
-
Clarify use of and requirement for acl:origin predicate solid/specification#59 (1 comment by @kjetilk)
-
Is support for RFC7232 Conditional Requests mandatory? solid/specification#33 (1 comment by @JordanShurmer)
-
Handling of resources which did not go through the HTTP interface solid/specification#119 (1 comment by @kjetilk)
-
How does the server determine whether a resource is an ACL resource? solid/specification#31 (1 comment by @csarven)
-
2 pull requests opened.
-
Rename WebID-OIDC to Solid-OIDC. solid/specification#114, by @dmitrizagidulin.
-
Prep authentication spec skeleton. solid/specification#113, by @dmitrizagidulin.
-
-
1 pull request merged.
-
Prep authentication spec skeleton. solid/specification#113.
-
-
2 pull requests received 4 new comments.
-
Prep authentication spec skeleton. solid/specification#113 (3 comments by @dmitrizagidulin, @RubenVerborgh)
-
GitHub
solid/specification
-
18 issues opened.
-
Explain the ACL inheritance algorithm for clients solid/specification#106, by @RubenVerborgh.
-
Handling requests without an interaction model solid/specification#105, by @csarven.
-
Should you be allowed to submit overlapping resource and container URIs? solid/specification#104, by @jaxoncreed.
-
Use 410 Gone for deleted documents solid/specification#103, by @kjetilk.
-
Specify approach for resource meta-data solid/specification#102, by @justinwb.
-
Service providers should generate a WebID profile for the pod server [Implementation Guidance] solid/specification#100, by @dmitrizagidulin.
-
Is Solid containment strictly hierarchical? solid/specification#98, by @kjetilk.
-
Should it be possible to create orphan resources? solid/specification#97, by @kjetilk.
-
Resource creation behaviour when using the `Slug` header solid/specification#96, by @NSeydoux.
-
Stronger requirements on payload fields? solid/specification#95, by @kjetilk.
-
Does the 1.0 spec still require a File System representation? solid/specification#94, by @humont.
-
mkdir-p only for PUT or also for POST? solid/specification#93, by @michielbdejong.
-
Act on the latest version of the resource state solid/specification#91, by @michielbdejong.
-
Can one convert a non-container LDP-RS into an LDP-BC or vice versa? solid/specification#90, by @michielbdejong.
-
Specify mechanism for data portability solid/specification#88, by @justinwb.
-
Specify mechanism for data discovery solid/specification#87, by @justinwb.
-
Specify data validation with shapes solid/specification#86, by @justinwb.
-
Specify PATCH solid/specification#85, by @csarven.
-
-
4 issues closed.
-
Does the 1.0 spec still require a File System representation? solid/specification#94.
-
Stronger requirements on payload fields? solid/specification#95.
-
mkdir-p only for PUT or also for POST? solid/specification#93.
-
Should globbing be included as a server-side feature? solid/specification#64.
-
-
3 issues reopened.
-
Is Solid containment strictly hierarchical? solid/specification#98, by @kjetilk.
-
Is Solid containment strictly hierarchical? solid/specification#98, by @kjetilk.
-
Can one convert a non-container LDP-RS into an LDP-BC or vice versa? solid/specification#90, by @RubenVerborgh.
-
-
36 issues received 203 new comments.
-
Act on the latest version of the resource state solid/specification#91 (32 comments by @acoburn, @dmitrizagidulin, @kjetilk, @michielbdejong, @TallTed)
-
Content-Type MUST be used on all PUT/POST/PATCH requests? solid/specification#70 (22 comments by @acoburn, @csarven, @dmitrizagidulin, @kjetilk, @pmcb55, @TallTed)
-
Implementation guidance on ETags solid/specification#60 (19 comments by @acoburn, @csarven, @dmitrizagidulin, @kjetilk, @RubenVerborgh)
-
Add the semantics of slashes, which is shared by client and server solid/specification#35 (16 comments by @acoburn, @csarven, @dmitrizagidulin, @kjetilk, @pmcb55, @timbl)
-
Should it be possible to create orphan resources? solid/specification#97 (16 comments by @csarven, @dmitrizagidulin, @JordanShurmer, @kjetilk, @TallTed, @timbl)
-
Which LDP features are required by Solid solid/specification#39 (13 comments by @csarven, @dmitrizagidulin, @kjetilk, @RubenVerborgh, @TallTed)
-
Is Solid containment strictly hierarchical? solid/specification#98 (11 comments by @csarven, @dmitrizagidulin, @jaxoncreed, @JordanShurmer, @justinwb, @kjetilk)
-
Can one convert a non-container LDP-RS into an LDP-BC or vice versa? solid/specification#90 (10 comments by @acoburn, @csarven, @michielbdejong, @RubenVerborgh)
-
Stronger requirements on payload fields? solid/specification#95 (9 comments by @csarven, @elf-pavlik, @kjetilk, @RubenVerborgh)
-
Attenuated app authorization solid/specification#73 (9 comments by @csarven, @elf-pavlik, @jaxoncreed, @michielbdejong, @zenomt)
-
Which LDP container types does a Solid server need to support solid/specification#47 (4 comments by @csarven, @dmitrizagidulin, @kjetilk)
-
Does the 1.0 spec still require a File System representation? solid/specification#94 (4 comments by @humont, @RubenVerborgh)
-
Resource creation behaviour when using the `Slug` header solid/specification#96 (3 comments by @csarven, @kjetilk)
-
Is support for RFC7232 Conditional Requests mandatory? solid/specification#33 (3 comments by @csarven, @kjetilk)
-
Explain the ACL inheritance algorithm for clients solid/specification#106 (2 comments by @dmitrizagidulin, @kjetilk)
-
Specify mechanism for data portability solid/specification#88 (2 comments by @dmitrizagidulin, @kjetilk)
-
Clarify recursive container creation on POST, PATCH and PUT solid/specification#68 (2 comments by @kjetilk, @timbl)
-
mkdir-p only for PUT or also for POST? solid/specification#93 (2 comments by @csarven, @michielbdejong)
-
Should globbing be included as a server-side feature? solid/specification#64 (2 comments by @kjetilk, @RubenVerborgh)
-
How does the server determine whether a resource is an ACL resource? solid/specification#31 (1 comment by @kjetilk)
-
Service providers should generate a WebID profile for the pod server [Implementation Guidance] solid/specification#100 (1 comment by @justinwb)
-
Decide on a method of recording the creator of a resource solid/specification#66 (1 comment by @dmitrizagidulin)
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217 (1 comment by @dmitrizagidulin)
-
How does client apps know that certain ACL files cannot be deleted? solid/specification#37 (1 comment by @kjetilk)
-
Clarify use of acl:default in the WebAC inheritance algorithm solid/specification#55 (1 comment by @kjetilk)
-
-
4 pull requests opened.
-
Link to the new gitter chat for this repo solid/specification#99, by @JordanShurmer.
-
Update LICENSE.md solid/specification#89, by @TallTed.
-
Create LICENSE.md solid/specification#84, by @Mitzi-Laszlo.
-
Add Namespaces section solid/specification#83, by @csarven.
-
-
3 pull requests merged.
-
Link to the new gitter chat for this repo solid/specification#99.
-
Add Namespaces section solid/specification#83.
-
Create LICENSE.md solid/specification#84.
-
-
1 pull request received 2 new comments.
Participants
-
1 participant joined.
-
Kayode Ezike joined.
-
-
2 participants left.
-
Jackson Morgan (O.team) left.
-
Kayode Ezike left.
-
GitHub
solid/specification
-
33 issues opened.
-
Description of implications for end users solid/specification#82, by @Mitzi-Laszlo.
-
Attenuated app authorization solid/specification#73, by @michielbdejong.
-
Content-Type MUST be used on all PUT/POST/PATCH requests? solid/specification#70, by @kjetilk.
-
Specify/advise semantics of default Container resources (index.html/.ttl) solid/specification#69, by @dmitrizagidulin.
-
Clarify recursive container creation on POST, PATCH and PUT solid/specification#68, by @dmitrizagidulin.
-
Loss of Control Mitigation solid/specification#67, by @kjetilk.
-
Decide on a method of recording the creator of a resource solid/specification#66, by @dmitrizagidulin.
-
Proposal: server-protected metadata solid/specification#65, by @dmitrizagidulin.
-
Should globbing be included as a server-side feature? solid/specification#64, by @dmitrizagidulin.
-
Specify metadata mechanism for Containers, RDFResources, NonRDFResources solid/specification#63, by @dmitrizagidulin.
-
Container creation via PUT solid/specification#62, by @dmitrizagidulin.
-
Creation of Memento resources solid/specification#61, by @acoburn.
-
Implementation guidance on ETags solid/specification#60, by @acoburn.
-
Clarify use of and requirement for acl:origin predicate solid/specification#59, by @acoburn.
-
Clarify the lifecycle of an ACL resource solid/specification#58, by @acoburn.
-
Does the acl:Authorization need to be materialized in an ACL resource solid/specification#57, by @acoburn.
-
Clarify what happens with semantically invalid WebAC resources solid/specification#56, by @acoburn.
-
Clarify use of acl:default in the WebAC inheritance algorithm solid/specification#55, by @acoburn.
-
WebAC link relation header solid/specification#54, by @acoburn.
-
Will WebSocket support be part of the Solid specification solid/specification#50, by @acoburn.
-
What server-based notification support is required? solid/specification#49, by @acoburn.
-
Is support for Prefer headers required by Solid? solid/specification#48, by @acoburn.
-
Which LDP container types does a Solid server need to support solid/specification#47, by @acoburn.
-
Should a Solid server limit the reuse of URLs? solid/specification#46, by @acoburn.
-
Required RDF serializations for Solid solid/specification#45, by @acoburn.
-
ldp:constrainedBy recommendations solid/specification#44, by @acoburn.
-
What are the semantics of Accept-Post solid/specification#43, by @acoburn.
-
Methods for ACL resource creation solid/specification#42, by @acoburn.
-
Specify the semantics of DELETE solid/specification#41, by @acoburn.
-
Specify semantics of resource creation via PUT solid/specification#40, by @acoburn.
-
Which LDP features are required by Solid solid/specification#39, by @acoburn.
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217, by @dmitrizagidulin.
-
Project Proposal - Coordinating the Solid Specification solid/specification#38, by @justinwb.
-
-
1 issue closed.
-
Container creation via PUT solid/specification#62.
-
-
33 issues received 176 new comments.
-
Content-Type MUST be used on all PUT/POST/PATCH requests? solid/specification#70 (28 comments by @acoburn, @bblfish, @csarven, @kjetilk, @pmcb55, @RubenVerborgh, @TallTed)
-
Does the acl:Authorization need to be materialized in an ACL resource solid/specification#57 (15 comments by @acoburn, @pmcb55, @RubenVerborgh, @timbl)
-
Creation of Memento resources solid/specification#61 (15 comments by @acoburn, @csarven, @hvdsomp, @pmcb55, @RubenVerborgh)
-
Clarify the lifecycle of an ACL resource solid/specification#58 (11 comments by @dmitrizagidulin, @jeff-zucker, @kjetilk, @pmcb55, @RubenVerborgh)
-
Project Proposal - Coordinating the Solid Specification solid/specification#38 (10 comments by @csarven, @dmitrizagidulin, @justinwb, @kjetilk, @michielbdejong, @RubenVerborgh)
-
Clarify use of acl:default in the WebAC inheritance algorithm solid/specification#55 (9 comments by @acoburn, @bourgeoa, @dmitrizagidulin, @kjetilk, @michielbdejong, @Otto-AA, @pmcb55, @timbl)
-
Proposal: Support Decentralized Identifiers (DIDs) in addition to Web IDs solid/specification#217 (8 comments by @creatinglake, @csarven, @dmitrizagidulin, @justinwb, @RubenVerborgh)
-
Attenuated app authorization solid/specification#73 (7 comments by @dmitrizagidulin, @michielbdejong, @RubenVerborgh)
-
Specify the semantics of DELETE solid/specification#41 (6 comments by @dmitrizagidulin, @kjetilk, @pmcb55, @RubenVerborgh)
-
Should a Solid server limit the reuse of URLs? solid/specification#46 (6 comments by @acoburn, @csarven, @RubenVerborgh)
-
Decide on a method of recording the creator of a resource solid/specification#66 (5 comments by @acoburn, @elf-pavlik, @kjetilk, @pmcb55)
-
Specify semantics of resource creation via PUT solid/specification#40 (5 comments by @csarven, @dmitrizagidulin, @pmcb55)
-
Proposal: server-protected metadata solid/specification#65 (3 comments by @acoburn, @kjetilk, @pmcb55)
-
Will WebSocket support be part of the Solid specification solid/specification#50 (3 comments by @kjetilk, @RubenVerborgh)
-
What server-based notification support is required? solid/specification#49 (3 comments by @csarven, @dmitrizagidulin, @RubenVerborgh)
-
Should globbing be included as a server-side feature? solid/specification#64 (3 comments by @dmitrizagidulin, @justinwb, @RubenVerborgh)
-
Clarify recursive container creation on POST, PATCH and PUT solid/specification#68 (2 comments by @acoburn, @dmitrizagidulin)
-
Which LDP container types does a Solid server need to support solid/specification#47 (2 comments by @pmcb55, @RubenVerborgh)
-
Is support for Prefer headers required by Solid? solid/specification#48 (2 comments by @pmcb55, @TallTed)
-
Establish versioned or living standard model for specs solid/specification#8 (2 comments by @csarven, @kjetilk)
-
Specify metadata mechanism for Containers, RDFResources, NonRDFResources solid/specification#63 (1 comment by @jeff-zucker)
-
How does the server determine whether a resource is an ACL resource? solid/specification#31 (1 comment by @csarven)
-
Clarify use of and requirement for acl:origin predicate solid/specification#59 (1 comment by @elf-pavlik)
-
How does client apps know that certain ACL files cannot be deleted? solid/specification#37 (1 comment by @megoth)
-
Participants
-
6 participants joined.
-
Aron Homberg joined.
-
Travis Vachon joined.
-
Mark Senefsky joined.
-
Mark Thompson joined.
-
Jackson Morgan (O.team) joined.
-
Noel De Martin joined.
-
-
1 organization joined.
-
Argu joined.
-
GitHub
solid/specification
-
12 issues opened.
-
How does client apps know that certain ACL files cannot be deleted? solid/specification#37, by @megoth.
-
Specify kind of actors and class of interactions solid/specification#36, by @csarven.
-
Document the WAC-Allow header in the spec. solid/specification#181, by @timbl.
-
Add the semantics of slashes, which is shared by client and server solid/specification#35, by @RubenVerborgh.
-
Add specification for filesystem portability solid/specification#34, by @RubenVerborgh.
-
Is support for RFC7232 Conditional Requests mandatory? solid/specification#33, by @RubenVerborgh.
-
How does the server determine whether a resource is an ACL resource? solid/specification#31, by @RubenVerborgh.
-
what is the scope of the Solid spec? solid/specification#29, by @Mitzi-Laszlo.
-
Structured Error Messages solid/specification#28, by @kjetilk.
-
Determine HTTP to HTTPS upgrade mechanism solid/specification#27, by @kjetilk.
-
Express "identifiable information" (non)normatively solid/specification#25, by @csarven.
-
Add ability to query resource access activity solid/specification#24, by @justinwb.
-
-
1 issue closed.
-
Write CORS section solid/specification#12.
-
-
10 issues received 55 new comments.
-
How does the server determine whether a resource is an ACL resource? solid/specification#31 (12 comments by @acoburn, @justinwb, @kjetilk, @michielbdejong, @pmcb55, @timbl)
-
How does client apps know that certain ACL files cannot be deleted? solid/specification#37 (10 comments by @csarven, @dmitrizagidulin, @kjetilk, @megoth, @RubenVerborgh)
-
Structured Error Messages solid/specification#28 (7 comments by @acoburn, @csarven, @kjetilk, @Mitzi-Laszlo, @RubenVerborgh)
-
what is the scope of the Solid spec? solid/specification#29 (6 comments by @csarven, @Mitzi-Laszlo, @RubenVerborgh)
-
Is support for RFC7232 Conditional Requests mandatory? solid/specification#33 (5 comments by @kjetilk, @michielbdejong)
-
Is WAC-Allow part of the solid spec? solid/specification#170 (3 comments by @csarven, @RubenVerborgh)
-
Document the WAC-Allow header in the spec. solid/specification#181 (3 comments by @RubenVerborgh, @timbl)
-
Determine HTTP to HTTPS upgrade mechanism solid/specification#27 (3 comments by @acoburn, @elf-pavlik, @RubenVerborgh)
-
Add ability to query resource access activity solid/specification#24 (3 comments by @csarven, @justinwb, @RubenVerborgh)
-
-
1 pull request opened.
-
Add HTTP section solid/specification#26, by @RubenVerborgh.
-
-
2 pull requests merged.
-
Add HTTP section solid/specification#26.
-
Add CORS section solid/specification#13.
-
-
2 pull requests received 90 new comments.
-
Add CORS section solid/specification#13 (57 comments by @csarven, @justinwb, @kjetilk, @michielbdejong, @RubenVerborgh, @TallTed)
-
Add HTTP section solid/specification#26 (33 comments by @csarven, @dmitrizagidulin, @justinwb, @kjetilk, @RubenVerborgh, @TallTed)
-
Participants
-
1 participant left.
-
Dakota Gravitt left.
-
-
1 organization joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
-
1 organization left.
-
popokotea left.
-
GitHub
solid/specification
-
17 issues opened.
-
Add URI Normalization solid/specification#22, by @kjetilk.
-
Discuss security considerations for fetching and processing external documents solid/specification#21, by @RubenVerborgh.
-
Proposal: Support COPY use case solid/specification#19, by @dmitrizagidulin.
-
Clarify Solid supports a subset of LDP solid/specification#18, by @dmitrizagidulin.
-
Resource Versioning solid/specification#280, by @csarven.
-
Mutable and immutable resources solid/specification#279, by @csarven.
-
Discuss and align definitions of data pod, app, etc. solid/specification#16, by @RubenVerborgh.
-
Using 'Pod' consistently throughout all documentation? solid/specification#15, by @pmcb55.
-
Discuss returning 404 for privacy reasons solid/specification#14, by @RubenVerborgh.
-
Write CORS section solid/specification#12, by @RubenVerborgh.
-
PUT RDFa, then GET turtle solid/specification#195, by @michielbdejong.
-
Document requirements to add, remove, update normative spec items solid/specification#10, by @csarven.
-
Associate each spec with a Use Cases and Requirements document solid/specification#9, by @csarven.
-
Establish versioned or living standard model for specs solid/specification#8, by @csarven.
-
Add that a pod server MAY be an Identity Provider solid/specification#7, by @RubenVerborgh.
-
Spec authoring in plain HTML+RDFa solid/specification#6, by @csarven.
-
Comment on proposed specification document structure solid/specification#5, by @RubenVerborgh.
-
-
5 issues closed.
-
Using 'Pod' consistently throughout all documentation? solid/specification#15.
-
Comment on proposed specification document structure solid/specification#5.
-
Clarify Solid supports a subset of LDP solid/specification#18.
-
Assign editors to this specification solid/specification#2.
-
Decide on a process for editing this specification solid/specification#1.
-
-
14 issues received 118 new comments.
-
PUT RDFa, then GET turtle solid/specification#195 (32 comments by @acoburn, @csarven, @dmitrizagidulin, @elf-pavlik, @RubenVerborgh, @Ryuno-Ki, @TallTed)
-
Proposal: Support COPY use case solid/specification#19 (17 comments by @acoburn, @dmitrizagidulin, @elf-pavlik, @RubenVerborgh, @TallTed)
-
Spec authoring in plain HTML+RDFa solid/specification#6 (17 comments by @acoburn, @csarven, @elf-pavlik, @kjetilk, @RubenVerborgh)
-
Comment on proposed specification document structure solid/specification#5 (13 comments by @acoburn, @csarven, @dmitrizagidulin, @justinwb, @kjetilk, @maxidorius)
-
Discuss and align definitions of data pod, app, etc. solid/specification#16 (11 comments by @csarven, @dmitrizagidulin, @elf-pavlik, @justinwb, @kjetilk)
-
Discuss returning 404 for privacy reasons solid/specification#14 (7 comments by @csarven, @dmitrizagidulin, @humont, @TallTed)
-
Using 'Pod' consistently throughout all documentation? solid/specification#15 (5 comments by @csarven, @kjetilk, @RubenVerborgh)
-
Establish versioned or living standard model for specs solid/specification#8 (5 comments by @csarven, @justinwb, @kjetilk, @RubenVerborgh)
-
Mutable and immutable resources solid/specification#279 (3 comments by @csarven, @elf-pavlik, @RubenVerborgh)
-
Discuss security considerations for fetching and processing external documents solid/specification#21 (2 comments by @acoburn, @dmitrizagidulin)
-
Associate each spec with a Use Cases and Requirements document solid/specification#9 (2 comments by @csarven, @justinwb)
-
-
2 pull requests opened.
-
Explain migration is still in progress solid/specification#17, by @michielbdejong.
-
Add CORS section solid/specification#13, by @RubenVerborgh.
-
-
1 pull request merged.
-
Explain migration is still in progress solid/specification#17.
-
-
2 pull requests received 42 new comments.
-
Add CORS section solid/specification#13 (39 comments by @acoburn, @csarven, @dmitrizagidulin, @justinwb, @kjetilk, @pmcb55, @RubenVerborgh)
-
Explain migration is still in progress solid/specification#17 (3 comments by @michielbdejong, @Mitzi-Laszlo, @RubenVerborgh)
-
Participants
-
2 participants joined.
-
Sylvain Saint-André joined.
-
Christine Perey joined.
-
-
2 participants left.
-
Timothy Holborn left.
-
Alexander Castro Romero left.
-
-
2 organizations joined.
-
Fundacion CTIC joined.
-
Fraunhofer Gesellschaft joined.
-
GitHub
solid/specification
-
4 issues opened.
-
Which permissions are required for deleting an ACL document? solid/specification#145, by @RubenVerborgh.
-
Which permissions are required for deleting a resource? solid/specification#197, by @RubenVerborgh.
-
Conformance critieria for headers with multiple field values solid/specification#71, by @kjetilk.
-
Recursive deletion of members on deletion of container solid/specification#132, by @fabiancook.
-
-
3 issues received 18 new comments.
-
Recursive deletion of members on deletion of container solid/specification#132 (15 comments by @acoburn, @akuckartz, @bourgeoa, @fabiancook, @kjetilk, @michielbdejong, @RubenVerborgh)
-
Conformance critieria for headers with multiple field values solid/specification#71 (2 comments by @kjetilk, @RubenVerborgh)
-
Which permissions are required for deleting an ACL document? solid/specification#145 (1 comment by @michielbdejong)
-
Participants
-
2 participants joined.
-
Yehua Chen joined.
-
Paul Worrall joined.
-
-
2 participants left.
-
Ricardo Usbeck left.
-
Aaron Coburn (Inrupt Inc.) left.
-
-
3 organizations joined.
-
Wageningen University joined.
-
Adobe joined.
-
Iron Horse Software, LLC joined.
-
GitHub
solid/specification
-
4 issues opened.
-
Assign editors to this specification solid/specification#2, by @RubenVerborgh.
-
Decide on a process for editing this specification solid/specification#1, by @RubenVerborgh.
-
Is WAC-Allow part of the solid spec? solid/specification#170, by @Otto-AA.
-
Identity as a Bargaining Chip solid/specification#354, by @Mitzi-Laszlo.
-
-
3 issues received 20 new comments.
-
Assign editors to this specification solid/specification#2 (10 comments by @HelloFillip, @justinwb, @kjetilk, @michielbdejong, @Mitzi-Laszlo)
-
Identity as a Bargaining Chip solid/specification#354 (6 comments by @megoth, @michielbdejong, @Mitzi-Laszlo, @RubenVerborgh)
-
Decide on a process for editing this specification solid/specification#1 (4 comments by @Mitzi-Laszlo)
-
-
1 pull request opened.
-
Update README.md solid/specification#4, by @Mitzi-Laszlo.
-
-
1 pull request merged.
-
Update README.md solid/specification#4.
-
Participants
-
9 participants joined.
-
Raúl R. Pearson joined.
-
Sina Bahram joined.
-
Sébastien Dubois joined.
-
Matthias Evering joined.
-
Mark Weiler joined.
-
Jon Pederson joined.
-
Gregg Kellogg joined.
-
Philipp Gfeller joined.
-
Elettra Bietti joined.
-
Participants
-
14 participants joined.
-
david mason joined.
-
Armando Ramos joined.
-
Christian Buggedei joined.
-
Daphne Muller joined.
-
Takeo Nishikata (Massachusetts Institute of Technology (MIT)) joined.
-
Chris Min joined.
-
Thomas Gallagher joined.
-
Teodora Petkova joined.
-
Tom Millross joined.
-
Khalid Alnuaim joined.
-
Jeff Zucker joined.
-
Benjamin Goering joined.
-
Alex Giurgiu joined.
-
Eric Prud'hommeaux joined.
-
-
2 participants left.
-
david mason left.
-
Giulio Moretto left.
-
-
6 organizations joined.
-
Startin'blox joined.
-
Fedict - Federal Public Service ICT joined.
-
WU (Wirschaftsuniversität Wien) - Vienna University of Economics and Business joined.
-
Evernym joined.
-
Reihoo joined.
-
OpenInc joined.
-
Participants
-
5 participants joined.
-
Alexander Castro Romero joined.
-
Eduardo Ibacache Rodriguez joined.
-
Mike Adams joined.
-
david mason joined.
-
Alain Bourgeois joined.
-
-
1 participant left.
-
Markus Sabadello left.
-
-
1 organization joined.
-
Inrupt Inc. joined.
-
Participants
-
3 participants joined.
-
Sarven Capadisli joined.
-
Alexandre Bourlier joined.
-
Dakota Gravitt joined.
-
-
1 organization joined.
-
Werk7 joined.
-
GitHub
solid/specification
-
2 issues opened.
-
Create Solid Spec Test Suite solid/specification#281, by @csarven.
-
Include conformance criteria for Solid spec solid/specification#282, by @csarven.
-
-
1 issue received 1 new comment.