You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to find a guideline to cite in a TAG review, and the very long list of guidelines made it hard to know whether any of them were relevant. You should focus this document on the most critical sustainability guidelines for standards authors and web developers to follow. It makes sense to move the other guidelines to another document instead of deleting them, so that they can inform the main document's structure, and so you can pull from them when writing the next version, but they shouldn't be in the first version that you try to publish.
To pick an example, https://w3c.github.io/sustainableweb-wsg/#ensure-your-scripts-are-secure belongs in a Security IG document, not a Sustainability document. Sure, it has a marginal knock-on effect on sustainability, but I shouldn't need to read its title when trying to find sustainability principles.
This is related to #5, but you'd need to take out low-priority guidelines even if none of the guidelines overlapped.
The text was updated successfully, but these errors were encountered:
Hi @jyasskin, thank you for pointing out the issue about overlaps. There are a lot of interconnections in the Web Sustainability Guidelines with topics such as Privacy, Security, and Accessibility.
This is "by design," considering the definition of Sustainability. e.g., in the Sustainable Web Manifesto, we have Clean, Efficient, Open, Honest, Regenerative, and Resilient; also, in the definition of EU Industry 4.1/5.0 (which adds Sustainability to Industry 4.0), we have Human-Centricity and Resilience.
So, privacy is part of the Human-centric and honest aspects, like accessibility, and security is also linked to resilience.
Indeed, it might make sense to move “specific guidelines” to another document, such as referencing WCAG. Still, I wouldn't remove the references, which are useful instead (meaning, you can't be sustainable if you don't respect Privacy, Accessibility, and Security).
Obviously, this increases the weight and complexity of a single guideline that carries additional guidelines.
I was trying to find a guideline to cite in a TAG review, and the very long list of guidelines made it hard to know whether any of them were relevant. You should focus this document on the most critical sustainability guidelines for standards authors and web developers to follow. It makes sense to move the other guidelines to another document instead of deleting them, so that they can inform the main document's structure, and so you can pull from them when writing the next version, but they shouldn't be in the first version that you try to publish.
To pick an example, https://w3c.github.io/sustainableweb-wsg/#ensure-your-scripts-are-secure belongs in a Security IG document, not a Sustainability document. Sure, it has a marginal knock-on effect on sustainability, but I shouldn't need to read its title when trying to find sustainability principles.
This is related to #5, but you'd need to take out low-priority guidelines even if none of the guidelines overlapped.
The text was updated successfully, but these errors were encountered: