Security Interest Group - Activity in 2024
No matches.
Participants
-
12 participants joined.
-
Xu Lin (W3C Invited Experts) joined.
-
Amir Sharif (Fondazione Bruno Kessler) joined.
-
Greg Bernstein (W3C Invited Experts) joined.
-
Sebastian Crane (W3C Invited Experts) joined.
-
Thomas Jones (W3C Invited Experts) joined.
-
Danja Vasiliev (Dyne.org) joined.
-
Artur Janc (Google LLC) joined.
-
Joe DeBlasio (Google LLC) joined.
-
Emily Stark (Google LLC) joined.
-
Samuel Schlesinger (Google LLC) joined.
-
Jeffrey Yasskin (Google LLC) joined.
-
Paul Ziv (Conexxus) joined.
-
-
2 organizations joined.
-
Google LLC joined.
-
Conexxus joined.
-
GitHub
w3c/securityig
-
1 issue opened.
-
Define a good time for the group call w3c/securityig#4, by @simoneonofri.
-
-
2 pull requests opened.
-
Add details about deliverables to 2024-12-18-agenda.md w3c/securityig#3, by @jyasskin.
-
Update SECURITY.md w3c/securityig#2, by @simoneonofri.
-
-
2 pull requests merged.
-
Add details about deliverables to 2024-12-18-agenda.md w3c/securityig#3.
-
Update SECURITY.md w3c/securityig#2.
-
w3c/security-questionnaire
-
1 issue closed.
-
use automatic publishing w3c/security-questionnaire#101.
-
-
2 pull requests merged.
-
Add auto-publish script w3c/security-questionnaire#171.
-
Create w3c.json w3c/security-questionnaire#179.
-
-
1 pull request received 3 new comments.
Lifecycle
-
1 charter started.
-
Chartered until 18 November 2026. Participants had to rejoin under this charter.
-
Participants
-
3 chairs appointed.
-
Tommaso Innocenti became a chair.
-
Patrick Schaller became a chair.
-
Denis Roio became a chair.
-
-
1 Team contact appointed.
-
Simone Onofri became a Team contact.
-
-
19 participants joined.
-
eugenio kim cerra (W3C Invited Experts) joined.
-
Sylvia Cadena (W3C) joined.
-
Veronica Cristiano (W3C Invited Experts) joined.
-
Yen-Lin Huang (Ministry of Digital Affairs, Taiwan) joined.
-
Joaquin Salvachua (Universidad Politécnica de Madrid) joined.
-
Shigeya Suzuki (Keio University) joined.
-
Michael Prorock (Tradeverifyd) joined.
-
Benjamin Young (Digital Bazaar) joined.
-
Wesley Smith (Digital Bazaar) joined.
-
Dave Longley (Digital Bazaar) joined.
-
David Lehn (Digital Bazaar) joined.
-
Manu Sporny (Digital Bazaar) joined.
-
Tommaso Innocenti (Amazon) joined.
-
Patrick Schaller (ETH Zurich) joined.
-
Eric Schuh (Legendary Requirements) joined.
-
Kevin Dean (Legendary Requirements) joined.
-
Joe Andrieu (Legendary Requirements) joined.
-
Denis Roio (Dyne.org) joined.
-
Simone Onofri (W3C) joined.
-
-
8 organizations joined.
-
Universidad Politécnica de Madrid joined.
-
Keio University joined.
-
Ministry of Digital Affairs, Taiwan joined.
-
Tradeverifyd joined.
-
Digital Bazaar joined.
-
ETH Zurich joined.
-
Legendary Requirements joined.
-
Dyne.org joined.
-
GitHub
w3c/securityig
-
1 pull request opened.
-
Minor tweaks w3c/securityig#1, by @plehegar.
-
-
1 pull request merged.
-
Minor tweaks w3c/securityig#1.
-
w3c/security-questionnaire
-
1 issue opened.
-
There are three active versions of this questionnaire w3c/security-questionnaire#175, by @domenic.
-
-
2 issues received 3 new comments.
-
Questionnaire markdown file is not actually convenient w3c/security-questionnaire#172 (2 comments by @domenic, @johannhof)
-
There are three active versions of this questionnaire w3c/security-questionnaire#175 (1 comment by @jyasskin)
-
-
4 pull requests opened.
-
Create w3c.json w3c/security-questionnaire#179, by @plehegar.
-
Link to Lukasz' specific analysis on visited links. w3c/security-questionnaire#178, by @jyasskin.
-
Make questionnaire.markdown convenient for copying into an explainer. w3c/security-questionnaire#177, by @jyasskin.
-
Add `class=question` to a header so it's included in questionnaire.markdown. w3c/security-questionnaire#176, by @jyasskin.
-
-
1 pull request closed.
-
Switch the CI to spec-prod, and enable it for PR validation. w3c/security-questionnaire#169.
-
-
4 pull requests received 8 new comments.
-
Add auto-publish script w3c/security-questionnaire#171 (5 comments by @jyasskin, @pes10k, @plehegar)
-
Link to Lukasz' specific analysis on visited links. w3c/security-questionnaire#178 (1 comment by @lflores-ms)
-
Switch the CI to spec-prod, and enable it for PR validation. w3c/security-questionnaire#169 (1 comment by @jyasskin)
-
GitHub
w3c/security-questionnaire
-
2 issues opened.
-
Example 10 is not supported by referenced article w3c/security-questionnaire#174, by @lflores-ms.
-
This questionnaire should ask about SecureContext restrictions w3c/security-questionnaire#173, by @domenic.
-
GitHub
w3c/security-questionnaire
-
2 issues opened.
-
Questionnaire markdown file is not actually convenient w3c/security-questionnaire#172, by @johannhof.
-
Remove or update the PDF viewer plugin objects list example w3c/security-questionnaire#163, by @jyasskin.
-
-
9 pull requests opened.
-
Add auto-publish script w3c/security-questionnaire#171, by @plehegar.
-
Don't describe this document as having conformance requirements, using the RFC2119 keywords, or having algorithms. w3c/security-questionnaire#170, by @jyasskin.
-
Switch the CI to spec-prod, and enable it for PR validation. w3c/security-questionnaire#169, by @jyasskin.
-
Copy-edit the AT section. w3c/security-questionnaire#168, by @jyasskin.
-
Fix uses of "effect" that should "affect" things. w3c/security-questionnaire#167, by @jyasskin.
-
Make the two non-fully-active questions adjacent. w3c/security-questionnaire#166, by @jyasskin.
-
Fix a claim that disconnecting an iframe causes it to load a document. w3c/security-questionnaire#165, by @jyasskin.
-
Improve the link to Web Bluetooth privacy considerations w3c/security-questionnaire#164, by @jyasskin.
-
Remove a misplaced period. w3c/security-questionnaire#162, by @jyasskin.
-
-
4 pull requests merged.
-
Make the two non-fully-active questions adjacent. w3c/security-questionnaire#166.
-
Fix a claim that disconnecting an iframe causes it to load a document. w3c/security-questionnaire#165.
-
Improve the link to Web Bluetooth privacy considerations w3c/security-questionnaire#164.
-
Remove a misplaced period. w3c/security-questionnaire#162.
-
-
1 pull request received 1 new comment.
-
Fix a claim that disconnecting an iframe causes it to load a document. w3c/security-questionnaire#165 (1 comment by @rakina)
-
GitHub
w3c/security-questionnaire
-
10 issues closed.
-
Explain how groups should address issues raised by the questionnaire in their specs w3c/security-questionnaire#88.
-
Is the User-Agent header field considered harmful? w3c/security-questionnaire#160.
-
Ask about dependencies and maturity of dependencies w3c/security-questionnaire#155.
-
Add question about whether new features allow for accessibility device use to be learned w3c/security-questionnaire#157.
-
cite design principle re: make private mode undetectable w3c/security-questionnaire#145.
-
a question or recommendations on error-handling w3c/security-questionnaire#137.
-
Mention (capability) negotiation? w3c/security-questionnaire#122.
-
The current questionnaire is very browser-centric w3c/security-questionnaire#116.
-
Add a section for preventing behaviours that are abusive toward users w3c/security-questionnaire#106.
-
'Hidden' data question needed? w3c/security-questionnaire#130.
-
-
7 issues received 8 new comments.
-
Explain how groups should address issues raised by the questionnaire in their specs w3c/security-questionnaire#88 (2 comments by @pes10k)
-
Is the User-Agent header field considered harmful? w3c/security-questionnaire#160 (1 comment by @hober)
-
Ask about dependencies and maturity of dependencies w3c/security-questionnaire#155 (1 comment by @pes10k)
-
Add question about whether new features allow for accessibility device use to be learned w3c/security-questionnaire#157 (1 comment by @hober)
-
The current questionnaire is very browser-centric w3c/security-questionnaire#116 (1 comment by @pes10k)
-
-
1 pull request opened.
-
add private browsing mode and design principals link w3c/security-questionnaire#161, by @pes10k.
-
-
4 pull requests merged.
-
add private browsing mode and design principals link w3c/security-questionnaire#161.
-
draft of error handling question, fixes #137 w3c/security-questionnaire#140.
-
New question on hidden metadata. w3c/security-questionnaire#138.
-
first draft of accessibility device section w3c/security-questionnaire#158.
-
-
2 pull requests received 3 new comments.
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
Is the User-Agent header field considered harmful? w3c/security-questionnaire#160, by @csarven.
-
-
1 pull request received 18 new comments.
-
first draft of accessibility device section w3c/security-questionnaire#158 (18 comments by @hober, @martinthomson)
-
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
Add question about whether new features allow for accessibility device use to be learned w3c/security-questionnaire#157, by @pes10k.
-
-
1 issue received 3 new comments.
-
Add question about whether new features allow for accessibility device use to be learned w3c/security-questionnaire#157 (3 comments by @hober, @pes10k)
-
-
2 pull requests opened.
-
fix the build. w3c/security-questionnaire#159, by @hober.
-
first draft of accessibility device section w3c/security-questionnaire#158, by @pes10k.
-
-
1 pull request merged.
-
fix the build. w3c/security-questionnaire#159.
-
-
1 pull request received 5 new comments.
-
first draft of accessibility device section w3c/security-questionnaire#158 (5 comments by @hober, @pes10k)
-