This document is also available in these non-normative formats: XML.
The Power of 10: Rules for Developing Safety-Critical Code
The Power of 10 Rules were created in 2006 by Gerard J. Holzmann of the NASA/JPL Laboratory for Reliable Software.[1] The rules are intended to eliminate certain C coding practices that make code difficult to review or statically analyze. These rules are a complement to the MISRA C guidelines and have been incorporated into the greater set of JPL coding standards.[2]
The Specification Is Not a Document - The Phoenix Architecture
Imagine joining a software project a few years from now. It is a large, mature system. It has thousands of business rules, years of operational experience,…
The lost art of XML — mmagueta
There exists a peculiar amnesia in software engineering regarding XML. Mention it in most circles and you will receive knowing smiles, dismissive waves, the sort of patronizing acknowledgment reserved for technologies deemed passé. "Oh, XML," they say, as if the very syllables carry the weight of obsolescence. "We use JSON now. Much cleaner."
Uncertainty limits the use of power analysis.
Operationalizing the Legal Principle of Data Minimization for...
Article 5(1)(c) of the European Union's General Data Protection Regulation (GDPR) requires that "personal data shall be [...] adequate, relevant, and limited to what is necessary in relation to...
Chromium Docs - The Rule Of 2
When you write code to parse, evaluate, or otherwise handle untrustworthy inputs from the Internet — which is almost everything we do in a web browser! — we like to follow a simple rule to make sure it's safe enough to do so. The Rule Of 2 is: Pick no more than 2 of
Home | Laws of UX
Laws of UX is a collection of best practices that designers can consider when building user interfaces.
Configurable Per-Query Data Minimization for Privacy-Compliant Web APIs
The purpose of regulatory data minimization obligations is to limit personal data to the absolute minimum necessary for a given context. Beyond the initial data collection, storage, and...
Web 2.0 ... The Machine is Us/ing Us
W3C Manual of Style
This manual is a guide containing best current practice, written for editors and authors of W3C technical reports. No requirements for W3C publications are in this document. All requirements for W3C publications are in W3C [[[PUBRULES]]].
Data Minimisation: a Language-Based Approach (Long Version)
Data minimisation is a privacy-enhancing principle considered as one of the pillars of personal data regulations. This principle dictates that personal data collected should be no more than...
Tailoring Legal Protection for Computer Software
Peter S. Menell, Tailoring Legal Protection for Computer Software, Stanford Law Review, Vol. 39, No. 6 (Jul., 1987), pp. 1329-1372
Design Tokens Format Module 2025.10
This document describes the technical specification for a file format to exchange design tokens between different tools.
All 12 Tips for Concision | LEGIBLE
Since July 2015 I’ve been sporadically posting a series of tips for concision in legal writing. I suggested a total of twelve, and links to all of them are collected here: