be-strict: Difference between revisions
Jump to navigation
Jump to search
AndyMabbett (talk | contribs) No edit summary |
AndyMabbett (talk | contribs) m (example) |
||
| Line 2: | Line 2: | ||
"'''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 microformat parsers) should be very strict in making sure that their output confirms to standards, but flexible in interpreting data received, which may not adhere to the relevant standard, but whose meaning is still unambiguous. | "'''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 microformat parsers) should be very strict in making sure that their output confirms 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?) | (Anyone got a better explanation, references, or etymology?) | ||
Revision as of 11:27, 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 microformat parsers) should be very strict in making sure that their output confirms 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?)