UK's National Rail Shuts Down Free Timetable App
JHaselden points to this "sad tale of one developer's trying time with the National Rail, the owners of the UK's train timetable data, which flies in the face of the recent assertion of Chris Scoggins (Chief Executive, National Rail Enquiries) in Wired recently stating that they had 'opened up' their data, 'often free of charge.'" This is a good case for keeping your old emails handy; the app's author uses cut-and-paste to excellent effect in his correspondence with the rail system.
What are they worried about? The risk that this might lead to customers sucessfully using their service?
# cat
Damn, my RAM is full of llamas.
And you are a silly person. Now go away or I shall taunt you a second time, you silly English Knnnniget!
Whenever in an argument, remember this.
The key bit in their Code of Practice for access to the data ( http://www.atoc.org/about-atoc/national-rail-enquiries/code-of-practice ) is:
"Whether the proposed use is of additional benefit to passengers. Applications which in NRE’s reasonable opinion are of demonstrable
benefit to passengers will be granted unless outweighed by a material adverse impact on TOCs (whether financially, strategically, operationally or in regards to their reputation or the reputation of the industry as a whole)."
So their own code says they will kick you if you financially impact the TOCs (Train Operating Companies). ie. You produce a free product which competes with their own mobile apps.
Those pedantic about either spelling or grammer are ultimatly the sad pathetic people who sit alone out in the kitchen at parties picking at their nails trying to not make eye contact with anyone.
Conversely, they may be people who care passionately about using language The Right Way -- much as Star Wars nerds will correct you if you assert that Han was Leia's sister, or that Luke build R2-D2. Pursuit of perfection is something which all nerds do to a certain extent, especially programmers. If I tell you, "your code example is missing braces on your 'if' clause, so it won't evaluate the way you want it to", I'm not trying to be an asshole. Think of it as a verbal compiler error. Ironically, many programmers take the perspective that writing in English is something in which correctness and conformity to convention doesn't matter -- and yet we must be extremely correct when coding.
Think back to school? did anyone like that kid who used to correct the other kids grammer? no. no they did not.
What can I say - no one likes being exposed as wrong.
There is no standards body for the english language, if someone says something and you understand it and the meaning you get is close enough to what they intended then it's perfectly good.
Natural language is too ambiguous to parse. You cannot always guarantee that someone will understand what you mean, and errors in word choice, punctuation, or spelling only compound that. People who care about communication take the time to be courteous to their listener/reader, and write/speak in a way which they know the audience will not mistake. If you can't be bothered to follow the conventions which guide English language (even if they aren't codified the way French is), you're either a visionary literary mind (e.g., e e cummings) or you need an editor.
The OED is considered by many to be a definitive reference for spellings and word meanings. I'm not sure where one would find a grammar reference - googling for one was not immediately useful. Still, not poor spelling is, in the age of the internet, a sign that one doesn't care about spelling it right, rather than not knowing the spelling. Unless you've mangled the word (and even then), Googling for it will give great answers. Sometimes Google corrects it, and other times the first page of results gives the answers many times over. ("orderves" -> "how do you spell orderves" -> "hors d'oeuvre") In short, spelling errors are a sign of either unnoticed typogaphical mistakes or of laziness, and when they're systematic people will tend to assume the latter.