Show Navigation
Notices tagged with w3c
-
Recently @W3.org (@w3c@w3c.social) published the first Group Note of the Vision for W3C:
https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/
I’m the current editor of the Vision for W3C and helped get it across the line this year to reach #w3cAB (W3C Advisory Board @ab@w3c.social) consensus to publish as an official Group Note, the first official Note that the AB (Advisory Board) has ever published.
I’m very proud of this milestone, as I and a few others including many on the AB¹, have been working on it for a few years in various forms, and with the broader W3C Vision TF² (Task Force) for the past year.
W3C also recently announced the Vision for W3C in their news feed:
https://www.w3.org/news/2024/group-note-vision-for-w3c/
One of the key goals of this document was to capture the spirit of why we are at #W3C and our shared values & principles we use to guide our work & decisions at W3C.
If you work with any groups at W3C, anything from a Community Group (CG) to a Working Group (WG), I highly recommend you read this document from start to finish.
See what resonates with you, if there is anything that doesn’t sound right to you, or if you see anything missing that you feel exemplifies the best of what W3C is, please file an issue or a suggestion:
https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22Project+Vision%22+-label%3ADefer
Check that list to see if your concerns or suggestions are already captured, and if so, add an upvote or comment accordingly.
Our goal is to eventually publish this document as an official W3C Statement, with the consensus of the entire #w3cAC (W3C Advisory Committee).
One key aspect which the Vision touches on but perhaps too briefly is what I see as the fundamental purpose of why we do the work we do at W3C, which in my opinion is:
To create & facilitate user-first interoperable standards that improve the web for humanity
The Vision does mention “#interoperable” explicitly as part of our Vision for the Web in https://w3c.github.io/AB-public/Vision#vision-web:
”There is one interoperable world-wide Web.”
The Vision also mentions “#interoperability” explicitly in our Operational Principles https://w3c.github.io/AB-public/Vision#op-principles:
“Interoperability: We verify the fitness of our specifications through open test suites and actual implementation experience, because we believe the purpose of standards is to enable independent interoperable implementations.”
These are both excellent, and yet, I think we can do better, with adding some sort of explicit statement between those two about that “We will” create & facilitate user-first interoperable standards that improve the web for humanity.
In the coming weeks I’ll be reflecting how we (the VisionTF) can incorporate that sort of imperative “We will” statement about interoperable standards into the Vision for W3C, as well as working with the AB and W3C Team on defining a succinct updated mission & purpose for W3C based on that sort of input and more.
In a related effort, I have also been leading the AB’s “3Is Priority Project³” (Interoperability and the Role of Independent Implementations), which is a pretty big project to define and clarify what each of those three Is mean, with respect to each other and Incubation, which is its own Priority Project⁴.
As part of the 3Is project, the first “I” I’ve been focusing on has unsurprisingly been “Interoperable”. As with other #OpenAB projects, our work on understanding interoperability, its aspects, and defining what do we mean by interoperable is published and iterated on the W3C’s public wiki:
https://www.w3.org/wiki/Interoperable
This is still a work in progress, however it’s sufficiently structured to take a look if interoperability is something you care about or have opinions about.
In particular, if you know of definitions of interoperable or interoperability that resonate and make sense to you, or articles or blog posts about interoperability that explore various aspects, I am gathering such references so we can make sure the W3C’s definition of interoperable is both well-stated, and clearly reflects a broader industry understanding of interoperability.
References:
¹ https://www.w3.org/TR/w3c-vision/#acknowledgements
² https://www.w3.org/wiki/AB/VisionTF
³ https://www.w3.org/wiki/AB/2024_Priorities#Interoperability_and_the_Role_of_Independent_Implementations
⁴ https://www.w3.org/wiki/AB/2024_Priorities#Incubation
-
Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan.
The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹.
The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²):
* https://www.w3.org/wiki/AC/Meetings#2024_Spring
Most of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.
Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.
Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB
Like most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels.
For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:
* 📄 report: https://www.w3.org/reports/ai-web-impact/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf
* ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch
* ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch
* 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)
* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf
* 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.
* 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/
I’ll update this list with additional resources as they are made publicly viewable.
If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday
References:
¹ https://w3.org/wiki/AC
² https://w3.org/wiki/AB
³ https://w3.org/wiki/Board
⁴ https://www.w3.org/Consortium/Process/
⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings
⁶ https://w3.org/tag
⁷ https://www.w3.org/groups/wg/
⁸ https://chapters.w3.org/
⁹ https://www.w3.org/invited-experts/#ac-observer
¹⁰ https://www.w3.org/wiki/TPAC
¹¹ https://www.w3.org/events/ac/2024/ac-2024/
¹² https://www.w3.org/membership/list/
¹³ https://en.wiktionary.org/wiki/hallway_track
¹⁴ https://microformats.org/wiki/existing-rel-values
¹⁵ https://indieweb.org/sidefile-antipattern
¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
-
I recently wrote a high level summary blog post:
W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023
https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac
of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.
Posting this note to explicitly #hashtag that article with topics mentioned therein:
#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub
because I forgot to put explicit categories (p-category markup) in the article post.
Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.
Post glossary:
article post
https://indieweb.org/article
note post
https://indieweb.org/note
p-category
https://indieweb.org/p-category
tags
https://indieweb.org/tags
-
Congrats to fellow re-elected W3C Advisory Board (@AB@W3C.social @W3CAB) members:
* @cwilso.com (@cdub@mastodon.social @cwilso)
* @fantasai.inkedblade.net (@fantasai@w3c.social @fantasai)
* Avneesh Singh
and newcomers:
* @reidmore@mastodon.social (@wendy_a_reid)
* Song XU
Thanks to Heejin Chung and Charles Nevile for your service on the #W3CAB.
https://www.w3.org/blog/news/archives/9933
via #W3C (@w3.org @w3c@w3c.social @w3c): https://w3c.social/@w3c/110491804762139049
Previously: https://tantek.com/2023/128/t1/w3c-advisory-board-election-support
-
s/agenda bashing/agenda gardening/g
Replace all uses of “agenda bashing” with “agenda gardening”, e.g. in group meetings.
Language matters, metaphors affect framing and reinforce values. Replacing violent metaphors with caring or at least non-violent expressions can help create a more constructive context.
Recommended this particular replacement yesterday during day 2 of our #W3C Advisory Board (@ab@w3c.social¹ @w3cab) meeting, after the #W3CAC meeting earlier this week.
It’s a small change, yet maybe it will inspire others.
Previously: https://tantek.com/2018/365/t3/december-too-busy-post-days
¹ Since the #W3CTAG (@tag@w3c.social @w3ctag) has an account on w3c.social, I figured the #W3CAB should too. Freshly created this week.
-
Three ways we openly document the governance of W3C:
#w3cAB: As part of driving openness in the #W3C Advisory Board (AB) and W3C in general, when I joined the AB in 2013, I created a stub AB wiki page, and worked with the rest of the AB to expand it over time, to the present where it has quick navigation to both our tools and projects¹.
#w3cBoD: Shortly after the W3C Board of Directors (BoD) was elected last year, I similarly created a Board wiki page, with quick navigation to meetings, minutes, and other publicly available Board resources².
#w3cAC: Prior AB member Art Barstow created an AdvisoryCommittee (AC) wiki page in 2012. I expanded it in the past year with sections on Email Lists and Meetings to help make it easier (more discoverable) for AC representatives to participate & contribute to the governance of W3C³.
These are all good steps, but not complete by any measure. Collectively we can do better.
Openness must go beyond finding & reading such resources.
As these are all on the W3C’s public wiki, which any W3C member (or invited expert) may edit, my hope is that anyone involved with W3C may help update such pages, and further improve them. Encouraging this kind of direct participation in how an organization is run goes hand-in-hand with openness & transparency.
¹ https://www.w3.org/wiki/AB
² https://www.w3.org/wiki/Board
³ https://www.w3.org/wiki/AdvisoryCommittee
-
Good morning from Sophia Antipolis, France, where myself and many other #W3C Advisory Committee (AC), Advisory Board (AB), & Board of Directors (BoD) members, and members of the W3C Team are here for two days of 2023 #w3cAC meetings¹.
Lots of great presentations this morning.
@cwilso.com (@cdub@mastodon.social @cwilso) is now providing an overview of the Advisory Board² and where we are with our 2023 Priority Projects³, which are done for the most part in the open, on the wiki and GitHub.
Our (AB) practice of developing our projects in the open for both W3C Members and the broader web community to see is something that myself and Chris Wilson (@cwilso.com) have been championing, leading, and driving since our first AB terms in 2013.
We strongly believe in continuing this level of transparency (or better) in the #w3cAB, and there is more work to do on the AB to make this practice an institutional default at W3C, especially in matters of governance.
Related: both Chris and I are running for re-election⁴ for the Advisory Board, and this is one of the reasons we want your support to continue serving on the AB.
¹ https://web.archive.org/web/20230509090512/https://www.w3.org/participate/meetings
² https://www.w3.org/wiki/AB
³ https://www.w3.org/wiki/AB/2023_Priorities
⁴ https://tantek.com/2023/128/t1/w3c-advisory-board-election-support
-
I am running for election in this month’s #W3C (@w3.org @w3c@w3c.social @w3c) Advisory Board (AB) election¹ and blogged my personal statement: https://tantek.com/2023/128/b1/running-for-w3c-advisory-board-ab-election
@fantasai.inkedblade.net (@fantasai@w3c.social @fantasai) is also running for the #W3CAB, and admirably blogged her imminent affiliation change *before* the election started: https://fantasai.inkedblade.net/weblog/2023/affiliation-change/ — Congrats Elika! Your new affiliation is lucky to have you.
In addition to the two of us, @cwilso.com (@cdub@mastodon.social @cwilso) also posts on his own blog and is running for the AB.
Those are the three candidates I know have their own personal #website, and was able to verify by searching for candidates on the web, #socialMedia, etc.
Three out of the nine candidates² running for election to the World Wide Web Consortium’s Advisory Board.
As I wrote in my statement:
> “I believe governance of W3C, and advising thereof, is most effectively done by those … who directly use & create on the web using W3C standards. This direct connection to the actual work of the web and W3C is essential to prioritizing the purpose & scope of governance thereof.”
I firmly believe that direct hands-on experience with using the web, beyond reading the web or using someone else’s apps, actually writing to the web, posting on the web, creating for the web, provides better insight into the technologies & standards necessary to evolve the web, how to improve them and represent the communities working on them.
I ask for your support for the Advisory Board, and support for those who create on the web.
If any other candidates have their own #IndieWeb site (or set one up!), and especially if they blog their personal statements, I will gladly link to them as well.
Thanks for your consideration.
¹ https://www.w3.org/blog/news/archives/9903
² https://www.w3.org/2023/04/ab-nominations.html
-
So the web is officially dead now, huh? #DRM #W3C #EME
-
Just two days before the #DayAgainstDRM, the #W3C approves DRM for the Web (EME) without even a commitment to defend security researchers:
https://www.eff.org/deeplinks/2017/07/amid-unprecedented-controversy-w3c-greenlights-drm-web
https://social.mikegerwitz.com/url/25959
Watch for an appeal.
-
Only a few days left to #DialUp Tim Berners-Lee to urge him to keep #DRM off the Web! Call the #W3C before 4/13 https://u.fsf.org/25y
-
W3C misses the point with inadequate security guidance https://u.fsf.org/248 #EME #W3C
-
Looks like protests against #DRM at #W3C meetings are becoming a regular thing. First ours in March, now ANSOL and AEL's in Portugal: https://u.fsf.org/1wg
-
@moshpirit !gnusocial has a small team of volunteers doing the development, much like !friendica, …
-
Why isn't !gnusocial part of the #W3C project? and why not implement the #Pump.io API as a good way to sca…
-
Just reminding everyone: #Netflix coerced the #W3C into implementing #DRM in #HTML5. They e…
-
@encycl @steve @mmn Thank Tim Berners Lee 4 selling out thy free & open web by pushing #W3C to cave to industry #EME demands #notnotevil
-
@inscius The reasoning makes no sense to me. Perhaps #Wikimedia is being lobbied hard by #MPAA like #W3C ... here comes #DRM :(
-
Not Cool: MPAA Joins The #W3C ~ !Copyright http://www.techdirt.com/articles/20140107/11263425789/not-cool-mpaa-joins-w3c.shtml
-
Beurk!! «Le #W3C entérine les #DRM» ~ http://yh5.ca/9p #WebDev
Tantek
MMN-o ✅⃠
Mike Gerwitz
Free Software Foundation
Defective by Design
lnxw48 (Linux Walt)
Alberto
laurelrusswurm
Hugo Soucy
All stadeus content and data are available under the