Other areas don’t, which keeps switching costs high. Dependency graph APIs vary by platform, vulnerability scanning integration is proprietary per forge, Dependabot and Renovate each have their own config format, and package metadata APIs differ across registries.
Areas that do not have (de facto) standards, meaning high switching costs: dependency graph APIs vulnerability scanning integration package metadata APIs are all different.
CEN TC465 Climate neutral Smart Cities and communities Initiative by ao [[Martin Brynskov p]], report published #2026/12/03
report Climate-Neutral Smart Cities and Communities in Zotero
European Standardisation Panel Survey wrt standardisation needs, wrt inno and comp. Run by #dgrtd Open until #2026/01/30
Feeds into EU standardisation strategy
EU Standardisation Strategy, d.d. #2022/02/02
The wild card remains a behind-the-scenes "Digital Bretton Woods"—standardized frameworks for transparency, due process, and appeals that let both sides claim victory while lowering uncertainty.
Not a wild card (The wild card is the zero sum behaviour of US admin), but an aimed for outcome. Standardisation, transparency and interoperability are key digital policy aims. Note that it is exactly what big tech is clamoring against at the moment.
We have to break this illusion that the organization is anything other than hired people sponsored by corporations working on some common shared goals together
well yes that is standardisation. If you exclude intended users from its creation it won't be one. A standard gets created by the intended field of users, who commit to adopting it once created. It's not idealism or altruism, it's industry.
I understand the argument that “having too many standards can hinder innovation and hurt collaborative efforts”, and while I don’t completely agree with it, I can see some validity in how the case can be made. However, telling people they’re wrong because their standard didn’t get a seal of approval
a standard is only a standard if it is adopted by those in the user group. Creating your 'own' by definition isn't a standard, at most it's a method or protocol.
Hypothesis permet d’annoter et de commenter très simplement une page web, de manière collective
Cet outil est en effet pratique, bien qu'il nécessite un compte. Je comprends le choix en terme pratique et en terme de référencement du projet. Mais n'aurait-il pas été intéressant de créer un site et un outil par soi-même? En tant que designer éditorial, il me parait primordial de réfléchir et se réapproprier la forme plutôt que de se conformer à des formes standardisées (ici une forme plutôt classique finalement). Une question très contemporaine je pense, quand on voit ce que sont devenues nos interfaces : les Géants laissent peu de place à la personnalisation, à l'appropriation des outils, et l'utilisateur est quelque peu infantilisé.