If you really want to be technical
OK, let's be technical. Let:
D be the number of depressed people; A be the number of internet addicted people; DA be the number of depressed and internet addicted people. T be the total number of people.
Then: "internet addicts are more likely than the general population to be depressed" means "the proportion of DA among A is greater than the proportion of D among T", or "DA/A > D/T", which is mathematically equivalent (since all number are positive) to "DA*T > D*A".
"depressed people could be less likely than the general population to be internet addicts" means "the proportion of DA among D is greater than the proportion of A among T", or "DA/D < A/T", which is equivalent "DA*T < D*A".
it is feasible that, although internet addicts are more likely than the general population to be depressed, depressed people could be less likely than the general population to be internet addicts.
No.
A general dissatisfaction with life seems to be one of the hallmarks of humanity and that is a good thing. We wouldn't be where we are if we were all content just living off the land like the other animals.
True, we would be
No, it doesn't. The summary says "more likely"; that is, as internet use increases, the probability of depression increases. That is the definition of correlation. Implying causation would be using a word like "cause". (I know, tricky concept) Which the summary doesn't.
The word "cause" would assert causation. When the summary says:
People who spend a lot of time surfing the internet are more likely to show signs of depression
it suggests causation, because that does not sound the same as:
People showing signs of depression are more likely to spend a lot of time surfing the internet
One might agree that those sentences are formally equivalent (in an idealized version of english), but the way most people speak, those sentences suggest different causations.
I think you're wrong. From the coverage I've read, it's a method of processing and manipulating XML documents, and they designed an piece of XML editing software around it which they showed to Microsoft and Microsoft then stole the ideas from.
News coverage of technical things is so effing horrible. Most tech articles are written by people who don't understand programming but don't see why that should stop them from broadcasting their misinterpretation of technical information. You should just read the patent; most of it is very clearly-written.
It does not predate XML, and has nothing to do with XML-based standards.
Filed in 1994, it does predate XML. It doesn't predate SGML, though, and since core XML is essentially the same thing, it's probably safe. However, I it does affect XML-based standards -- specifically the ones that separate content from structure/presentation.
The Patent
It's a way to separate content from structure. So, for example, where and SGML document would store data like "<p>Hi <i>friend</i></p>", they store it as two separate pieces of data. The content piece would be "Hi friend", the structure piece would be "0:p, 3:i, 9:/i, 9:/p" (roughly). So now if you wanted to format that document differently, you could just use a different structure piece; the content piece doesn't change.
This exact technique obvious, so I don't think it should have been awarded a patent. But maybe what's obvious to us in 2009 may not have been obvious to the patent examiner in 1994 and, in any case, it doesn't look like any of the affected parties are going to try and argue obviousness. The important question is how generally will their technique be interpreted?
Taken narrowly, it's a way of putting XML-like tags in a separate file, mapping them back into the content using byte offsets. This is easy enough to work around. Taken broadly, it's a way of separating content from structure. So, any time you augment the content in one file by some kind of annotations in another, you're violating their patent. So HTML and CSS are problematic because the style information is in a separate file, even though the mapping is done using tag and class names and not using byte offsets.
I don't know much about patent litigation, so I don't know how much leeway they give plaintiffs. But I doubt Microsoft Word uses their exact technique; they probably do something similar to HTML+CSS or XSLT. So this victory could indicate that the courts are interpreting the technique broadly. Which sucks. Man, patents like this are killing the industry.
In less than a century, computers will be making substantial progress on ... the overriding problem of war and peace. -- James Slagle