#w3c

London friends! 🇬🇧

The @w3c @tag (Technical Architecture Group) is coming to Samsung King’s Cross on March 4, and we’d love to chat.

If you’re interested in web standards, browser architecture, or want to discuss the future of the platform, grab a free ticket and say hi: https://ti.to/web-standards/meet-the-w3c-tag

#W3C #WebStandards #TAG #London @w3cdevs

@w3c
The RDF version of SKOS [1] does not contain a licensing information, other than e.g. SSN [2] or DCAT3 [3]. Is it permitted to distribute (parts of) it and under which conditions? Does the W3C Software license [4] or the W3C Document license [5] apply to it, and if yes, which version? Could a licensing statement be added?

1. https://www.w3.org/2009/08/skos-reference/skos.rdf
2. https://www.w3.org/ns/ssn/ssn.rdf
3. https://www.w3.org/ns/dcat3.ttl
4. https://www.w3.org/copyright/software-license-2023/
5. https://www.w3.org/copyright/document-license-2023/

#RDF #SKOS #W3C

Rogue Project's Friendica Social Network | Display

friendica.rogueproject.org/dis…

Fediverse Report – #149 – On Protocol Governance The W3C has announced a new Social Web Working Group, starting January 15, 2026, to maintain and update...

#w3c #ActivityPub #governance #protocol
RE: connectedplaces.online/?p=5144

Medien: 1

Fediverse Politics, Meta®

ActivityPub, the protocol that powers much of the fediverse and allows the various fediverse platforms and servers to talk to each other, has become an official W3C standard 8 years ago!

https://www.w3.org/news/2018/activitypub-is-now-a-w3c-recommendation/

#fediverse #activitypub #standards #OpenWeb #W3C #anniversary #OTD #OnThisDay

New Social Web Working Group at W3C https://socialwebfoundation.org/2026/01/15/new-social-web-working-group-at-w3c/ #ActivityPub, #Socialcg, #Socialweb, #Socialwg, #W3c, #Workinggroup

connectedplaces.online/reports/fediverse-report-148-on-protocol-governance/

On the complexities of protocol governance.

There are only two organisations that are active in the fediverse that are a paid member of the W3C: Meta and the Social Web Foundation.

With the Social Web Foundation also receiving funding from Meta, the company that built Threads now has more institutional standing in ActivityPub governance than any of the organisations actually building open fediverse software.

Mastodon gGmbH, Framasoft, and others are not W3C members and cannot participate in the Working Group unless they are invited.

#w3c #ActivityPub Esteemed Fediverse, a personal remark

it currently matters again to have a chair who knows what is going on, is striving for facts, understanding fascism and having a will to resist imperialism. And the capacity to save net neutrality.
#stabil

Hey @darius
thank you for this:
https://lists.w3.org/Archives/Public/public-socialweb/2026Jan/0000.html
💖

---
Currently we move our projects to codeberg and so i just published a first document there about our fedi projects.
https://codeberg.org/Menschys/fedi-codebase
We would really like to have building blocks for a healthy and fair ActivityPub, supporting Client-To-Server.

Current Issues are linked. If you want, I can give you an overview of the Social CG dev meetings since 2016 and the European Events like fedicamp, fediday, Public Spaces, 3C etc.

ActivityPub standardization is back! The #W3C just announced a new Working Group to evolve #ActivityPub and #ActivityStream and related standards! This is extremely good news. It's not like all the world's federated social media protocol problems were already solved! https://lists.w3.org/Archives/Public/public-socialweb/2026Jan/0000.html

Today the W3C standards organization announced a new working group to advance the ActivityPub and Activity Streams standards. The Social Web Foundation, as a W3C member organization, will be participating in the group. The working group’s goal is to release a backwards-compatible iteration of each specification in Q3 of 2026.

Activity Streams was released in 2017, and ActivityPub was released in early 2018. Since that time, the experience of hundreds of implementers and millions of users has shown places that the specifications are confusing or unclear, or missing features. The new Social Web Working Group will provide revisions of these documents to make them easier to use for implementers.

ActivityPub is an actively used protocol with millions of users and billions of notes, images, video and audio files published. Standards work on ActivityPub will necessarily be evolutionary, not revolutionary, and will incorporate backwards compatibility. Developers can confidently keep working on ActivityPub today without worrying about breaking changes in the future.

The Social Web Working Group will work closely with the Social Web Community Group, the organization that has been stewarding ActivityPub and its extensions since 2018. The Community Group will remain the focal point for innovative developments extending ActivityPub into different areas like geosocial applications or threaded forums, while the Working Group will concentrate on the core documents.

One Community Group document that will be moving into the Working Group is LOLA, the live data portability spec that originated in the CG’s Data Portability Task Force. LOLA lets users move from one ActivityPub server to another while retaining all their social connections, their content, and their reactions. It’s a great improvement for data portability on the social web.

The Social Web Working Group will consist of representatives of W3C member organizations and invited experts from the standards and development community. The group will be chaired by Darius Kazemi, longtime contributor to the ActivityPub developer community. Meetings and proceedings will be public, and developers can review the work happening in the ActivityPub GitHub repository.

Thanks to everyone who’s done the work getting this charter to completion; especially Dmitri Zagidulin, the SocialCG chair who drove the charter editing and review process. Now, the work begins!