be-strict: Difference between revisions
Jump to navigation
Jump to search
m (noted possible etymology) |
AndyMabbett (talk | contribs) (Disadvantages?) |
||
Line 7: | Line 7: | ||
(Anyone got a better explanation, references, or etymology?) | (Anyone got a better explanation, references, or etymology?) | ||
* I believe this is a variant of [http://en.wikipedia.org/wiki/Jon_Postel#Postel.27s_Law Postel's Law]. Having had many years developing and implementing standards, IMHO there are both plusses and minusses to Postel's law. [[User:Tantek|Tantek]] 08:23, 26 Mar 2007 (PDT) | * I believe this is a variant of [http://en.wikipedia.org/wiki/Jon_Postel#Postel.27s_Law Postel's Law]. Having had many years developing and implementing standards, IMHO there are both plusses and minusses to Postel's law. [[User:Tantek|Tantek]] 08:23, 26 Mar 2007 (PDT) | ||
**Disadvantages? [[User:AndyMabbett|Andy Mabbett]] 08:34, 26 Mar 2007 (PDT) |
Revision as of 15:34, 26 March 2007
Be strict in what you send, but generous in what you receive
"Be strict in what you send, but generous in what you receive" is a principle in computing (originally referring to e-mail), which suggests that systems (such as e-mail relays or microformat parsers) should be very strict in making sure that their output conforms to standards, but flexible in interpreting data received, which may not adhere to the relevant standard, but whose meaning is still unambiguous.
See hcard-brainstorming#ADR with no children for an example of how this might be applied.
(Anyone got a better explanation, references, or etymology?)
- I believe this is a variant of Postel's Law. Having had many years developing and implementing standards, IMHO there are both plusses and minusses to Postel's law. Tantek 08:23, 26 Mar 2007 (PDT)
- Disadvantages? Andy Mabbett 08:34, 26 Mar 2007 (PDT)