Social Web Working Group - Activity in 2016
No matches.
TR publications
-
2 documents published.
-
Activity Streams 2.0 published as a Candidate Recommendation Snapshot. History of Activity Streams 2.0
-
Activity Vocabulary published as a Candidate Recommendation Snapshot. History of Activity Vocabulary
-
GitHub
w3c/Micropub
-
2 issues opened.
-
Note that Location can be a plaintext property w3c/Micropub#66, by @dshanske.
-
Clarify the difference between points 3 & 6 of 2.1.3. w3c/Micropub#65, by @Zegnat.
-
w3c/websub
-
5 issues closed.
-
add CR exit criteria w3c/websub#56.
-
add conformance criteria w3c/websub#55.
-
[CR blocker] add Conformance Classes like Webmention has w3c/websub#8.
-
-
1 issue reopened.
-
Unilateral unsubscription notifications w3c/websub#16, by @aaronpk.
-
-
10 issues received 16 new comments.
-
Discovery: Limit HTML rel=hub links to <link> elements in <head> only. w3c/websub#67 (1 comment by @cweiske)
-
4 pull requests opened.
-
replace RFC3986 with WHATWG-URL w3c/websub#78, by @aaronpk.
-
Add exit criteria w3c/websub#77, by @aaronpk.
-
add conformance classes and criteria w3c/websub#76, by @aaronpk.
-
mentioning that <link> for discovery in HTML can only happen if prese… w3c/websub#75, by @julien51.
-
-
4 pull requests merged.
-
Add exit criteria w3c/websub#77.
-
add conformance classes and criteria w3c/websub#76.
-
Clarify requirement-level of Content-Type header w3c/websub#74.
-
-
3 pull requests received 5 new comments.
-
mentioning that <link> for discovery in HTML can only happen if prese… w3c/websub#75 (3 comments by @aaronpk, @julien51)
-
w3c/ldn
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add Fedora repository implementation w3c/ldn#62, by @acoburn.
-
Add Carbon LDP as implementation w3c/ldn#61, by @codyburleson.
-
-
2 pull requests merged.
-
Add Fedora repository implementation w3c/ldn#62.
-
Add Carbon LDP as implementation w3c/ldn#61.
-
w3c/webmention
-
1 issue opened.
-
4 issues closed.
-
web mentions for datasets with many URLs w3c/webmention#83.
-
JSON reference really needs to be to RFC 7159, not 4627 w3c/webmention#75.
-
-
1 issue reopened.
-
5 issues received 18 new comments.
-
[Editorial] Improve section 4.5 with specific mention of using CORS when retrieving target URLs w3c/webmention#84 (8 comments by @aaronpk, @hildjj, @sandhawke, @tantek)
-
web mentions for datasets with many URLs w3c/webmention#83 (6 comments by @aaronpk, @kevinmarks, @sandhawke)
-
likely editorial: loopback exception specifically about not sending to loopbacks w3c/webmention#71 (2 comments by @aaronpk)
-
[Non-normative] Add informative reference to Pingback, brief summary of FAQ in intro w3c/webmention#76 (1 comment by @aaronpk)
-
-
3 pull requests opened.
-
added note about republishing protected content w3c/webmention#87, by @aaronpk.
-
add note about sending webmentions from large datasets w3c/webmention#86, by @aaronpk.
-
add background with informative reference to Pingback w3c/webmention#85, by @aaronpk.
-
-
3 pull requests merged.
-
add note about sending webmentions from large datasets w3c/webmention#86.
-
add background with informative reference to Pingback w3c/webmention#85.
-
added note about republishing protected content w3c/webmention#87.
-
w3c/activitystreams
-
1 issue opened.
-
Weird sentence w3c/activitystreams#384, by @rhiaro.
-
-
8 issues closed.
-
Weird sentence w3c/activitystreams#384.
-
Note that namespace document has full extensions information w3c/activitystreams#379.
-
Unclear on why direct Object relationships (vs. Links) are useful w3c/activitystreams#364.
-
Default Language Context MAY -> SHOULD w3c/activitystreams#354.
-
Make sure examples using multiple vocabularies is up to date w3c/activitystreams#376.
-
Link to previous version's changelog from changelog w3c/activitystreams#378.
-
Context value as string, list or object w3c/activitystreams#377.
-
Update "name" examples that sound too much like autogenerated w3c/activitystreams#380.
-
-
1 issue reopened.
-
Weird sentence w3c/activitystreams#384, by @rhiaro.
-
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
Update context examples w3c/activitystreams#385, by @rhiaro.
-
Add dokieli implementation report w3c/activitystreams#383, by @csarven.
-
-
3 pull requests merged.
-
Update OA and PROV use in examples w3c/activitystreams#381.
-
Add dokieli implementation report w3c/activitystreams#383.
-
initial pass at social streams implementation report w3c/activitystreams#382.
-
-
1 pull request received 2 new comments.
w3c/activitypub
-
1 issue opened.
-
add JSON Web Signature ref. w3c/activitypub#172, by @PaulJeong14.
-
TR publications
-
7 documents published.
-
Webmention published as a Proposed Recommendation. History of Webmention
-
ActivityPub published as a Candidate Recommendation Snapshot. History of ActivityPub
-
Linked Data Notifications published as a Candidate Recommendation Snapshot. History of Linked Data Notifications
-
WebSub published as a Working Draft. History of WebSub
-
ActivityPub published as a Working Draft. History of ActivityPub
-
Social Web Protocols published twice as a Working Draft. History of Social Web Protocols
-
Participants
-
1 participant joined.
-
Aaron Parecki (Okta) joined.
-
-
1 participant left.
-
Aaron Parecki (Okta) left.
-
GitHub
w3c/websub
-
19 issues opened.
-
Redirections during (un)subscription POSTs to a hub w3c/websub#73, by @tonyg.
-
https://www.w3.org/TR/pubsub/ should redirect to .../websub/ w3c/websub#71, by @tonyg.
-
Drop MUST requirement for rel=self w3c/websub#69, by @cweiske.
-
Replace rel=self with rel=canonical w3c/websub#68, by @cweiske.
-
Discovery: Limit HTML rel=hub links to <link> elements in <head> only. w3c/websub#67, by @cweiske.
-
Discovery: "exact" URL w3c/websub#66, by @cweiske.
-
Change author section w3c/websub#57, by @julien51.
-
add CR exit criteria w3c/websub#56, by @aaronpk.
-
add conformance criteria w3c/websub#55, by @aaronpk.
-
Add link to test suite w3c/websub#54, by @aaronpk.
-
Resolving #43 and #36 w3c/websub#53, by @aaronpk.
-
Add CONTRIBUTING.md w3c/websub#52, by @julien51.
-
Updating previous subscriptions that have a hub.secret w3c/websub#47, by @aaronpk.
-
Discovery: minor wording change w3c/websub#44, by @aaronpk.
-
No connection between subscription request and verification from hub w3c/websub#43, by @aaronpk.
-
Subscription verification request is not authenticated/protected w3c/websub#42, by @aaronpk.
-
[CR blocker] link to test suite and implementation reports w3c/websub#41, by @tantek.
-
Drop .host-meta discovery if no known implementations w3c/websub#40, by @aaronpk.
-
-
29 issues closed.
-
Test hubs/feeds? w3c/websub#39.
-
Discovery: "exact" URL w3c/websub#66.
-
Content distribution: link header meanings w3c/websub#38.
-
[CR blocker] link to test suite and implementation reports w3c/websub#41.
-
https://www.w3.org/TR/pubsub/ should redirect to .../websub/ w3c/websub#71.
-
Drop MUST requirement for rel=self w3c/websub#69.
-
Add link to test suite w3c/websub#54.
-
Resolving #43 and #36 w3c/websub#53.
-
Drop .host-meta discovery if no known implementations w3c/websub#40.
-
Discovery inconsistency w3c/websub#37.
-
bad name choice (and there is evidence) w3c/websub#10.
-
Reference PubSubHubbub w3c/websub#11.
-
Use POST instead of GET for subscription denials w3c/websub#28.
-
Use of hub.secret to authenticate hub in more circumstances w3c/websub#36.
-
Change author section w3c/websub#57.
-
use subscription resource w3c/websub#20.
-
Unbounded lease duration w3c/websub#17.
-
Headers and signature validation w3c/websub#14.
-
Failed content distribution attempts w3c/websub#15.
-
Clarify whether fat pings are required or not w3c/websub#35.
-
Language/direction/localizability of error message w3c/websub#33.
-
algorithm names w3c/websub#21.
-
Validation: synchronous? w3c/websub#22.
-
consecutive version diff'ing w3c/websub#24.
-
Discovery: minor wording change w3c/websub#44.
-
Lease duration bounds w3c/websub#18.
-
[FPWD blocker] consider renaming the spec w3c/websub#5.
-
-
2 issues reopened.
-
Content distribution: link header meanings w3c/websub#38, by @julien51.
-
Document current state of interoperable content types w3c/websub#27, by @aaronpk.
-
-
31 issues received 114 new comments.
-
No connection between subscription request and verification from hub w3c/websub#43 (12 comments by @aaronpk, @julien51, @tonyg, @voxpelli)
-
Drop .host-meta discovery if no known implementations w3c/websub#40 (10 comments by @aaronpk, @akuckartz, @julien51, @pfefferle, @tantek)
-
Updating previous subscriptions that have a hub.secret w3c/websub#47 (7 comments by @julien51, @tonyg)
-
Document current state of interoperable content types w3c/websub#27 (7 comments by @aaronpk, @julien51, @sandhawke, @voxpelli)
-
bad name choice (and there is evidence) w3c/websub#10 (7 comments by @aaronpk, @dret, @julien51, @sandhawke)
-
Replace rel=self with rel=canonical w3c/websub#68 (6 comments by @cweiske, @julien51, @pfefferle, @voxpelli)
-
Clarify whether fat pings are required or not w3c/websub#35 (6 comments by @aaronpk, @julien51, @sandhawke, @voxpelli)
-
Use of hub.secret to authenticate hub in more circumstances w3c/websub#36 (5 comments by @aaronpk, @julien51)
-
Discovery: Limit HTML rel=hub links to <link> elements in <head> only. w3c/websub#67 (3 comments by @cweiske, @dissolve, @julien51)
-
Use POST instead of GET for subscription denials w3c/websub#28 (3 comments by @aaronpk, @akuckartz, @julien51)
-
Subscription verification request is not authenticated/protected w3c/websub#42 (3 comments by @aaronpk, @tonyg)
-
https://www.w3.org/TR/pubsub/ should redirect to .../websub/ w3c/websub#71 (2 comments by @aaronpk, @tonyg)
-
Clarify that Content-Type MUST or SHOULD be included in (un)subscription requests w3c/websub#65 (1 comment by @julien51)
-
-
16 pull requests opened.
-
Clarify requirement-level of Content-Type header w3c/websub#74, by @tonyg.
-
removed exact to remove confusion. Fixes #66 w3c/websub#72, by @julien51.
-
add root slash to /.well-known w3c/websub#70, by @pfefferle.
-
Proposed language change to resolve #38. w3c/websub#64, by @tonyg.
-
clarify the use of GET vs POST at the callback w3c/websub#63, by @aaronpk.
-
renames to WebSub w3c/websub#62, by @aaronpk.
-
rephrased discovery section. Fixed #37 w3c/websub#61, by @julien51.
-
hub.callback should be a capability-url w3c/websub#60, by @julien51.
-
Pointing to previous versions of the protocol. Fixes #11 w3c/websub#59, by @julien51.
-
updated authors, fixes #57 w3c/websub#58, by @julien51.
-
rephrased retry section. Fixes #15 w3c/websub#51, by @julien51.
-
explicitly indicating that the list of algorithms can evolve. Fixes #21 w3c/websub#50, by @julien51.
-
rephrased displaying of errors. Fixes #33. Thanks @aaronpk w3c/websub#49, by @julien51.
-
clarifying the use for fat pings. fixes #35 w3c/websub#48, by @julien51.
-
clarification on hub.topic w3c/websub#46, by @aaronpk.
-
wording change w3c/websub#45, by @aaronpk.
-
-
16 pull requests merged.
-
removed exact to remove confusion. Fixes #66 w3c/websub#72.
-
Proposed language change to resolve #38. w3c/websub#64.
-
add root slash to /.well-known w3c/websub#70.
-
clarify the use of GET vs POST at the callback w3c/websub#63.
-
rephrased discovery section. Fixed #37 w3c/websub#61.
-
renames to WebSub w3c/websub#62.
-
Pointing to previous versions of the protocol. Fixes #11 w3c/websub#59.
-
hub.callback should be a capability-url w3c/websub#60.
-
updated authors, fixes #57 w3c/websub#58.
-
rephrased retry section. Fixes #15 w3c/websub#51.
-
clarifying the use for fat pings. fixes #35 w3c/websub#48.
-
rephrased displaying of errors. Fixes #33. Thanks @aaronpk w3c/websub#49.
-
wording change w3c/websub#45.
-
clarification on hub.topic w3c/websub#46.
-
-
6 pull requests received 12 new comments.
-
Clarify that verification and validation are asynchronous wrt the subscription HTTP request itself w3c/websub#31 (2 comments by @julien51, @tonyg)
-
explicitly indicating that the list of algorithms can evolve. Fixes #21 w3c/websub#50 (1 comment by @dret)
w3c/webmention
-
4 issues opened.
-
web mentions for datasets with many URLs w3c/webmention#83, by @agreiner.
-
[Non-normative] Add informative reference to Pingback, brief summary of FAQ in intro w3c/webmention#76, by @tantek.
-
JSON reference really needs to be to RFC 7159, not 4627 w3c/webmention#75, by @tantek.
-
likely editorial: loopback exception specifically about not sending to loopbacks w3c/webmention#71, by @tantek.
-
-
12 pull requests opened.
-
Add loopback and private webmention to ProcessWire w3c/webmention#82, by @gRegorLove.
-
Add @barryf's Transformative to implementation reports w3c/webmention#81, by @barryf.
-
Jonny Barnes’ webmention implentation report w3c/webmention#80, by @jonnybarnes.
-
rm top boilerplate and tick boxes in section 3.2.2 w3c/webmention#79, by @j4y-funabashi.
-
Aruna implementation report w3c/webmention#78, by @j4y-funabashi.
-
Updating implementation report w3c/webmention#77, by @voxpelli.
-
wordpress implementation report w3c/webmention#74, by @snarfed.
-
Initial report for Known w3c/webmention#73, by @benwerd.
-
added, deployed, tested loopback sending avoidance w3c/webmention#72, by @tantek.
-
initial report for webmention.herokuapp.com w3c/webmention#70, by @kevinmarks.
-
Submit Falcon implementation report w3c/webmention#69, by @tantek.
-
fix broken link to TEMPLATE.md w3c/webmention#68, by @tantek.
-
-
12 pull requests merged.
-
Add @barryf's Transformative to implementation reports w3c/webmention#81.
-
Add loopback and private webmention to ProcessWire w3c/webmention#82.
-
Jonny Barnes’ webmention implentation report w3c/webmention#80.
-
rm top boilerplate and tick boxes in section 3.2.2 w3c/webmention#79.
-
Aruna implementation report w3c/webmention#78.
-
Updating implementation report w3c/webmention#77.
-
wordpress implementation report w3c/webmention#74.
-
added, deployed, tested loopback sending avoidance w3c/webmention#72.
-
Initial report for Known w3c/webmention#73.
-
initial report for webmention.herokuapp.com w3c/webmention#70.
-
Submit Falcon implementation report w3c/webmention#69.
-
fix broken link to TEMPLATE.md w3c/webmention#68.
-
-
4 pull requests received 15 new comments.
w3c/ldn
-
1 issue opened.
-
Receiver responses to notification requests w3c/ldn#60, by @albertmeronyo.
-
-
2 issues closed.
-
Add Acknowledgements w3c/ldn#39.
-
Add test suite and reporting section w3c/ldn#8.
-
-
1 issue received 1 new comment.
w3c/activitystreams
-
6 issues opened.
-
Update "name" examples that sound too much like autogenerated w3c/activitystreams#380, by @evanp.
-
Note that namespace document has full extensions information w3c/activitystreams#379, by @evanp.
-
Link to previous version's changelog from changelog w3c/activitystreams#378, by @evanp.
-
Context value as string, list or object w3c/activitystreams#377, by @rhiaro.
-
Make sure examples using multiple vocabularies is up to date w3c/activitystreams#376, by @csarven.
-
Make sure namespace is up to date with spec w3c/activitystreams#375, by @rhiaro.
-
-
16 issues closed.
-
Why exclude markup from name? w3c/activitystreams#338.
-
Namespace needs other formats w3c/activitystreams#357.
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336.
-
Reference Social Web Protocols as Informative reference w3c/activitystreams#371.
-
Ensure all features in the document have test documents w3c/activitystreams#358.
-
Link to Errata document w3c/activitystreams#372.
-
Is name or nameMap essential? w3c/activitystreams#312.
-
***Map terms should be listed in the Properties chapter for clarity w3c/activitystreams#344.
-
Language implies that OrderedCollection pages may not be OrderedCollectionPages w3c/activitystreams#366.
-
Vague language on OrderedCollection type usage requirements w3c/activitystreams#365.
-
Various typos w3c/activitystreams#363.
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/activitystreams#351.
-
Inconsistent usage of "type" and "class" w3c/activitystreams#362.
-
Typo: missing "a" w3c/activitystreams#361.
-
More clarity on the scope of of anti-XSS considerations w3c/activitystreams#367.
-
Not applicable reference to Section 4.6 in conformance criteria w3c/activitystreams#368.
-
-
13 issues received 16 new comments.
-
Unclear on why direct Object relationships (vs. Links) are useful w3c/activitystreams#364 (3 comments by @evanp, @jasnell)
-
Update "name" examples that sound too much like autogenerated w3c/activitystreams#380 (1 comment by @akuckartz)
-
***Map terms should be listed in the Properties chapter for clarity w3c/activitystreams#344 (1 comment by @evanp)
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336 (1 comment by @r12a)
-
Not applicable reference to Section 4.6 in conformance criteria w3c/activitystreams#368 (1 comment by @strugee)
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/activitystreams#351 (1 comment by @evanp)
-
More clarity on the scope of of anti-XSS considerations w3c/activitystreams#367 (1 comment by @evanp)
-
-
4 pull requests opened.
-
initial pass at social streams implementation report w3c/activitystreams#382, by @dissolve.
-
Update OA and PROV use in examples w3c/activitystreams#381, by @csarven.
-
Implementation reports w3c/activitystreams#374, by @cwebber.
-
Remove duplicate Tombstone section w3c/activitystreams#373, by @optikfluffel.
-
-
1 pull request merged.
-
Implementation reports w3c/activitystreams#374.
-
-
2 pull requests closed.
-
Use https ref in @context w3c/activitystreams#353.
-
Remove duplicate Tombstone section w3c/activitystreams#373.
-
-
1 pull request received 1 new comment.
w3c/Micropub
-
1 issue closed.
-
Accessibility Review w3c/Micropub#34.
-
-
3 issues received 6 new comments.
-
no language or direction or localizability of error message? w3c/Micropub#36 (3 comments by @aaronpk, @akuckartz, @aphillips)
-
w3c/activitypub
-
5 issues opened.
-
Typo in publicInbox link w3c/activitypub#171, by @strugee.
-
Improve wording about default Activity addressing w3c/activitypub#170, by @strugee.
-
Add references about OAuth 2.0 w3c/activitypub#169, by @PaulJeong14.
-
About transient objects. w3c/activitypub#168, by @PaulJeong14.
-
in the section 7.9, change reference. w3c/activitypub#167, by @PaulJeong14.
-
-
5 issues closed.
-
Typo in publicInbox link w3c/activitypub#171.
-
Get AP terms in AS2 context/namespace w3c/activitypub#132.
-
in the section 7.9, change reference. w3c/activitypub#167.
-
Add test suite and reporting section. w3c/activitypub#106.
-
Add/Remove activity permission rules are wonky w3c/activitypub#148.
-
-
5 issues received 5 new comments.
TR publications
-
5 documents published.
-
Micropub published as a Candidate Recommendation Snapshot. History of Micropub
-
Post Type Discovery published as a Working Draft. History of Post Type Discovery
-
Linked Data Notifications published as a Working Draft. History of Linked Data Notifications
-
ActivityPub published as a Working Draft. History of ActivityPub
-
PubSub published as a First Public Working Draft. History of PubSub
-
Participants
-
1 organization left.
-
Hypothes.is Project left.
-
GitHub
w3c/websub
-
25 issues opened.
-
Test hubs/feeds? w3c/websub#39, by @tonyg.
-
Content distribution: link header meanings w3c/websub#38, by @tonyg.
-
Discovery inconsistency w3c/websub#37, by @aaronpk.
-
Use of hub.secret to authenticate hub in more circumstances w3c/websub#36, by @tonyg.
-
Clarify whether fat pings are required or not w3c/websub#35, by @voxpelli.
-
Language/direction/localizability of error message w3c/websub#33, by @aaronpk.
-
Include a spec version number? w3c/websub#29, by @tonyg.
-
Use POST instead of GET for subscription denials w3c/websub#28, by @crertel.
-
Document current state of interoperable content types w3c/websub#27, by @aaronpk.
-
Drop suggestion of using "From" header w3c/websub#26, by @aaronpk.
-
consecutive version diff'ing w3c/websub#24, by @dret.
-
Validation: synchronous? w3c/websub#22, by @tonyg.
-
algorithm names w3c/websub#21, by @dret.
-
use subscription resource w3c/websub#20, by @dret.
-
HTTP response codes to content distribution attempts w3c/websub#19, by @tonyg.
-
Lease duration bounds w3c/websub#18, by @tonyg.
-
Unbounded lease duration w3c/websub#17, by @tonyg.
-
Unilateral unsubscription notifications w3c/websub#16, by @tonyg.
-
Failed content distribution attempts w3c/websub#15, by @tonyg.
-
Headers and signature validation w3c/websub#14, by @tonyg.
-
URL vs URI (RFC 3986) inconsistency w3c/websub#13, by @dret.
-
Reference PubSubHubbub w3c/websub#11, by @pfefferle.
-
bad name choice (and there is evidence) w3c/websub#10, by @dret.
-
register "hub" link relation with IANA w3c/websub#9, by @dret.
-
[CR blocker] add Conformance Classes like Webmention has w3c/websub#8, by @tantek.
-
-
3 issues closed.
-
Drop suggestion of using "From" header w3c/websub#26.
-
Include a spec version number? w3c/websub#29.
-
HTTP response codes to content distribution attempts w3c/websub#19.
-
-
23 issues received 108 new comments.
-
bad name choice (and there is evidence) w3c/websub#10 (18 comments by @aaronpk, @dret, @julien51, @pfefferle, @sandhawke, @tonyg, @voxpelli)
-
Use POST instead of GET for subscription denials w3c/websub#28 (15 comments by @aaronpk, @akuckartz, @crertel, @julien51, @pfefferle, @tonyg, @voxpelli)
-
Headers and signature validation w3c/websub#14 (11 comments by @aaronpk, @dret, @julien51, @sknebel)
-
Document current state of interoperable content types w3c/websub#27 (10 comments by @aaronpk, @julien51, @tonyg, @voxpelli)
-
Drop suggestion of using "From" header w3c/websub#26 (6 comments by @aaronpk, @crertel, @julien51, @voxpelli)
-
HTTP response codes to content distribution attempts w3c/websub#19 (3 comments by @aaronpk, @dret, @tonyg)
-
-
8 pull requests opened.
-
Remove problematic wording. Resolves #14. w3c/websub#34, by @tonyg.
-
Fix up section numbering (is there an automatic tool for this?) w3c/websub#32, by @tonyg.
-
remove recommendation about using From header w3c/websub#30, by @aaronpk.
-
clarify lease_seconds is a non-negative decimal integer w3c/websub#25, by @aaronpk.
-
making clear this is talking about media types w3c/websub#23, by @dret.
-
fix current status text w3c/websub#12, by @dret.
-
name change per issue 1 w3c/websub#7, by @tantek.
-
-
6 pull requests merged.
-
making clear this is talking about media types w3c/websub#23.
-
fix current status text w3c/websub#12.
-
name change per issue 1 w3c/websub#7.
-
clarify lease_seconds is a non-negative decimal integer w3c/websub#25.
-
remove recommendation about using From header w3c/websub#30.
-
-
1 pull request closed.
-
Remove problematic wording. Resolves #14. w3c/websub#34.
-
-
2 pull requests received 2 new comments.
-
Fix up section numbering (is there an automatic tool for this?) w3c/websub#32 (1 comment by @julien51)
w3c/webmention
-
1 issue opened.
-
Update URL reference from RFC 3986 to WHATWG URL w3c/webmention#67, by @aaronpk.
-
-
2 issues closed.
-
Update URL reference from RFC 3986 to WHATWG URL w3c/webmention#67.
-
"protocol summary" section is unclear w3c/webmention#55.
-
-
1 issue reopened.
-
Update URL reference from RFC 3986 to WHATWG URL w3c/webmention#67, by @aaronpk.
-
-
1 issue received 4 new comments.
-
Update URL reference from RFC 3986 to WHATWG URL w3c/webmention#67 (4 comments by @aaronpk, @akuckartz, @rhiaro)
-
-
1 pull request opened.
-
Add FrancisCMS implementation report w3c/webmention#66, by @jgarber623.
-
-
1 pull request merged.
-
Add FrancisCMS implementation report w3c/webmention#66.
-
w3c/ldn
-
12 issues opened.
-
LDN High-level security review w3c/ldn#56, by @nickrmc83.
-
Open World Assumption reference not clear in note 2 in ¶3.4 w3c/ldn#55, by @bblfish.
-
unclarity in ¶3.1 "discovery" on finding a link in GET w3c/ldn#54, by @bblfish.
-
Fix link to PubSubHubbub w3c/ldn#53, by @aaronpk.
-
Use of "inbox" w3c/ldn#52, by @klensin.
-
Content language negotiation? w3c/ldn#51, by @r12a.
-
Examples should include @language w3c/ldn#50, by @r12a.
-
Example should have charset=UTF-8 w3c/ldn#49, by @r12a.
-
Reference to expired IETF draft w3c/ldn#48, by @r12a.
-
schema.org namespace w3c/ldn#47, by @acoburn.
-
Editorial improvement w3c/ldn#45, by @acka47.
-
-
16 issues closed.
-
LDN High-level security review w3c/ldn#56.
-
security: posting to unprepared resources w3c/ldn#43.
-
Use of "inbox" w3c/ldn#52.
-
Fix link to PubSubHubbub w3c/ldn#53.
-
Accessibility review w3c/ldn#33.
-
Content language negotiation? w3c/ldn#51.
-
Reference to expired IETF draft w3c/ldn#48.
-
Example should have charset=UTF-8 w3c/ldn#49.
-
Examples should include @language w3c/ldn#50.
-
Coment on HTML example in section 3.1 Discovery w3c/ldn#44.
-
i18n review w3c/ldn#35.
-
Namespace location w3c/ldn#13.
-
schema.org namespace w3c/ldn#47.
-
Editorial improvement w3c/ldn#45.
-
-
18 issues received 81 new comments.
-
unclarity in ¶3.1 "discovery" on finding a link in GET w3c/ldn#54 (11 comments by @bblfish, @csarven, @rhiaro)
-
Open World Assumption reference not clear in note 2 in ¶3.4 w3c/ldn#55 (10 comments by @bblfish, @csarven, @rhiaro)
-
security: posting to unprepared resources w3c/ldn#43 (8 comments by @chrysn, @cwebber, @rhiaro, @sandhawke)
-
Implementation of the OPTIONS request not mentioned in section 3.3 w3c/ldn#46 (5 comments by @csarven, @nfreire, @rhiaro)
-
Coment on HTML example in section 3.1 Discovery w3c/ldn#44 (4 comments by @csarven, @nfreire, @rhiaro)
-
-
3 pull requests opened.
-
ler pyldon reports, readme list w3c/ldn#59, by @albertmeronyo.
-
ler implementation docs w3c/ldn#58, by @albertmeronyo.
-
pyldn implementation docs w3c/ldn#57, by @albertmeronyo.
-
-
2 pull requests merged.
-
ler pyldon reports, readme list w3c/ldn#59.
-
pyldn implementation docs w3c/ldn#57.
-
-
1 pull request closed.
-
ler implementation docs w3c/ldn#58.
-
-
2 pull requests received 2 new comments.
w3c/Micropub
-
7 issues opened.
-
Allow a 202 Accepted from Media Endpoint uploads w3c/Micropub#64, by @barryf.
-
Note about access_token should be normative w3c/Micropub#62, by @rhiaro.
-
Add a way to provide end user error messages w3c/Micropub#61, by @voxpelli.
-
Fix example w3c/Micropub#60, by @dissolve.
-
q=syndicate-to not needed? w3c/Micropub#59, by @dissolve.
-
requirements for query options. w3c/Micropub#58, by @dissolve.
-
Why SHOULD store unrecognized properties? w3c/Micropub#57, by @dissolve.
-
-
7 issues closed.
-
Allow a 202 Accepted from Media Endpoint uploads w3c/Micropub#64.
-
Specify what a mp-* instruction is and how to add new ones w3c/Micropub#33.
-
Note about access_token should be normative w3c/Micropub#62.
-
q=syndicate-to not needed? w3c/Micropub#59.
-
Why SHOULD store unrecognized properties? w3c/Micropub#57.
-
Fix example w3c/Micropub#60.
-
requirements for query options. w3c/Micropub#58.
-
-
8 issues received 24 new comments.
-
Specify what a mp-* instruction is and how to add new ones w3c/Micropub#33 (5 comments by @aaronpk, @voxpelli)
-
1 pull request merged.
-
spell fix w3c/Micropub#63.
-
w3c/activitypub
-
41 issues opened.
-
Is an id required for an object sent over the network? w3c/activitypub#166, by @cwebber.
-
bcc field MUST be stripped from delivered ActivityStreams object. w3c/activitypub#165, by @cwebber.
-
Add examples to media upload mechanism. w3c/activitypub#164, by @cwebber.
-
Rename "Binary Data" to "Uploading Media"? w3c/activitypub#163, by @cwebber.
-
Inbox Discovery/Delivery doesn't fully jive with LDN w3c/activitypub#162, by @gobengo.
-
Notification Targeting: is it complete and is it secure? w3c/activitypub#161, by @gobengo.
-
Example of Public Content Addressing? And should an impl attempt to target/deliver to that URL? w3c/activitypub#160, by @gobengo.
-
"Object creation without a Create Activity" transformation could use more precision w3c/activitypub#159, by @gobengo.
-
Add more friendly diagrams / introdutory material to intro w3c/activitypub#158, by @cwebber.
-
Let the "endpoints" actor property either be an inlined mapping or a link w3c/activitypub#157, by @cwebber.
-
Public content delivery w3c/activitypub#156, by @jaywink.
-
Change tracking w3c/activitypub#155, by @brooksn.
-
Incrementing like counts is a MAY w3c/activitypub#154, by @strugee.
-
Deliver objects to Collections owned by the actor, not server w3c/activitypub#153, by @strugee.
-
Suggest delivery retry mechanisms w3c/activitypub#152, by @strugee.
-
Weird sentence in 8.2 Delivery w3c/activitypub#151, by @strugee.
-
[Question] How exactly do comments on shares get distributed? w3c/activitypub#150, by @strugee.
-
To what extent are Follow activities Undone? w3c/activitypub#149, by @strugee.
-
Add/Remove activity permission rules are wonky w3c/activitypub#148, by @strugee.
-
Update Activity replacement rule ambiguity w3c/activitypub#147, by @strugee.
-
Public collection URI is specified in an example which isn't normative w3c/activitypub#146, by @strugee.
-
preferredUsername vs. name w3c/activitypub#145, by @strugee.
-
Shouldn't the actor `following` and `followers` collections be references? w3c/activitypub#144, by @strugee.
-
Minor problems potentially affecting implementations w3c/activitypub#143, by @strugee.
-
Editorial improvements w3c/activitypub#142, by @strugee.
-
Clarify 'to' vs 'cc' w3c/activitypub#141, by @brooksn.
-
Actor discovery w3c/activitypub#140, by @jaywink.
-
Privacy of followers/following/likes collections w3c/activitypub#139, by @jaywink.
-
about 404 error in the section 3.2 w3c/activitypub#137, by @PaulJeong14.
-
Change 'ActivityStreams Vocabulary' to 'Activity Vocabulary' w3c/activitypub#135, by @PaulJeong14.
-
interoperability clarifications w3c/activitypub#134, by @anarcat.
-
Broken «Social Web Protocols» link w3c/activitypub#133, by @amirouche.
-
Get AP terms in AS2 context/namespace w3c/activitypub#132, by @cwebber.
-
Switch over to ActivityStreams namespace/context w3c/activitypub#131, by @cwebber.
-
Add Undo activity side effects description in Server to Server section w3c/activitypub#130, by @cwebber.
-
Jan's typos and small errors, Volume 1 w3c/activitypub#129, by @jankusanagi.
-
No language markup in example 1 (editorial) w3c/activitypub#128, by @aphillips.
-
establishing 'id' uniqueness/identity w3c/activitypub#127, by @aphillips.
-
'Actor' and language/direction w3c/activitypub#126, by @aphillips.
-
Review of the spec w3c/activitypub#125, by @ghost.
-
-
47 issues closed.
-
Is an id required for an object sent over the network? w3c/activitypub#166.
-
What properties are required or otherwise expected? Make sure we're clear w3c/activitypub#124.
-
Review SHOULD, MUST, etc terms. Be sure for CR! w3c/activitypub#117.
-
Properly cite SWP w3c/activitypub#122.
-
Broken «Social Web Protocols» link w3c/activitypub#133.
-
"Object creation without a Create Activity" transformation could use more precision w3c/activitypub#159.
-
Inbox Discovery/Delivery doesn't fully jive with LDN w3c/activitypub#162.
-
Notification Targeting: is it complete and is it secure? w3c/activitypub#161.
-
Update Activity replacement rule ambiguity w3c/activitypub#147.
-
Suggest delivery retry mechanisms w3c/activitypub#152.
-
bcc field MUST be stripped from delivered ActivityStreams object. w3c/activitypub#165.
-
Review media upload endpoint's mechanism w3c/activitypub#110.
-
Rename "Binary Data" to "Uploading Media"? w3c/activitypub#163.
-
Public content delivery w3c/activitypub#156.
-
More clearly mark sections that are non-normative appropriately w3c/activitypub#116.
-
Add Undo activity side effects description in Server to Server section w3c/activitypub#130.
-
Weird sentence in 8.2 Delivery w3c/activitypub#151.
-
establishing 'id' uniqueness/identity w3c/activitypub#127.
-
Add security considerations section mentioning sanitizing marked up content w3c/activitypub#108.
-
Verify that location headers, status codes instructions align with LDP, make sense w3c/activitypub#118.
-
Public collection URI is specified in an example which isn't normative w3c/activitypub#146.
-
about 404 error in the section 3.2 w3c/activitypub#137.
-
Minor problems potentially affecting implementations w3c/activitypub#143.
-
Review of the spec w3c/activitypub#125.
-
Actor discovery w3c/activitypub#140.
-
Jan's typos and small errors, Volume 1 w3c/activitypub#129.
-
Review LDN section in spec w3c/activitypub#119.
-
Incrementing like counts is a MAY w3c/activitypub#154.
-
To what extent are Follow activities Undone? w3c/activitypub#149.
-
Deliver objects to Collections owned by the actor, not server w3c/activitypub#153.
-
Let the "endpoints" actor property either be an inlined mapping or a link w3c/activitypub#157.
-
Privacy of followers/following/likes collections w3c/activitypub#139.
-
ActivityPump Vocabulary and JSON-LD context w3c/activitypub#30.
-
Switch over to ActivityStreams namespace/context w3c/activitypub#131.
-
preferredUsername vs. name w3c/activitypub#145.
-
Shouldn't the actor `following` and `followers` collections be references? w3c/activitypub#144.
-
Change 'ActivityStreams Vocabulary' to 'Activity Vocabulary' w3c/activitypub#135.
-
Clarify 'to' vs 'cc' w3c/activitypub#141.
-
No language markup in example 1 (editorial) w3c/activitypub#128.
-
'Actor' and language/direction w3c/activitypub#126.
-
accessibility review w3c/activitypub#114.
-
wide review w3c/activitypub#115.
-
security review w3c/activitypub#113.
-
"source" field w3c/activitypub#107.
-
Mark media upload endpoint at risk w3c/activitypub#109.
-
i18n review w3c/activitypub#112.
-
-
4 issues reopened.
-
Public content delivery w3c/activitypub#156, by @cwebber.
-
Actor discovery w3c/activitypub#140, by @cwebber.
-
No language markup in example 1 (editorial) w3c/activitypub#128, by @r12a.
-
establishing 'id' uniqueness/identity w3c/activitypub#127, by @cwebber.
-
-
46 issues received 198 new comments.
-
Inbox Discovery/Delivery doesn't fully jive with LDN w3c/activitypub#162 (24 comments by @akuckartz, @cwebber, @gobengo, @rhiaro)
-
No language markup in example 1 (editorial) w3c/activitypub#128 (18 comments by @akuckartz, @aphillips, @cwebber, @r12a)
-
"Object creation without a Create Activity" transformation could use more precision w3c/activitypub#159 (14 comments by @cwebber, @gobengo, @jasnell, @rhiaro)
-
Example of Public Content Addressing? And should an impl attempt to target/deliver to that URL? w3c/activitypub#160 (12 comments by @cwebber, @gobengo, @jasnell, @rhiaro)
-
Notification Targeting: is it complete and is it secure? w3c/activitypub#161 (9 comments by @cwebber, @gobengo, @rhiaro)
-
Let the "endpoints" actor property either be an inlined mapping or a link w3c/activitypub#157 (4 comments by @cwebber, @rhiaro)
-
Privacy of followers/following/likes collections w3c/activitypub#139 (4 comments by @cwebber, @jaywink)
-
What properties are required or otherwise expected? Make sure we're clear w3c/activitypub#124 (2 comments by @cwebber)
-
Minor problems potentially affecting implementations w3c/activitypub#143 (2 comments by @cwebber, @strugee)
-
[Question] How exactly do comments on shares get distributed? w3c/activitypub#150 (1 comment by @cwebber)
-
More clearly mark sections that are non-normative appropriately w3c/activitypub#116 (1 comment by @cwebber)
-
Verify that location headers, status codes instructions align with LDP, make sense w3c/activitypub#118 (1 comment by @cwebber)
-
Public collection URI is specified in an example which isn't normative w3c/activitypub#146 (1 comment by @cwebber)
-
Deliver objects to Collections owned by the actor, not server w3c/activitypub#153 (1 comment by @cwebber)
-
Shouldn't the actor `following` and `followers` collections be references? w3c/activitypub#144 (1 comment by @cwebber)
-
Change 'ActivityStreams Vocabulary' to 'Activity Vocabulary' w3c/activitypub#135 (1 comment by @cwebber)
-
1 pull request opened.
-
fix typo on section 2.2 w3c/activitypub#138, by @ebalder.
-
-
1 pull request merged.
-
fix typo on section 2.2 w3c/activitypub#138.
-
-
1 pull request received 1 new comment.
w3c/activitystreams
-
1 issue opened.
-
Link to Errata document w3c/activitystreams#372, by @evanp.
-
TR publications
-
5 documents published.
-
Activity Streams 2.0 published as a Candidate Recommendation Snapshot. History of Activity Streams 2.0
-
Activity Vocabulary published as a Candidate Recommendation Snapshot. History of Activity Vocabulary
-
Linked Data Notifications published twice as a Working Draft. History of Linked Data Notifications
-
ActivityPub published as a Working Draft. History of ActivityPub
-
Participants
-
1 participant joined.
-
Benjamin Goering (W3C Invited Experts) joined.
-
GitHub
w3c/ldn
-
12 issues opened.
-
Coment on HTML example in section 3.1 Discovery w3c/ldn#44, by @nfreire.
-
security: posting to unprepared resources w3c/ldn#43, by @chrysn.
-
Sort out normative vs non-normative considerations section w3c/ldn#41, by @rhiaro.
-
Add Acknowledgements w3c/ldn#39, by @csarven.
-
Give some background and context w3c/ldn#38, by @csarven.
-
Clarify paging mechanism w3c/ldn#36, by @dmitrizagidulin.
-
i18n review w3c/ldn#35, by @rhiaro.
-
Security review w3c/ldn#34, by @rhiaro.
-
Accessibility review w3c/ldn#33, by @rhiaro.
-
Backoff strategy for discovery w3c/ldn#32, by @rhiaro.
-
GET requests on receivers with no Accept header w3c/ldn#31, by @acoburn.
-
CR exit criteria w3c/ldn#30, by @rhiaro.
-
-
17 issues closed.
-
Give some background and context w3c/ldn#38.
-
Security review w3c/ldn#34.
-
Media type application/activity+json w3c/ldn#10.
-
Backoff strategy for discovery w3c/ldn#32.
-
Clarify paging mechanism w3c/ldn#36.
-
Create an overview diagram w3c/ldn#4.
-
CR exit criteria w3c/ldn#30.
-
GET requests on receivers with no Accept header w3c/ldn#31.
-
consumer / receiver difference ? w3c/ldn#2.
-
Examples in both Turtle and JSON-LD syntax w3c/ldn#5.
-
Updates to notifications w3c/ldn#14.
-
Add note regarding preference of JSON-LD w3c/ldn#7.
-
Retry sending? w3c/ldn#26.
-
Notifications? Or queuing mechanism? w3c/ldn#21.
-
-
2 issues reopened.
-
Media type application/activity+json w3c/ldn#10, by @rhiaro.
-
Clarify paging mechanism w3c/ldn#36, by @csarven.
-
-
17 issues received 53 new comments.
-
Namespace location w3c/ldn#13 (14 comments by @akuckartz, @azaroth42, @csarven, @danbri, @kidehen, @nandana, @rhiaro, @timbl)
-
Backoff strategy for discovery w3c/ldn#32 (8 comments by @aaronpk, @akuckartz, @BigBlueHat, @csarven, @rhiaro)
-
Inbox and notification persistence, permanence, integrity w3c/ldn#17 (7 comments by @BigBlueHat, @csarven, @rhiaro)
-
Guidence for complete system that does sending, receiving and consuming w3c/ldn#11 (1 comment by @rhiaro)
-
-
3 pull requests opened.
-
Added IndieAnndroid as an implementation of receiving w3c/ldn#42, by @Kongaloosh.
-
Mention of RDF::LinkedData::Notifications w3c/ldn#40, by @kjetilk.
-
Add solid-notifications to implementation list w3c/ldn#37, by @dmitrizagidulin.
-
-
3 pull requests merged.
-
Mention of RDF::LinkedData::Notifications w3c/ldn#40.
-
Add solid-notifications to implementation list w3c/ldn#37.
-
1 pull request reopened.
-
Add solid-notifications to implementation list w3c/ldn#37, by @csarven.
-
-
3 pull requests received 3 new comments.
w3c/websub
-
2 issues opened.
-
[FPWD blocker] consider renaming the spec w3c/websub#5, by @tantek.
-
Update SHA1 text to allow for better hashing mechanisms w3c/websub#4, by @aaronpk.
-
-
1 issue closed.
-
Update SHA1 text to allow for better hashing mechanisms w3c/websub#4.
-
-
2 issues received 10 new comments.
-
[FPWD blocker] consider renaming the spec w3c/websub#5 (7 comments by @aaronpk, @dissolve, @julien51, @pfefferle)
-
Update SHA1 text to allow for better hashing mechanisms w3c/websub#4 (3 comments by @aaronpk, @julien51)
-
-
4 pull requests opened.
-
Protocol should allow for various types of sognature algorithms. w3c/websub#6, by @julien51.
-
update RFC2616 references w3c/websub#3, by @aaronpk.
-
add links to source repo in header w3c/websub#2, by @aaronpk.
-
remove unclosed tag, fix brackets in reference w3c/websub#1, by @aaronpk.
-
-
4 pull requests merged.
-
update RFC2616 references w3c/websub#3.
-
add links to source repo in header w3c/websub#2.
-
remove unclosed tag, fix brackets in reference w3c/websub#1.
-
1 pull request received 2 new comments.
-
Protocol should allow for various types of sognature algorithms. w3c/websub#6 (2 comments by @aaronpk, @julien51)
-
w3c/activitypub
-
24 issues opened.
-
What properties are required or otherwise expected? Make sure we're clear w3c/activitypub#124, by @cwebber.
-
Properly cite SWP w3c/activitypub#122, by @cwebber.
-
Authentication and authorization are tricky words w3c/activitypub#121, by @cwebber.
-
Fix capitalization of "Micropub" w3c/activitypub#120, by @aaronpk.
-
Review LDN section in spec w3c/activitypub#119, by @cwebber.
-
Verify that location headers, status codes instructions align with LDP, make sense w3c/activitypub#118, by @cwebber.
-
Review SHOULD, MUST, etc terms. Be sure for CR! w3c/activitypub#117, by @cwebber.
-
More clearly mark sections that are non-normative appropriately w3c/activitypub#116, by @cwebber.
-
wide review w3c/activitypub#115, by @cwebber.
-
accessibility review w3c/activitypub#114, by @cwebber.
-
security review w3c/activitypub#113, by @cwebber.
-
i18n review w3c/activitypub#112, by @cwebber.
-
Summarize reasoning behind namespace w3c/activitypub#111, by @cwebber.
-
Review media upload endpoint's mechanism w3c/activitypub#110, by @cwebber.
-
Mark media upload endpoint at risk w3c/activitypub#109, by @cwebber.
-
Add security considerations section mentioning sanitizing marked up content w3c/activitypub#108, by @cwebber.
-
"source" field w3c/activitypub#107, by @cwebber.
-
Add test suite and reporting section. w3c/activitypub#106, by @cwebber.
-
Add Acknowledgments section w3c/activitypub#105, by @cwebber.
-
Remove "streams" section in favor of requiring these collections to be of type OrderedCollection w3c/activitypub#104, by @cwebber.
-
Clarify that addressing is on object, and Create activity copies over addressing w3c/activitypub#103, by @cwebber.
-
Mention for JSON-LD @Context w3c/activitypub#102, by @PaulJeong14.
-
proxyUrl type endpoint, or something like it. w3c/activitypub#101, by @cwebber.
-
-
30 issues closed.
-
Authentication and authorization are tricky words w3c/activitypub#121.
-
Fix capitalization of "Micropub" w3c/activitypub#120.
-
Add Acknowledgments section w3c/activitypub#105.
-
ActivityPub needs an explicit Conformance section + 2119 reference w3c/activitypub#86.
-
The context w3c/activitypub#43.
-
Mention for JSON-LD @Context w3c/activitypub#102.
-
Add @context to all examples w3c/activitypub#99.
-
Address spam in security considerations section w3c/activitypub#90.
-
Move authorization and authentication to a security considerations section w3c/activitypub#60.
-
Create a security considerations section w3c/activitypub#82.
-
Clarify auth to reduce incomptable activitypub implementations w3c/activitypub#77.
-
Partial updates w3c/activitypub#85.
-
Add subscribe verb and change meaning of follow verb w3c/activitypub#80.
-
Specify service discovery of inbox/outbox via link relations w3c/activitypub#50.
-
Allow application/ld+json; profile="http://www.w3.org/ns/activitystreams" w3c/activitypub#95.
-
Split the specification up into more implementable sections w3c/activitypub#79.
-
How to discover oauth endpoints? w3c/activitypub#92.
-
proxyUrl type endpoint, or something like it. w3c/activitypub#101.
-
Specify how ActivityStreams paging works in ActivityPub w3c/activitypub#97.
-
Clarify stream ordering requirements w3c/activitypub#54.
-
Clarify that addressing is on object, and Create activity copies over addressing w3c/activitypub#103.
-
Create "verification of content" section w3c/activitypub#81.
-
Call out Micropub and SocialWebProtocols in ActivityPub spec w3c/activitypub#87.
-
Clarify where @id should not yet be provided / will be provided by server w3c/activitypub#62.
-
Transient and garbage collectable activities w3c/activitypub#34.
-
Simplifying deleted object tombstones w3c/activitypub#36.
-
How to define side effects in extensions? w3c/activitypub#31.
-
Specify 201 Created on successful submission w3c/activitypub#96.
-
mediaEndpoint -> media-endpoint w3c/activitypub#94.
-
-
33 issues received 61 new comments.
-
Specify how ActivityStreams paging works in ActivityPub w3c/activitypub#97 (5 comments by @akuckartz, @cwebber, @melvincarvalho)
-
proxyUrl type endpoint, or something like it. w3c/activitypub#101 (4 comments by @cwebber, @jankusanagi)
-
ActivityPub needs an explicit Conformance section + 2119 reference w3c/activitypub#86 (2 comments by @cwebber)
-
Add subscribe verb and change meaning of follow verb w3c/activitypub#80 (2 comments by @cwebber, @rhiaro)
-
Specify service discovery of inbox/outbox via link relations w3c/activitypub#50 (2 comments by @cwebber)
-
Call out Micropub and SocialWebProtocols in ActivityPub spec w3c/activitypub#87 (2 comments by @cwebber)
-
Clarify where @id should not yet be provided / will be provided by server w3c/activitypub#62 (2 comments by @cwebber)
-
Add security considerations section mentioning sanitizing marked up content w3c/activitypub#108 (1 comment by @cwebber)
-
Move authorization and authentication to a security considerations section w3c/activitypub#60 (1 comment by @cwebber)
-
Clarify auth to reduce incomptable activitypub implementations w3c/activitypub#77 (1 comment by @cwebber)
-
Allow application/ld+json; profile="http://www.w3.org/ns/activitystreams" w3c/activitypub#95 (1 comment by @cwebber)
-
Split the specification up into more implementable sections w3c/activitypub#79 (1 comment by @cwebber)
-
Remove "streams" section in favor of requiring these collections to be of type OrderedCollection w3c/activitypub#104 (1 comment by @cwebber)
-
-
2 pull requests closed.
-
Minor edits - typo fixes, style edits, formatting changes w3c/activitypub#74.
-
fixing typos w3c/activitypub#89.
-
-
2 pull requests received 2 new comments.
-
Minor edits - typo fixes, style edits, formatting changes w3c/activitypub#74 (1 comment by @cwebber)
-
w3c/webmention
-
3 issues opened.
-
Link to SWP w3c/webmention#64, by @rhiaro.
-
Update HTTP reference to point at RFC723* w3c/webmention#63, by @kjetilk.
-
Why only "410 GONE" for deleted posts? w3c/webmention#62, by @Perlkonig.
-
-
8 issues closed.
-
Update HTTP reference to point at RFC723* w3c/webmention#63.
-
Recommend a backoff strategy for discovering webmention endpoints w3c/webmention#48.
-
Link to SWP w3c/webmention#64.
-
Section 3.2: no language support w3c/webmention#57.
-
Webmention verification w3c/webmention#42.
-
Definition of 'link' w3c/webmention#43.
-
Why only "410 GONE" for deleted posts? w3c/webmention#62.
-
section 3.1.2 charset w3c/webmention#56.
-
-
10 issues received 17 new comments.
-
Update HTTP reference to point at RFC723* w3c/webmention#63 (4 comments by @aaronpk, @akuckartz, @kjetilk)
-
Recommend a backoff strategy for discovering webmention endpoints w3c/webmention#48 (2 comments by @aaronpk, @marado)
-
-
1 pull request opened.
-
Submitting implementation report for grav-plugin-webmention w3c/webmention#65, by @Perlkonig.
-
-
1 pull request merged.
-
Submitting implementation report for grav-plugin-webmention w3c/webmention#65.
-
-
1 pull request received 1 new comment.
-
Submitting implementation report for grav-plugin-webmention w3c/webmention#65 (1 comment by @aaronpk)
-
w3c/Micropub
-
9 issues opened.
-
Update intro paragraph to link to SWP w3c/Micropub#56, by @aaronpk.
-
Custom MIME type for error and configuration response w3c/Micropub#55, by @cweiske.
-
Error Response: Use status code 404 for "resource not found" w3c/Micropub#54, by @cweiske.
-
Media endpoint: error responses w3c/Micropub#53, by @cweiske.
-
file uploads: alt text and multiple files w3c/Micropub#52, by @cweiske.
-
Clarify if updates container "either" or "at least one of" replace/add/delete w3c/Micropub#51, by @cweiske.
-
"4.1 Examples of Creating Objects" lists "like-of" twice w3c/Micropub#50, by @cweiske.
-
Behavior when the slug already exists w3c/Micropub#49, by @cweiske.
-
File upload: Rename "photo" to "image" w3c/Micropub#48, by @cweiske.
-
-
18 issues closed.
-
Update intro paragraph to link to SWP w3c/Micropub#56.
-
Error Response: Use status code 404 for "resource not found" w3c/Micropub#54.
-
encoding health warning for x-www-urlencoded w3c/Micropub#39.
-
Custom MIME type for error and configuration response w3c/Micropub#55.
-
Media endpoint: error responses w3c/Micropub#53.
-
file uploads: alt text and multiple files w3c/Micropub#52.
-
no way to indicate direction or language of name w3c/Micropub#37.
-
Behavior when the slug already exists w3c/Micropub#49.
-
"4.1 Examples of Creating Objects" lists "like-of" twice w3c/Micropub#50.
-
File upload: Rename "photo" to "image" w3c/Micropub#48.
-
Add MAY/SHOULD/MUST to http://micropub.net/draft/#querying w3c/Micropub#42.
-
Note that clients may not get the expected response from `?q=config` w3c/Micropub#41.
-
Make 3.3.5 explanation more readable w3c/Micropub#44.
-
3.3.2 JSON upload section should require content-type w3c/Micropub#46.
-
Link "Error respones" w3c/Micropub#45.
-
MicroPub normatively references IndieAuth, a non-stable standard w3c/Micropub#47.
-
-
17 issues received 59 new comments.
-
Error Response: Use status code 404 for "resource not found" w3c/Micropub#54 (19 comments by @aaronpk, @akuckartz, @bear, @BigBlueHat, @cweiske, @voxpelli)
-
Servers should send "501 Not Implemented" status for unimplemented #querying commands w3c/Micropub#43 (8 comments by @aaronpk, @akuckartz, @cweiske)
-
no way to indicate direction or language of name w3c/Micropub#37 (7 comments by @aaronpk, @akuckartz, @r12a)
-
Custom MIME type for error and configuration response w3c/Micropub#55 (6 comments by @aaronpk, @csarven, @cweiske, @voxpelli)
-
Clarify if updates container "either" or "at least one of" replace/add/delete w3c/Micropub#51 (2 comments by @aaronpk, @tantek)
-
MicroPub normatively references IndieAuth, a non-stable standard w3c/Micropub#47 (1 comment by @cwebber)
-
w3c/activitystreams
-
15 issues opened.
-
Reference Social Web Protocols as Informative reference w3c/activitystreams#371, by @evanp.
-
Namespace(s) for extensions w3c/activitystreams#370, by @sandhawke.
-
AS1 objects with a "post" verb and a target turn into `Add`, but then the Object is never `Create`d w3c/activitystreams#369, by @strugee.
-
Not applicable reference to Section 4.6 in conformance criteria w3c/activitystreams#368, by @strugee.
-
More clarity on the scope of of anti-XSS considerations w3c/activitystreams#367, by @strugee.
-
Language implies that OrderedCollection pages may not be OrderedCollectionPages w3c/activitystreams#366, by @strugee.
-
Vague language on OrderedCollection type usage requirements w3c/activitystreams#365, by @strugee.
-
Unclear on why direct Object relationships (vs. Links) are useful w3c/activitystreams#364, by @strugee.
-
Various typos w3c/activitystreams#363, by @strugee.
-
Inconsistent usage of "type" and "class" w3c/activitystreams#362, by @strugee.
-
Typo: missing "a" w3c/activitystreams#361, by @strugee.
-
Q: Activity - a reply to a comment which is related to a another object w3c/activitystreams#360, by @tiblu.
-
Q: Activity type "Update" describe actual modifications w3c/activitystreams#359, by @tiblu.
-
Ensure all features in the document have test documents w3c/activitystreams#358, by @evanp.
-
Namespace needs other formats w3c/activitystreams#357, by @rhiaro.
-
-
5 issues closed.
-
Namespace(s) for extensions w3c/activitystreams#370.
-
AS1 objects with a "post" verb and a target turn into `Add`, but then the Object is never `Create`d w3c/activitystreams#369.
-
Q: Activity - a reply to a comment which is related to a another object w3c/activitystreams#360.
-
Q: Activity type "Update" describe actual modifications w3c/activitystreams#359.
-
Figures not rendering? w3c/activitystreams#349.
-
-
1 issue reopened.
-
Is name or nameMap essential? w3c/activitystreams#312, by @evanp.
-
-
16 issues received 47 new comments.
-
Is name or nameMap essential? w3c/activitystreams#312 (14 comments by @BigBlueHat, @cwebber, @evanp, @jasnell, @rhiaro, @tantek)
-
More clarity on the scope of of anti-XSS considerations w3c/activitystreams#367 (5 comments by @jasnell, @strugee)
-
Q: Activity type "Update" describe actual modifications w3c/activitystreams#359 (5 comments by @jasnell, @tiblu)
-
Language implies that OrderedCollection pages may not be OrderedCollectionPages w3c/activitystreams#366 (3 comments by @jasnell, @strugee)
-
Unclear on why direct Object relationships (vs. Links) are useful w3c/activitystreams#364 (3 comments by @jasnell, @strugee)
-
Vague language on OrderedCollection type usage requirements w3c/activitystreams#365 (3 comments by @akuckartz, @jasnell, @strugee)
-
AS1 objects with a "post" verb and a target turn into `Add`, but then the Object is never `Create`d w3c/activitystreams#369 (2 comments by @jasnell, @strugee)
-
Q: Activity - a reply to a comment which is related to a another object w3c/activitystreams#360 (2 comments by @jasnell, @tiblu)
-
Not applicable reference to Section 4.6 in conformance criteria w3c/activitystreams#368 (1 comment by @jasnell)
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336 (1 comment by @r12a)
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/activitystreams#351 (1 comment by @csarven)
-
TR publications
-
4 documents published.
-
Micropub published as a Candidate Recommendation Snapshot. History of Micropub
-
Linked Data Notifications published as a Working Draft. History of Linked Data Notifications
-
ActivityPub published as a Working Draft. History of ActivityPub
-
Social Web Protocols published as a Working Draft. History of Social Web Protocols
-
GitHub
w3c/activitystreams
-
8 issues opened.
-
Activity on behalf of a user w3c/activitystreams#355, by @aries1980.
-
Default Language Context MAY -> SHOULD w3c/activitystreams#354, by @r12a.
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/activitystreams#351, by @csarven.
-
orderedItems in numerous examples, despite being deprecated w3c/activitystreams#350, by @cwebber.
-
Figures not rendering? w3c/activitystreams#349, by @cwebber.
-
What should subject and object of Relationship be? w3c/activitystreams#348, by @rhiaro.
-
Link with `subject`? w3c/activitystreams#347, by @rhiaro.
-
Can value of object property be a list? w3c/activitystreams#346, by @rhiaro.
-
-
7 issues closed.
-
Spanish translations w3c/activitystreams#337.
-
Activity on behalf of a user w3c/activitystreams#355.
-
orderedItems in numerous examples, despite being deprecated w3c/activitystreams#350.
-
Link with `subject`? w3c/activitystreams#347.
-
What should subject and object of Relationship be? w3c/activitystreams#348.
-
"Note" should probably be "Document"? w3c/activitystreams#345.
-
Can value of object property be a list? w3c/activitystreams#346.
-
-
2 issues reopened.
-
Default Language Context MAY -> SHOULD w3c/activitystreams#354, by @evanp.
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336, by @r12a.
-
-
11 issues received 51 new comments.
-
Why exclude markup from name? w3c/activitystreams#338 (10 comments by @BigBlueHat, @jasnell, @kevinmarks, @r12a, @tantek)
-
Default Language Context MAY -> SHOULD w3c/activitystreams#354 (7 comments by @akuckartz, @evanp, @jasnell, @r12a)
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336 (7 comments by @BigBlueHat, @jasnell, @r12a)
-
What should subject and object of Relationship be? w3c/activitystreams#348 (6 comments by @jasnell, @rhiaro)
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/activitystreams#351 (4 comments by @csarven, @evanp, @jasnell)
-
orderedItems in numerous examples, despite being deprecated w3c/activitystreams#350 (4 comments by @cwebber, @jasnell)
-
-
3 pull requests opened.
-
Initial write-up of Apache Streams w3c/activitystreams#356, by @steveblackmon.
-
Use https ref in @context w3c/activitystreams#353, by @jasnell.
-
Updating bidi details w3c/activitystreams#352, by @jasnell.
-
-
1 pull request merged.
-
Updating bidi details w3c/activitystreams#352.
-
-
3 pull requests received 5 new comments.
w3c/ldn
-
3 issues opened.
-
Headers constrain the content w3c/ldn#28, by @melvincarvalho.
-
supporting ldn requires supporing http notifications w3c/ldn#27, by @melvincarvalho.
-
Retry sending? w3c/ldn#26, by @rhiaro.
-
-
2 issues closed.
-
Headers constrain the content w3c/ldn#28.
-
-
5 issues received 70 new comments.
-
supporting ldn requires supporing http notifications w3c/ldn#27 (45 comments by @BigBlueHat, @csarven, @cwebber, @melvincarvalho, @rhiaro, @semanticfire)
-
-
1 pull request opened.
-
1 pull request closed.
-
1 pull request received 1 new comment.
-
Removing implementation that does not comply with link headers w3c/ldn#29 (1 comment by @melvincarvalho)
-
w3c/Micropub
-
8 issues opened.
-
MicroPub normatively references IndieAuth, a non-stable standard w3c/Micropub#47, by @cwebber.
-
3.3.2 JSON upload section should require content-type w3c/Micropub#46, by @cweiske.
-
Link "Error respones" w3c/Micropub#45, by @cweiske.
-
Make 3.3.5 explanation more readable w3c/Micropub#44, by @cweiske.
-
Add MAY/SHOULD/MUST to http://micropub.net/draft/#querying w3c/Micropub#42, by @cweiske.
-
Note that clients may not get the expected response from `?q=config` w3c/Micropub#41, by @aaronpk.
-
Normatively describe the configuration response w3c/Micropub#40, by @aaronpk.
-
-
3 issues closed.
-
no language or direction or localizability of error message? w3c/Micropub#36.
-
Normatively describe the configuration response w3c/Micropub#40.
-
Uploading files that are referred to in the content w3c/Micropub#35.
-
-
8 issues received 25 new comments.
-
MicroPub normatively references IndieAuth, a non-stable standard w3c/Micropub#47 (10 comments by @aaronpk, @akuckartz, @cwebber, @rhiaro)
-
Servers should send "501 Not Implemented" status for unimplemented #querying commands w3c/Micropub#43 (6 comments by @aaronpk, @dshanske, @voxpelli)
-
no language or direction or localizability of error message? w3c/Micropub#36 (1 comment by @aaronpk)
-
w3c/webmention
-
1 issue closed.
-
Caution regarding using form encoded data w3c/webmention#60.
-
-
2 issues received 15 new comments.
-
Caution regarding using form encoded data w3c/webmention#60 (10 comments by @aaronpk, @dissolve, @kevinmarks, @melvincarvalho)
-
Section 3.2: no language support w3c/webmention#57 (5 comments by @aaronpk, @kevinmarks, @sandhawke)
-
-
1 pull request opened.
-
Added delete support (3.1.4) w3c/webmention#61, by @gRegorLove.
-
-
1 pull request merged.
-
Added delete support (3.1.4) w3c/webmention#61.
-
w3c/activitypub
-
4 issues opened.
-
Add @context to all examples w3c/activitypub#99, by @cwebber.
-
When posting a Create object, always copy creator's actor to the attributedTo w3c/activitypub#98, by @cwebber.
-
Specify how ActivityStreams paging works in ActivityPub w3c/activitypub#97, by @cwebber.
-
Specify 201 Created on successful submission w3c/activitypub#96, by @cwebber.
-
-
4 issues closed.
-
How is Notification performed? w3c/activitypub#76.
-
Sending replies up the chain w3c/activitypub#47.
-
Separate document into ActivityPub and ActivitySub documents w3c/activitypub#91.
-
When posting a Create object, always copy creator's actor to the attributedTo w3c/activitypub#98.
-
-
6 issues received 8 new comments.
-
Separate document into ActivityPub and ActivitySub documents w3c/activitypub#91 (1 comment by @rhiaro)
-
When posting a Create object, always copy creator's actor to the attributedTo w3c/activitypub#98 (1 comment by @cwebber)
-
Allow application/ld+json; profile="http://www.w3.org/ns/activitystreams" w3c/activitypub#95 (1 comment by @rhiaro)
-
Specify how ActivityStreams paging works in ActivityPub w3c/activitypub#97 (1 comment by @melvincarvalho)
-
Clarify where @id should not yet be provided / will be provided by server w3c/activitypub#62 (1 comment by @rhiaro)
-
1 pull request opened.
-
Delivery algorithms w3c/activitypub#100, by @rhiaro.
-
-
1 pull request merged.
-
Delivery algorithms w3c/activitypub#100.
-
-
1 pull request closed.
-
Clarify Notification & Delivery w3c/activitypub#75.
-
-
1 pull request received 1 new comment.
TR publications
-
8 documents published.
-
Micropub published as a Working Draft. History of Micropub
-
Activity Streams 2.0 published twice as a Working Draft. History of Activity Streams 2.0
-
Activity Vocabulary published twice as a Working Draft. History of Activity Vocabulary
-
JF2 Post Serialization Format published as a First Public Working Draft. History of JF2 Post Serialization Format
-
Post Type Discovery published as a First Public Working Draft. History of Post Type Discovery
-
Linked Data Notifications published as a First Public Working Draft. History of Linked Data Notifications
-
Participants
-
1 participant joined.
-
Julien Genestoux (W3C Invited Experts) joined.
-
-
2 participants left.
-
Shane Hudson (W3C Invited Experts) left.
-
Benjamin Goering (W3C Invited Experts) left.
-
GitHub
w3c/webmention
-
4 issues opened.
-
Caution regarding using form encoded data w3c/webmention#60, by @melvincarvalho.
-
section 3.2: no character encoding on response examples w3c/webmention#58, by @r12a.
-
Section 3.2: no language support w3c/webmention#57, by @r12a.
-
section 3.1.2 charset w3c/webmention#56, by @r12a.
-
-
2 issues closed.
-
Webmention message is not clearly mapped to linked data w3c/webmention#51.
-
section 3.2: no character encoding on response examples w3c/webmention#58.
-
-
4 issues received 19 new comments.
-
Webmention message is not clearly mapped to linked data w3c/webmention#51 (13 comments by @akuckartz, @melvincarvalho, @rhiaro, @sandhawke, @tantek)
-
Caution regarding using form encoded data w3c/webmention#60 (3 comments by @aaronpk, @akuckartz, @dissolve)
-
-
1 pull request opened.
-
Implementation report for ProcessWire Webmention plugin w3c/webmention#59, by @gRegorLove.
-
-
1 pull request merged.
-
Implementation report for ProcessWire Webmention plugin w3c/webmention#59.
-
w3c/ldn
-
6 issues opened.
-
explain relationship to webmention w3c/ldn#25, by @dret.
-
Use `ldn` for TR shortname w3c/ldn#23, by @csarven.
-
Requires receivers store everything, even junk w3c/ldn#22, by @aaronpk.
-
Notifications? Or queuing mechanism? w3c/ldn#21, by @gklyne.
-
Remove: MUST send to all inboxes w3c/ldn#20, by @sandhawke.
-
URI for notification w3c/ldn#19, by @rhiaro.
-
-
10 issues closed.
-
Use `ldn` for TR shortname w3c/ldn#23.
-
explain relationship to webmention w3c/ldn#25.
-
Consider adding a section for Web IDL w3c/ldn#3.
-
Domain specific inbox discovery w3c/ldn#16.
-
URI for notification w3c/ldn#19.
-
Requires receivers store everything, even junk w3c/ldn#22.
-
Contents of Inbox and NonRDFSources w3c/ldn#18.
-
Deduplication of notifications w3c/ldn#12.
-
Remove: MUST send to all inboxes w3c/ldn#20.
-
Give guidance on shared Inboxes w3c/ldn#6.
-
-
1 issue reopened.
-
Requires receivers store everything, even junk w3c/ldn#22, by @rhiaro.
-
-
13 issues received 88 new comments.
-
Media type application/activity+json w3c/ldn#10 (26 comments by @akuckartz, @csarven, @melvincarvalho, @rhiaro, @RubenVerborgh)
-
explain relationship to webmention w3c/ldn#25 (9 comments by @akuckartz, @csarven, @dret, @melvincarvalho, @rhiaro)
-
Requires receivers store everything, even junk w3c/ldn#22 (9 comments by @aaronpk, @akuckartz, @csarven, @rhiaro)
-
Guidence for complete system that does sending, receiving and consuming w3c/ldn#11 (3 comments by @akuckartz, @csarven, @rhiaro)
-
-
1 pull request opened.
-
Add solid words to implementations w3c/ldn#24, by @melvincarvalho.
-
-
1 pull request merged.
-
Add solid words to implementations w3c/ldn#24.
-
-
1 pull request received 1 new comment.
w3c/activitystreams
-
15 issues opened.
-
"Note" should probably be "Document"? w3c/activitystreams#345, by @cwebber.
-
***Map terms should be listed in the Properties chapter for clarity w3c/activitystreams#344, by @rogersuen.
-
The preview property is missing in the Properties list for the Link type. w3c/activitystreams#343, by @rogersuen.
-
Use full URL for links between the documents w3c/activitystreams#342, by @evanp.
-
**Map fields become a SHOULD w3c/activitystreams#341, by @evanp.
-
Linking to RFC 3339 for duration is dubious w3c/activitystreams#339, by @r12a.
-
Why exclude markup from name? w3c/activitystreams#338, by @r12a.
-
Spanish translations w3c/activitystreams#337, by @r12a.
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336, by @r12a.
-
How to know the language of a natural language value when there is no translation? w3c/activitystreams#335, by @r12a.
-
RFC 5646 listed as informative reference w3c/activitystreams#334, by @r12a.
-
Use BCP 47 rather than RFC 5646 w3c/activitystreams#333, by @r12a.
-
Internationalize IRI in example 3 w3c/activitystreams#332, by @r12a.
-
Clarify that zone offsets in times do not indicate local time w3c/activitystreams#331, by @r12a.
-
Revise language in Exit criteria to note At Risk features w3c/activitystreams#330, by @evanp.
-
-
13 issues closed.
-
**Map fields become a SHOULD w3c/activitystreams#341.
-
Use full URL for links between the documents w3c/activitystreams#342.
-
The preview property is missing in the Properties list for the Link type. w3c/activitystreams#343.
-
Revise language in Exit criteria to note At Risk features w3c/activitystreams#330.
-
Clarify that zone offsets in times do not indicate local time w3c/activitystreams#331.
-
Internationalize IRI in example 3 w3c/activitystreams#332.
-
Use BCP 47 rather than RFC 5646 w3c/activitystreams#333.
-
RFC 5646 listed as informative reference w3c/activitystreams#334.
-
How to know the language of a natural language value when there is no translation? w3c/activitystreams#335.
-
Linking to RFC 3339 for duration is dubious w3c/activitystreams#339.
-
Media Type definition w3c/activitystreams#53.
-
Test documents that are known invalid Activity Streams 2.0 documents w3c/activitystreams#328.
-
Link to the validator from the test documents directory w3c/activitystreams#327.
-
-
3 issues reopened.
-
Spanish translations w3c/activitystreams#337, by @r12a.
-
Why exclude markup from name? w3c/activitystreams#338, by @sandhawke.
-
Media Type definition w3c/activitystreams#53, by @evanp.
-
-
15 issues received 57 new comments.
-
**Map fields become a SHOULD w3c/activitystreams#341 (23 comments by @akuckartz, @aphillips, @azaroth42, @evanp, @jasnell, @r12a, @sandhawke, @wilkie)
-
Why exclude markup from name? w3c/activitystreams#338 (12 comments by @akuckartz, @BigBlueHat, @evanp, @jasnell, @r12a, @sandhawke)
-
The preview property is missing in the Properties list for the Link type. w3c/activitystreams#343 (2 comments by @evanp, @jasnell)
-
***Map terms should be listed in the Properties chapter for clarity w3c/activitystreams#344 (2 comments by @evanp, @jasnell)
-
How to know the language of a natural language value when there is no translation? w3c/activitystreams#335 (2 comments by @evanp, @jasnell)
-
Clarify that zone offsets in times do not indicate local time w3c/activitystreams#331 (1 comment by @r12a)
-
It should be possible to indicate the default base direction for natural language values w3c/activitystreams#336 (1 comment by @jasnell)
-
Define tiny and topological vocabulary for "relationship" w3c/activitystreams#289 (1 comment by @rhiaro)
-
-
1 pull request opened.
-
Address i18n concerns w3c/activitystreams#340, by @jasnell.
-
-
2 pull requests merged.
-
Address i18n concerns w3c/activitystreams#340.
-
Clarify in core that Links can have 'id' w3c/activitystreams#329.
-
-
1 pull request received 1 new comment.
w3c/Micropub
-
8 issues opened.
-
encoding health warning for x-www-urlencoded w3c/Micropub#39, by @r12a.
-
example in pounds w3c/Micropub#38, by @r12a.
-
no way to indicate direction or language of name w3c/Micropub#37, by @r12a.
-
no language or direction or localizability of error message? w3c/Micropub#36, by @r12a.
-
Uploading files that are referred to in the content w3c/Micropub#35, by @kevinmarks.
-
Accessibility Review w3c/Micropub#34, by @aaronpk.
-
Specify what a mp-* instruction is and how to add new ones w3c/Micropub#33, by @voxpelli.
-
Rename "mp-action" to "action" w3c/Micropub#32, by @aaronpk.
-
-
4 issues closed.
-
example in pounds w3c/Micropub#38.
-
Clear up language regarding file upload and media endpoint w3c/Micropub#29.
-
Rename "mp-action" to "action" w3c/Micropub#32.
-
Media endpoint diagram image url 404s w3c/Micropub#30.
-
-
8 issues received 25 new comments.
-
Clear up language regarding file upload and media endpoint w3c/Micropub#29 (5 comments by @aaronpk, @richardcarls)
-
Uploading files that are referred to in the content w3c/Micropub#35 (2 comments by @aaronpk, @kevinmarks)
-
no language or direction or localizability of error message? w3c/Micropub#36 (1 comment by @aaronpk)
w3c/activitypub
-
1 issue opened.
-
Allow application/ld+json; profile="http://www.w3.org/ns/activitystreams" w3c/activitypub#95, by @rhiaro.
-
-
2 issues received 2 new comments.
-
Allow application/ld+json; profile="http://www.w3.org/ns/activitystreams" w3c/activitypub#95 (1 comment by @akuckartz)
TR publications
-
3 documents published.
-
Micropub published as a Working Draft. History of Micropub
-
ActivityPub published as a Working Draft. History of ActivityPub
-
Social Web Protocols published as a Working Draft. History of Social Web Protocols
-
Participants
-
1 participant joined.
-
Sarven Capadisli (W3C Invited Experts) joined.
-
-
1 participant left.
-
Sarven Capadisli (W3C Invited Experts) left.
-
-
1 organization joined.
-
Wiley joined.
-
GitHub
w3c/ldn
-
17 issues opened.
-
Contents of Inbox and NonRDFSources w3c/ldn#18, by @csarven.
-
Inbox and notification persistence, permanence, integrity w3c/ldn#17, by @csarven.
-
Domain specific inbox discovery w3c/ldn#16, by @csarven.
-
Inbox interactions w3c/ldn#15, by @csarven.
-
Updates to notifications w3c/ldn#14, by @csarven.
-
Namespace location w3c/ldn#13, by @csarven.
-
Deduplication of notifications w3c/ldn#12, by @rhiaro.
-
Media type application/activity+json w3c/ldn#10, by @rhiaro.
-
What to serve eventually when Turtle is received w3c/ldn#9, by @csarven.
-
Add test suite and reporting section w3c/ldn#8, by @csarven.
-
Add note regarding preference of JSON-LD w3c/ldn#7, by @akuckartz.
-
Give guidance on shared Inboxes w3c/ldn#6, by @csarven.
-
Examples in both Turtle and JSON-LD syntax w3c/ldn#5, by @csarven.
-
Create an overview diagram w3c/ldn#4, by @csarven.
-
Consider adding a section for Web IDL w3c/ldn#3, by @csarven.
-
consumer / receiver difference ? w3c/ldn#2, by @akuckartz.
-
-
2 issues closed.
-
Inbox interactions w3c/ldn#15.
-
-
1 issue reopened.
-
Contents of Inbox and NonRDFSources w3c/ldn#18, by @csarven.
-
-
10 issues received 21 new comments.
-
Guidence for complete system that does sending, receiving and consuming w3c/ldn#11 (1 comment by @csarven)
-
1 pull request opened.
-
Add a Gitter chat badge to README.md w3c/ldn#1, by @gitter-badger.
-
-
1 pull request closed.
-
Add a Gitter chat badge to README.md w3c/ldn#1.
-
w3c/webmention
-
2 issues opened.
-
"protocol summary" section is unclear w3c/webmention#55, by @aphillips.
-
Webmention message is not clearly mapped to linked data w3c/webmention#51, by @melvincarvalho.
-
-
5 issues closed.
-
webmention verification should specify using a HEAD request w3c/webmention#46.
-
Sending webmentions - discovery - lacks interoperability w3c/webmention#40.
-
Differentiate new class "proxy receiver" and how it differs from "receiver" w3c/webmention#44.
-
Webmention should use JSON-LD w3c/webmention#47.
-
8 issues received 50 new comments.
-
Webmention message is not clearly mapped to linked data w3c/webmention#51 (37 comments by @aaronpk, @akuckartz, @dissolve, @melvincarvalho, @rhiaro, @sandhawke)
-
Security consideration: Attacker can cause webmention sender to send arbitrary requests to victim w3c/webmention#20 (4 comments by @aaronpk, @ePirat, @mblaney)
-
Differentiate new class "proxy receiver" and how it differs from "receiver" w3c/webmention#44 (2 comments by @aaronpk)
-
Move mention of specific limit of redirects to Security Considerations section w3c/webmention#45 (1 comment by @aaronpk)
-
webmention verification should specify using a HEAD request w3c/webmention#46 (1 comment by @aaronpk)
-
-
5 pull requests opened.
-
Implementation report for Bridgy w3c/webmention#54, by @snarfed.
-
Implementation report for Dobrado w3c/webmention#53, by @mblaney.
-
add Kaku to implementation section w3c/webmention#52, by @bear.
-
current status of postly w3c/webmention#50, by @dissolve.
-
Add GNU Social implementation report w3c/webmention#49, by @singpolyma.
-
-
5 pull requests merged.
-
Implementation report for Bridgy w3c/webmention#54.
-
Implementation report for Dobrado w3c/webmention#53.
-
add Kaku to implementation section w3c/webmention#52.
-
current status of postly w3c/webmention#50.
-
Add GNU Social implementation report w3c/webmention#49.
-
-
2 pull requests received 2 new comments.
w3c/activitystreams
-
10 issues opened.
-
Test documents that are known invalid Activity Streams 2.0 documents w3c/activitystreams#328, by @evanp.
-
Link to the validator from the test documents directory w3c/activitystreams#327, by @evanp.
-
Typo in vocabulary/url example w3c/activitystreams#326, by @azaroth42.
-
Label all the closed issues in standard way w3c/activitystreams#325, by @sandhawke.
-
Rename activitystreams-core to core and activitystreams-vocab to vocab w3c/activitystreams#324, by @sandhawke.
-
Link to implementation reports w3c/activitystreams#323, by @evanp.
-
Link to Test Suite w3c/activitystreams#322, by @evanp.
-
Implementation report template and submission process w3c/activitystreams#321, by @evanp.
-
Update the links to Github repo and pages to w3c/activitystreams w3c/activitystreams#320, by @evanp.
-
Add note in exit criteria about dropping features w3c/activitystreams#319, by @evanp.
-
-
11 issues closed.
-
Label all the closed issues in standard way w3c/activitystreams#325.
-
Implementation report template and submission process w3c/activitystreams#321.
-
Link to implementation reports w3c/activitystreams#323.
-
Link to Test Suite w3c/activitystreams#322.
-
Add note in exit criteria about dropping features w3c/activitystreams#319.
-
Make AS1 an informative reference w3c/activitystreams#317.
-
Update the links to Github repo and pages to w3c/activitystreams w3c/activitystreams#320.
-
Remove reference to CURIE w3c/activitystreams#318.
-
Rename activitystreams-core to core and activitystreams-vocab to vocab w3c/activitystreams#324.
-
Typo in vocabulary/url example w3c/activitystreams#326.
-
JSON-LD context needs updating w3c/activitystreams#316.
-
-
7 issues received 13 new comments.
-
Label all the closed issues in standard way w3c/activitystreams#325 (4 comments by @akuckartz, @evanp, @rhiaro)
-
[Proposal] Support for free definable annotations w3c/activitystreams#231 (2 comments by @annando, @rhiaro)
-
AS2-classes inherit from more than one parent class... w3c/activitystreams#274 (1 comment by @rhiaro)
-
-
1 pull request opened.
-
Clarify in core that Links can have 'id' w3c/activitystreams#329, by @gobengo.
-
w3c/activitypub
-
7 issues opened.
-
mediaEndpoint -> media-endpoint w3c/activitypub#94, by @rhiaro.
-
How to discover oauth endpoints? w3c/activitypub#92, by @cwebber.
-
Separate document into ActivityPub and ActivitySub documents w3c/activitypub#91, by @cwebber.
-
Address spam in security considerations section w3c/activitypub#90, by @cwebber.
-
Spam (unsolicited, non-addressed delivery) w3c/activitypub#88, by @rhiaro.
-
Call out Micropub and SocialWebProtocols in ActivityPub spec w3c/activitypub#87, by @cwebber.
-
ActivityPub needs an explicit Conformance section + 2119 reference w3c/activitypub#86, by @tantek.
-
-
4 issues closed.
-
Make HTTP methods optional w3c/activitypub#18.
-
Submitting a file (e.g. a Photo) w3c/activitypub#23.
-
How is the new URL returned after an update? w3c/activitypub#83.
-
Spam (unsolicited, non-addressed delivery) w3c/activitypub#88.
-
-
9 issues received 15 new comments.
-
Split the specification up into more implementable sections w3c/activitypub#79 (3 comments by @cwebber)
-
Call out Micropub and SocialWebProtocols in ActivityPub spec w3c/activitypub#87 (1 comment by @akuckartz)
-
-
2 pull requests opened.
-
#18 remove HTTP PUT and HTTP DELETE w3c/activitypub#93, by @tsyesika.
-
fixing typos w3c/activitypub#89, by @dret.
-
-
1 pull request merged.
-
#18 remove HTTP PUT and HTTP DELETE w3c/activitypub#93.
-
-
1 pull request received 3 new comments.
w3c/Micropub
-
4 issues opened.
-
Media endpoint diagram image url 404s w3c/Micropub#30, by @jjdelc.
-
Clear up language regarding file upload and media endpoint w3c/Micropub#29, by @richardcarls.
-
Add section linking to ActivityPub w3c/Micropub#27, by @aaronpk.
-
Add UX diagram showing benefits of media endpoint w3c/Micropub#26, by @aaronpk.
-
-
8 issues closed.
-
Add explanation/intro/scenario w3c/Micropub#21.
-
Register link relation with IANA w3c/Micropub#19.
-
Add UX diagram showing benefits of media endpoint w3c/Micropub#26.
-
Add section linking to ActivityPub w3c/Micropub#27.
-
Should `q=source` always return the URL of the post? w3c/Micropub#23.
-
Add explicit note about string vs array values w3c/Micropub#24.
-
Drop form-encoded support for updates? w3c/Micropub#25.
-
Discuss using ActivityPub syntax for updates/deletes w3c/Micropub#22.
-
-
8 issues received 9 new comments.
-
2 pull requests opened.
-
Fix App flow image url w3c/Micropub#31, by @jjdelc.
-
singular -> plural w3c/Micropub#28, by @dret.
-
-
3 pull requests closed.
-
Fix App flow image url w3c/Micropub#31.
-
singular -> plural w3c/Micropub#28.
-
first attempt to address #19 w3c/Micropub#20.
-
-
3 pull requests received 3 new comments.
TR publications
-
5 documents published.
-
Webmention published as a Candidate Recommendation Snapshot. History of Webmention
-
Activity Streams 2.0 published as a Working Draft. History of Activity Streams 2.0
-
Activity Vocabulary published as a Working Draft. History of Activity Vocabulary
-
Webmention published as a Working Draft. History of Webmention
-
Micropub published as a Working Draft. History of Micropub
-
Participants
-
1 organization joined.
-
University of Surrey joined.
-
GitHub
w3c/activitystreams
-
8 issues opened.
-
Remove reference to CURIE w3c/activitystreams#318, by @evanp.
-
Make AS1 an informative reference w3c/activitystreams#317, by @evanp.
-
JSON-LD context needs updating w3c/activitystreams#316, by @rhiaro.
-
formerType defined as functional w3c/activitystreams#315, by @jasnell.
-
Add a paragraph with benefits of upgrade to 1.0 and 2.0 w3c/activitystreams#313, by @evanp.
-
Is name or nameMap essential? w3c/activitystreams#312, by @natalieesk.
-
Add relationship vocabulary to activitystreams2.owl w3c/activitystreams#311, by @evanp.
-
-
14 issues closed.
-
Add a paragraph with benefits of upgrade to 1.0 and 2.0 w3c/activitystreams#313.
-
Changelog w3c/activitystreams#314.
-
formerType defined as functional w3c/activitystreams#315.
-
Add relationship vocabulary to activitystreams2.owl w3c/activitystreams#311.
-
How to denote a "Closed" poll or discussion thread? w3c/activitystreams#297.
-
Is "name" always a SHOULD for Object types? w3c/activitystreams#296.
-
Add a `deleted` timestamp property to Object w3c/activitystreams#292.
-
Define tiny and topological vocabulary for "relationship" w3c/activitystreams#289.
-
Example of Accept activity with "target" property w3c/activitystreams#306.
-
Example of Add activity with "origin" property w3c/activitystreams#307.
-
Example of Delete activity with "origin" property w3c/activitystreams#308.
-
Example of Offer activity with target property w3c/activitystreams#309.
-
Example of Profile object with describes property w3c/activitystreams#310.
-
add an example with text/markdown content w3c/activitystreams#305.
-
-
9 issues received 23 new comments.
-
Is "name" always a SHOULD for Object types? w3c/activitystreams#296 (4 comments by @evanp, @jasnell)
-
Define tiny and topological vocabulary for "relationship" w3c/activitystreams#289 (4 comments by @evanp, @kevinmarks, @sandhawke, @tantek)
-
JSON-LD context needs updating w3c/activitystreams#316 (3 comments by @jasnell, @rhiaro, @sandhawke)
-
Add a paragraph with benefits of upgrade to 1.0 and 2.0 w3c/activitystreams#313 (3 comments by @evanp, @shevski, @tantek)
-
How to denote a "Closed" poll or discussion thread? w3c/activitystreams#297 (3 comments by @evanp, @jasnell)
-
-
1 pull request closed.
-
Drop Relationship and subject w3c/activitystreams#291.
-
-
1 pull request received 1 new comment.
w3c/webmention
-
12 issues opened.
-
Recommend a backoff strategy for discovering webmention endpoints w3c/webmention#48, by @aaronpk.
-
Webmention should use JSON-LD w3c/webmention#47, by @sandhawke.
-
webmention verification should specify using a HEAD request w3c/webmention#46, by @bear.
-
Move mention of specific limit of redirects to Security Considerations section w3c/webmention#45, by @aaronpk.
-
Differentiate new class "proxy receiver" and how it differs from "receiver" w3c/webmention#44, by @aaronpk.
-
Definition of 'link' w3c/webmention#43, by @rhiaro.
-
Webmention verification w3c/webmention#42, by @hvdsomp.
-
Client is not defined w3c/webmention#41, by @melvincarvalho.
-
Sending webmentions - discovery - lacks interoperability w3c/webmention#40, by @melvincarvalho.
-
No JSON based social syntax w3c/webmention#39, by @melvincarvalho.
-
No document at http://www.w3.org/ns/webmention w3c/webmention#38, by @melvincarvalho.
-
Remove Salmentions? w3c/webmention#37, by @sandhawke.
-
-
4 issues closed.
-
No JSON based social syntax w3c/webmention#39.
-
No document at http://www.w3.org/ns/webmention w3c/webmention#38.
-
Client is not defined w3c/webmention#41.
-
Remove Salmentions? w3c/webmention#37.
-
-
10 issues received 116 new comments.
-
No JSON based social syntax w3c/webmention#39 (57 comments by @aaronpk, @akuckartz, @kevinmarks, @lehors, @melvincarvalho, @rhiaro, @sandhawke, @tantek)
-
Webmention verification w3c/webmention#42 (19 comments by @aaronpk, @dissolve, @hvdsomp, @kevinmarks, @rhiaro, @sandhawke, @sknebel, @tantek)
-
webmention verification should specify using a HEAD request w3c/webmention#46 (12 comments by @aaronpk, @bear, @dissolve, @sandhawke, @voxpelli, @wilkie)
-
Sending webmentions - discovery - lacks interoperability w3c/webmention#40 (7 comments by @aaronpk, @kevinmarks, @melvincarvalho, @sandhawke, @voxpelli)
-
No document at http://www.w3.org/ns/webmention w3c/webmention#38 (7 comments by @aaronpk, @akuckartz, @melvincarvalho, @rhiaro, @sandhawke)
-
Recommend a backoff strategy for discovering webmention endpoints w3c/webmention#48 (3 comments by @bear, @tantek, @voxpelli)
-
Differentiate new class "proxy receiver" and how it differs from "receiver" w3c/webmention#44 (1 comment by @sandhawke)
-
w3c/activitypub
-
1 issue opened.
-
Partial updates w3c/activitypub#85, by @rhiaro.
-
-
4 issues received 6 new comments.
-
Clarify auth to reduce incomptable activitypub implementations w3c/activitypub#77 (2 comments by @dmitrizagidulin, @rpeinl)
-
Move authorization and authentication to a security considerations section w3c/activitypub#60 (1 comment by @rpeinl)
-
w3c/Micropub
-
1 issue opened.
-
Drop form-encoded support for updates? w3c/Micropub#25, by @aaronpk.
-
-
2 issues received 3 new comments.
TR publications
-
2 documents published.
-
Webmention published twice as a Working Draft. History of Webmention
-
GitHub
w3c/webmention
-
1 issue opened.
-
Develop exit criteria for CR w3c/webmention#35, by @aaronpk.
-
-
4 issues closed.
-
Develop exit criteria for CR w3c/webmention#35.
-
Register "webmention" with IANA w3c/webmention#29.
-
Webmention MUST be done anonymously w3c/webmention#14.
-
-
5 issues received 13 new comments.
-
Security consideration: Attacker can cause webmention sender to send arbitrary requests to victim w3c/webmention#20 (5 comments by @aaronpk, @tantek, @voxpelli)
-
It is unclear how to convert "source" and "target" parameters to URIs w3c/webmention#9 (4 comments by @aaronpk, @jasnell, @melvincarvalho, @rhiaro)
-
-
2 pull requests opened.
-
clarify form fields, checkbox for 100% open source w3c/webmention#36, by @tantek.
-
remove jekmentions from Implementations->Services w3c/webmention#34, by @sknebel.
-
-
2 pull requests merged.
-
clarify form fields, checkbox for 100% open source w3c/webmention#36.
-
remove jekmentions from Implementations->Services w3c/webmention#34.
-
w3c/activitystreams
-
8 issues opened.
-
Example of Profile object with describes property w3c/activitystreams#310, by @evanp.
-
Example of Offer activity with target property w3c/activitystreams#309, by @evanp.
-
Example of Delete activity with "origin" property w3c/activitystreams#308, by @evanp.
-
Example of Add activity with "origin" property w3c/activitystreams#307, by @evanp.
-
Example of Accept activity with "target" property w3c/activitystreams#306, by @evanp.
-
add an example with text/markdown content w3c/activitystreams#305, by @elf-pavlik.
-
Definition of IntransitiveActivity is incorrect w3c/activitystreams#304, by @evanp.
-
Are the @ symbols going to stay? w3c/activitystreams#303, by @natalieesk.
-
-
11 issues closed.
-
Ensure -vocabulary has examples of described class features w3c/activitystreams#249.
-
CR: What are the separate "features" of AS2? w3c/activitystreams#280.
-
CR: Need explicit CR exit critera in spec w3c/activitystreams#279.
-
Problem with the "Undo" activity w3c/activitystreams#301.
-
Are the @ symbols going to stay? w3c/activitystreams#303.
-
Definition of IntransitiveActivity is incorrect w3c/activitystreams#304.
-
scope v context w3c/activitystreams#300.
-
Add 'IntransitiveActivity' to as-core section 4 (to match as-vocab) w3c/activitystreams#290.
-
CR: needs Conformance Clause w3c/activitystreams#281.
-
Core example 27 uses the wrong context w3c/activitystreams#298.
-
Proposal: drop 'scope' property w3c/activitystreams#299.
-
-
14 issues received 27 new comments.
-
Is "name" always a SHOULD for Object types? w3c/activitystreams#296 (5 comments by @evanp, @jasnell)
-
Define tiny and topological vocabulary for "relationship" w3c/activitystreams#289 (5 comments by @evanp, @jasnell, @tantek)
-
Ensure -vocabulary has examples of described class features w3c/activitystreams#249 (2 comments by @azaroth42, @evanp)
-
-
1 pull request opened.
-
Update index.html w3c/activitystreams#302, by @evanp.
-
-
1 pull request merged.
-
Update index.html w3c/activitystreams#302.
-
-
1 pull request received 1 new comment.
w3c/Micropub
-
2 issues opened.
-
Add explicit note about string vs array values w3c/Micropub#24, by @aaronpk.
-
Should `q=source` always return the URL of the post? w3c/Micropub#23, by @aaronpk.
-
-
3 issues received 12 new comments.
-
Discuss using ActivityPub syntax for updates/deletes w3c/Micropub#22 (10 comments by @aaronpk, @barryf, @valpackett)
-
w3c/activitypub
-
2 issues opened.
-
Move preferredUsername, summary, icon to "MAY" provideable actor properties w3c/activitypub#84, by @cwebber.
-
How is the new URL returned after an update? w3c/activitypub#83, by @aaronpk.
-
-
7 issues closed.
-
Submit objects without Activity w3c/activitypub#32.
-
Requirements around the id requirements are not clear w3c/activitypub#78.
-
Implementation doc: dereference objects posted to inbox w3c/activitypub#46.
-
Don't dereference groups to all users w3c/activitypub#52.
-
Discovery of collections/streams w3c/activitypub#71.
-
Move preferredUsername, summary, icon to "MAY" provideable actor properties w3c/activitypub#84.
-
fix draft type on http://w3c-social.github.io/activitypub/ w3c/activitypub#73.
-
-
4 issues received 4 new comments.
-
fix draft type on http://w3c-social.github.io/activitypub/ w3c/activitypub#73 (1 comment by @cwebber)
TR publications
-
3 documents published.
-
Webmention published twice as a Working Draft. History of Webmention
-
Micropub published as a Working Draft. History of Micropub
-
Participants
-
1 participant joined.
-
Joshua Tilles (W3C Invited Experts) joined.
-
GitHub
w3c/activitystreams
-
7 issues opened.
-
Problem with the "Undo" activity w3c/activitystreams#301, by @tsyesika.
-
scope v context w3c/activitystreams#300, by @jasnell.
-
Proposal: drop 'scope' property w3c/activitystreams#299, by @dmitrizagidulin.
-
Core example 27 uses the wrong context w3c/activitystreams#298, by @evanp.
-
How to denote a "Closed" poll or discussion thread? w3c/activitystreams#297, by @dmitrizagidulin.
-
Is "name" always a SHOULD for Object types? w3c/activitystreams#296, by @evanp.
-
markup and translations w3c/activitystreams#295, by @karlitschek.
-
-
6 issues closed.
-
Extension Registry and tweet:id w3c/activitystreams#283.
-
Why is ActivityStreams 2 so bloated? ;_; w3c/activitystreams#284.
-
Feedback on AS2 from django implementer of v1 w3c/activitystreams#285.
-
markup and translations w3c/activitystreams#295.
-
11 issues received 42 new comments.
-
Define tiny and topological vocabulary for "relationship" w3c/activitystreams#289 (7 comments by @dmitrizagidulin, @evanp, @jasnell, @tantek)
-
Add a `deleted` timestamp property to Object w3c/activitystreams#292 (7 comments by @dmitrizagidulin, @evanp, @jasnell)
-
Is it ever justified for an AS2 object to have both `name` and `nameMap`? (also applies to `content` and `summary`) w3c/activitystreams#294 (5 comments by @jasnell, @Josh-Tilles)
-
Problem with the "Undo" activity w3c/activitystreams#301 (4 comments by @cwebber, @jasnell, @tsyesika)
-
Add 'IntransitiveActivity' to as-core section 4 (to match as-vocab) w3c/activitystreams#290 (3 comments by @evanp, @jasnell, @rhiaro)
-
How to denote a "Closed" poll or discussion thread? w3c/activitystreams#297 (3 comments by @evanp, @jasnell)
-
Is "name" always a SHOULD for Object types? w3c/activitystreams#296 (3 comments by @evanp, @jasnell)
-
-
1 pull request received 1 new comment.
w3c/webmention
-
1 issue opened.
-
Add conformance requirements section w3c/webmention#32, by @aaronpk.
-
-
3 issues closed.
-
Support whole-domain delegation w3c/webmention#21.
-
Add conformance requirements section w3c/webmention#32.
-
It is unclear how to convert "source" and "target" parameters to URIs w3c/webmention#9.
-
-
1 issue reopened.
-
Webmention MUST be done anonymously w3c/webmention#14, by @aaronpk.
-
-
16 issues received 31 new comments.
-
Security consideration: Attacker can cause webmention sender to send arbitrary requests to victim w3c/webmention#20 (6 comments by @aaronpk, @cwebber, @ePirat)
-
It is unclear how to convert "source" and "target" parameters to URIs w3c/webmention#9 (6 comments by @aaronpk, @sandhawke)
-
Webmention is not correctly defined in the rel registry (from #3) w3c/webmention#8 (2 comments by @aaronpk, @kevinmarks)
-
-
1 pull request opened.
-
use "SHOULD NOT" in the rfc2119 sense w3c/webmention#33, by @willnorris.
-
-
1 pull request merged.
-
use "SHOULD NOT" in the rfc2119 sense w3c/webmention#33.
-
w3c/activitypub
-
7 issues opened.
-
Create a security considerations section w3c/activitypub#82, by @tsyesika.
-
Create "verification of content" section w3c/activitypub#81, by @cwebber.
-
Add subscribe verb and change meaning of follow verb w3c/activitypub#80, by @tsyesika.
-
Split the specification up into more implementable sections w3c/activitypub#79, by @tsyesika.
-
Requirements around the id requirements are not clear w3c/activitypub#78, by @cwebber.
-
Clarify auth to reduce incomptable activitypub implementations w3c/activitypub#77, by @tsyesika.
-
How is Notification performed? w3c/activitypub#76, by @rhiaro.
-
-
13 issues closed.
-
DELETE method doesn't mention tombstone post w3c/activitypub#40.
-
Add Example activities of each type in sec 9.2 "Activities" w3c/activitypub#61.
-
Clarify normative reqs of default recipient list w3c/activitypub#51.
-
Clarify ACL w3c/activitypub#28.
-
'Silent' posting w3c/activitypub#38.
-
Embedding object in inReplyTo w3c/activitypub#37.
-
Targeting missing from examples w3c/activitypub#26.
-
Special "Followers" collection section incomplete w3c/activitypub#27.
-
Inbox MAY only be accessible by owning user (not must?) w3c/activitypub#39.
-
"to": "http://as.schema/public" vs. "target": "MY OUTBOX URI" w3c/activitypub#29.
-
Support discovery without responding with HTML w3c/activitypub#49.
-
Link to issues at top of ActivityPump document w3c/activitypub#58.
-
-
1 issue reopened.
-
Transient and garbage collectable activities w3c/activitypub#34, by @tsyesika.
-
-
27 issues received 51 new comments.
-
Requirements around the id requirements are not clear w3c/activitypub#78 (4 comments by @melvincarvalho, @tsyesika, @wilkie)
-
Clarify stream ordering requirements w3c/activitypub#54 (3 comments by @akuckartz, @cwebber, @tsyesika)
-
ActivityPump Vocabulary and JSON-LD context w3c/activitypub#30 (2 comments by @sandhawke, @tsyesika)
-
Expected response for POST {Update,Delete} activity with object: 'http://facebook.com' w3c/activitypub#48 (2 comments by @cwebber, @tsyesika)
-
Add Example activities of each type in sec 9.2 "Activities" w3c/activitypub#61 (1 comment by @tsyesika)
-
Clarify auth to reduce incomptable activitypub implementations w3c/activitypub#77 (1 comment by @tsyesika)
-
"to": "http://as.schema/public" vs. "target": "MY OUTBOX URI" w3c/activitypub#29 (1 comment by @tsyesika)
-
fix draft type on http://w3c-social.github.io/activitypub/ w3c/activitypub#73 (1 comment by @cwebber)
-
1 pull request opened.
-
Clarify Notification & Delivery w3c/activitypub#75, by @rhiaro.
-
w3c/Micropub
-
3 issues opened.
-
Discuss using ActivityPub syntax for updates/deletes w3c/Micropub#22, by @aaronpk.
-
Add explanation/intro/scenario w3c/Micropub#21, by @dret.
-
Register link relation with IANA w3c/Micropub#19, by @dret.
-
-
1 issue received 4 new comments.
-
1 pull request opened.
-
first attempt to address #19 w3c/Micropub#20, by @dret.
-
Participants
-
2 participants joined.
-
Ann Bassetti (W3C Invited Experts) joined.
-
Irina Bolychevsky (W3C) joined.
-
GitHub
w3c/activitystreams
-
12 issues opened.
-
Add a `deleted` timestamp property to Object w3c/activitystreams#292, by @dmitrizagidulin.
-
Add 'IntransitiveActivity' to as-core section 4 (to match as-vocab) w3c/activitystreams#290, by @dmitrizagidulin.
-
Define tiny and topological vocabulary for "relationship" w3c/activitystreams#289, by @dmitrizagidulin.
-
Why do Objects have '.id' but Links don't? w3c/activitystreams#288, by @gobengo.
-
What is the scope of rel value w3c/activitystreams#287, by @dissolve.
-
Language in Appendix B [non-CR, action] w3c/activitystreams#286, by @azaroth42.
-
Feedback on AS2 from django implementer of v1 w3c/activitystreams#285, by @kevinmarks.
-
Why is ActivityStreams 2 so bloated? ;_; w3c/activitystreams#284, by @kevinmarks.
-
Extension Registry and tweet:id w3c/activitystreams#283, by @gobengo.
-
Implementation of Relationships w3c/activitystreams#282, by @rhiaro.
-
5 issues closed.
-
AS2 specs should have a section on privacy implications w3c/activitystreams#255.
-
Implementation of Relationships w3c/activitystreams#282.
-
Language in Appendix B [non-CR, action] w3c/activitystreams#286.
-
What is the scope of rel value w3c/activitystreams#287.
-
Why do Objects have '.id' but Links don't? w3c/activitystreams#288.
-
-
12 issues received 44 new comments.
-
Why is ActivityStreams 2 so bloated? ;_; w3c/activitystreams#284 (15 comments by @akuckartz, @cwebber, @ghost, @gobengo, @jasnell, @kevinmarks)
-
Extension Registry and tweet:id w3c/activitystreams#283 (5 comments by @gobengo, @Josh-Tilles, @kevinmarks)
-
Add a `deleted` timestamp property to Object w3c/activitystreams#292 (5 comments by @cwebber, @dmitrizagidulin, @rhiaro)
-
Why do Objects have '.id' but Links don't? w3c/activitystreams#288 (4 comments by @dmitrizagidulin, @jasnell)
-
Is it ever justified for an AS2 object to have both `name` and `nameMap`? (also applies to `content` and `summary`) w3c/activitystreams#294 (1 comment by @Josh-Tilles)
-
AS2 specs should have a section on privacy implications w3c/activitystreams#255 (1 comment by @jasnell)
-
-
1 pull request opened.
-
Drop Relationship and subject w3c/activitystreams#291, by @dmitrizagidulin.
-
-
1 pull request received 3 new comments.
w3c/webmention
-
4 issues closed.
-
Should be source syntax agnostic w3c/webmention#25.
-
Discuss handling of fragments in URLs w3c/webmention#24.
-
clarifying URLEncoded form meaning w3c/webmention#11.
-
DDoS prevention w3c/webmention#27.
-
-
6 issues received 7 new comments.
-
Security consideration: Attacker can cause webmention sender to send arbitrary requests to victim w3c/webmention#20 (1 comment by @aaronpk)
-
1 pull request received 2 new comments.
w3c/Micropub
-
1 issue opened.
-
8 issues closed.
-
License w3c/Micropub#7.
-
add section with all the assumptions made w3c/Micropub#6.
-
comparing mp-* actions to AS2.0 equivalents w3c/Micropub#4.
-
coupling with microformats w3c/Micropub#2.
-
"url" parameter conflict w3c/Micropub#12.
-
comparing Patch to existing specifications w3c/Micropub#5.
-
Capitalization Micropub/Microformat w3c/Micropub#17.
-
-
6 issues received 6 new comments.
w3c/activitypub
-
4 issues opened.
-
fix draft type on http://w3c-social.github.io/activitypub/ w3c/activitypub#73, by @dissolve.
-
Discovery of collections/streams w3c/activitypub#71, by @rhiaro.
-
Standardize on `gh-pages` branch w3c/activitypub#70, by @dmitrizagidulin.
-
Actors with no Followers/Following collections w3c/activitypub#69, by @dmitrizagidulin.
-
-
5 issues closed.
-
Clarify "prohom authorization" (typo?) w3c/activitypub#55.
-
What's a "share activity"? w3c/activitypub#65.
-
Clarify use of 'objectTypes' w3c/activitypub#53.
-
Actors with no Followers/Following collections w3c/activitypub#69.
-
Standardize on `gh-pages` branch w3c/activitypub#70.
-
-
8 issues received 15 new comments.
-
Move authorization and authentication to a security considerations section w3c/activitypub#60 (3 comments by @akuckartz, @cwebber)
-
-
2 pull requests opened.
-
Minor edits - typo fixes, style edits, formatting changes w3c/activitypub#74, by @dmitrizagidulin.
-
re-fixing typos w3c/activitypub#72, by @dret.
-
-
1 pull request merged.
-
re-fixing typos w3c/activitypub#72.
-
-
1 pull request closed.
-
fixing typos w3c/activitypub#68.
-
-
3 pull requests received 6 new comments.
-
Minor edits - typo fixes, style edits, formatting changes w3c/activitypub#74 (1 comment by @dmitrizagidulin)
TR publications
-
4 documents published.
-
ActivityPub published as a First Public Working Draft. History of ActivityPub
-
Micropub published as a First Public Working Draft. History of Micropub
-
Social Web Protocols published as a First Public Working Draft. History of Social Web Protocols
-
Webmention published as a First Public Working Draft. History of Webmention
-
Participants
-
2 participants joined.
-
Benjamin Goering (W3C Invited Experts) joined.
-
Dmitri Zagidulin (W3C Invited Experts) joined.
-
GitHub
w3c/webmention
-
1 issue opened.
-
Register "webmention" with IANA w3c/webmention#29, by @dret.
-
-
1 issue received 5 new comments.
-
3 pull requests opened.
-
Fix <img> URL attribute from href to src. w3c/webmention#31, by @DomenicoDeFelice.
-
adding "IANA Considerations" section w3c/webmention#30, by @dret.
-
make fpwd for next week w3c/webmention#28, by @sandhawke.
-
-
3 pull requests merged.
-
adding "IANA Considerations" section w3c/webmention#30.
-
Fix <img> URL attribute from href to src. w3c/webmention#31.
-
make fpwd for next week w3c/webmention#28.
-
-
2 pull requests received 4 new comments.
w3c/activitypub
-
4 issues opened.
-
Responses on Activities? w3c/activitypub#67, by @tsyesika.
-
Groups are mentioned, but never expanded w3c/activitypub#66, by @cwebber.
-
What's a "share activity"? w3c/activitypub#65, by @cwebber.
-
Rename "favorites" collection to "likes"? w3c/activitypub#64, by @cwebber.
-
-
6 issues closed.
-
Responses on Activities? w3c/activitypub#67.
-
Groups are mentioned, but never expanded w3c/activitypub#66.
-
Rename "favorites" collection to "likes"? w3c/activitypub#64.
-
HTTPS-only identifiers is too restrictive w3c/activitypub#15.
-
Allow Webfinger for Actors w3c/activitypub#20.
-
Outbox stream having ALL objects seems unsustainable w3c/activitypub#63.
-
-
6 issues received 14 new comments.
-
1 pull request opened.
-
fixing typos w3c/activitypub#68, by @dret.
-
w3c/Micropub
-
2 issues opened.
-
Capitalization Micropub/Microformat w3c/Micropub#17, by @dret.
-
s/edit/update w3c/Micropub#16, by @rhiaro.
-
-
8 issues closed.
-
s/edit/update w3c/Micropub#16.
-
Responses needs like example html w3c/Micropub#9.
-
MediaObjects - binary files w3c/Micropub#8.
-
Consider eliminating add and update w3c/Micropub#14.
-
references to normative/informative dependencies w3c/Micropub#3.
-
why mp-* instead of HTTP headers w3c/Micropub#10.
-
Consider using full "micropub-*" instead of "mp-*" w3c/Micropub#13.
-
Remove references to proprietary silos w3c/Micropub#15.
-
-
7 issues received 9 new comments.
w3c/activitystreams
-
4 issues opened.
-
CR: needs Conformance Clause w3c/activitystreams#281, by @sandhawke.
-
CR: What are the separate "features" of AS2? w3c/activitystreams#280, by @sandhawke.
-
CR: Need explicit CR exit critera in spec w3c/activitystreams#279, by @tantek.
-
W3C Social WG members and other contributors missing in Acknowledgements section w3c/activitystreams#278, by @elf-pavlik.
-
-
4 issues closed.
-
W3C Social WG members and other contributors missing in Acknowledgements section w3c/activitystreams#278.
-
CR: Require valid AS2 implementations to use AS2 vocab where applicable w3c/activitystreams#276.
-
AS2-classes inherit from more than one parent class... w3c/activitystreams#274.
-
-
6 issues received 10 new comments.
-
CR: What are the separate "features" of AS2? w3c/activitystreams#280 (2 comments by @gobengo, @sandhawke)
-
W3C Social WG members and other contributors missing in Acknowledgements section w3c/activitystreams#278 (2 comments by @jasnell)
-
AS2 specs should have a section on privacy implications w3c/activitystreams#255 (2 comments by @jasnell, @tantek)
-
CR: Need lifecycle and naming convention guidance for extensions to help possible future convergence and standardization w3c/activitystreams#261 (2 comments by @elf-pavlik, @jasnell)
-
CR: Require valid AS2 implementations to use AS2 vocab where applicable w3c/activitystreams#276 (1 comment by @jasnell)
-
AS2-classes inherit from more than one parent class... w3c/activitystreams#274 (1 comment by @jasnell)
-