StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>i think, a better question is, "how to write a good specification?" ...</p> <p>most RFCs are bad specs, in my eyes ... personally, i quite hate them ... they are still better than ECMA-specs, but that's not a real criterium i think ...</p> <p>for example: compare <a href="http://www.json.org/" rel="nofollow noreferrer">JSON-"specs" on json.org</a> with the <a href="http://tools.ietf.org/html/rfc4627" rel="nofollow noreferrer">actual RFC</a> ... i do agree, the first is not 100% exact (well, actually it is more exact then most JSON encoders), but in a few lines and a few syntax diagrams it says where JSON comes from, what its usage is, and defines the format ...</p> <p>i don't see a real point in writing endless RCFs, because in the end noone reads them leading to the point where</p> <ul> <li>you don't get the comment you requested for</li> <li>people make implementations without really knowing your standard</li> </ul> <p>if you really want to propose a standard, or make it comprehensible, do not use documents with countless pages ... it's just a waste of time ... when the standard is mature, you can start bothering making a very formal and strict definition, which is a good basis for highly consistent behaviour accross implementations, if it is really clear ...</p> <p>do not obscure ideas by using too many strange and invented words, abreviations or refering to thousands of other things ... the simplicity of a solution is a measure for it's actual worth ... and treating the reader of your document, like a slightly dumb alien, to whom you have to explain everything, but at the same time expecting they can follow unjustifiably complex and bloated explanations, does not seem very sane to me ... just <a href="http://en.wikipedia.org/wiki/K.I.S.S." rel="nofollow noreferrer">KISS</a> ... ;)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload