Get involved in @w3c and give input on all of our specs. See also youtube.com/@W3COfficial and @w3cdevs@w3c.social. By @dontcallmeDOM and @marieforgue
Joined October 2014
- Tweets 4,375
- Following 608
- Followers 11,339
- Likes 2,472
For all these facts and stories, meet the TAG this coming Thursday in London! ti.to/w3c-tag/meet-the-tag-l…
1
2
Example of a recent @w3ctag finding: how to help users decide about the trustworthiness and provenance of #syndicatedcontent w3.org/2001/tag/doc/distribu… @triblondon
1
2
Fact: the @w3ctag publishes findings. These are short documents that cover a specific issue in the Web architecture: tag.w3.org/findings/
1
2
The @w3ctag is also looking at how Web technologies fit with the principles of the #ExtensibleWebManifesto, i.e., can low level capabilities explain or provide the equivalent of high level features? github.com/extensibleweb/man…
1
2
's latest focus has been on pushing consistency in #JavaScript #APIs, documenting its principles along the way w3ctag.github.io/design-prin…
1
3
Fact: the @w3ctag reviews technical specifications for the Web. See what they're up to these days: github.com/w3ctag/design-rev…
1
3
Fact: the @w3ctag helps make the Web a better place for #developers by improving the consistency of Web technologies developed inside and outside W3C. Read their stories: w3.org/blog/TAG/
1
1
What is the TAG? Created by @w3c in 2001, the Technical Architecture Group serves #developers interests by driving consistent Web #design principles. Learn more: w3.org/2001/tag/ @w3ctag
1
1
4
5
Now the hard work of reviewing all these potential bugs and change requests is still to be done - but hey, you've got to start somewhere 😅
But with 200+ recommendations without an active Working Group, even tracking all these repos is a bit of a logistical challenge. We've recently set up an automatic periodic summary of the activity on repos of these orphan specifications
We're starting to track the maintained state of W3C Recommendations lists.w3.org/Archives/Public… @w3c
1
We are now trying to improve how that maintenance happens, and facilitate the publication of correction to the standards. With many of our specs developed in @github repos, we want to use these repos to track and discuss bugs discovered after Recommendation.
1
1
Some of our standards have enough of an active community that they maintain themselves, with a new working group created to formalize these updates.
But not all of our standards do - yet all of our standards need to be maintained as bugs emerge over time.
After 4 years, the JSON-LD community is now interested in bringing an update to the existing Recommendation, based on lessons learned and features that didn't make the first release json-ld.org/presentations/JS…
1
To do so, W3C would need to charter a new Working Group to take up the work - that process has now started. If you're interested in the future of #JSONLD, please bring your input on the new charter github.com/json-ld/charter/i… lists.w3.org/Archives/Public…
5
1
4
After 4 years, the JSON-LD community is now interested in bringing an update to the existing Recommendation, based on lessons learned and features that didn't make the first release json-ld.org/presentations/JS…
1
1
1
It is one of the format recognized to express data with @schemaorg_dev and is in wide use - in 2.1M+ distinct domains in 2016 according to webdatacommons.org/structure…
1
JSON-LD 1.0 provides a set of conventions for describing data in JSON that makes it compatible with Linked Data, aiming at making data easily reusable across data sets - it was published as a W3C Recommendation in 2014 w3.org/TR/json-ld/ #jsonld
1
1
and some of the derivative APIs of generic sensors: e.g. ambient light github.com/w3c/ambient-light… - incorporating the results of research in particular in the field of security and privacy is critical in improving the safety of users
They've been brought up for discussions to the relevant groups - e.g. for the work on Generic Sensors github.com/w3c/sensors/issue…+
1
@w3ctag member @lukOlejnik has authored research work on standards privacy for modern #APIs (with @s_englehardt and @random_walker). How to make privacy impact assessments of Web standards? Read kwz.me/hBZ
1
1
@w3ctag member @lukOlejnik wants to keep an eye on the possible links between Web standardisation and data privacy regulations #GDPR #ePrivacy
1
1