375 karma · joined May 1, 2011
It seems that the on appeal, the full bench decided that google was actually responsible - given their algorithms were responsible for placing the ad in the context.
This doesn't seem to be quite the same as the ambush marketing you mention. That would be more placing an ad for "dell" when searching for "elegant mobile personal computer".
Be aware about issues between mod_wsgi and that approach - http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Appl...
I think it's clearer to see the distinction between an information model and a storage model: The fundamental goal of an information model is to provide a mechanism to convert input information into output information. But if the model is so degenerate that it just echos back the same data in the same format that was put in (at a different time), then it's probably better to call it a storage model.
The relational model is a logic system that lets us use predicate calculus to infer from one set of propositions taken to be true, a second set which is by implication true. That is, it provides a means to obtain encoded answers in response to encoded questions applied to a body of encoded facts.
And a KV store is clearly a storage model.
And there are some in-between, such as the CouchDB document store, that can transform one body of information to another, but also pay attention to physical storage issues.
A passphrase defeats that threat. And integrating the ssh agent with something like the gnome keyring means you never even have to remember your passphrase.
cperciva is giving 2 examples: (1) use a service provider that doesn't require your trust. (2) limit the exposure of customer sensitive information to your employees that you must trust to keep it private.
I agree this is a better strategy than simply updating a privacy policy, as far as actual security is concerned.
Are you skeptical that a domain for that scenario exists?
You highlighted the element of referential integrity within their description, whereas I highlighted atomicity. But both are just operational characteristics of the database.
Halpin's CWA comes into play even within a database that is not being updated and has only one relation. Eg. Consider a relation P that models the fact type that person with NAME was born on DOB. P = { {NAME: Bob, DOB: 2/2/22} }
CWA answers the query "Was Mary born on 2/2/22?" with False.
This is the first time I have heard the expression "Closed World Assumption" used to refer to transactional atomicity.
For example, the Terry Halpin textbook "Information Modeling and Relational Databases" describes the CWA thus:
> When modeling a business domain, one may take different positions with respect to the completeness of the information captured in the model. The Closed World Assumption (CWA) is the assumption that all relevant facts are known (i.e, appear in the model, either as asserted facts or derived facts) and that all the relevant business rules are known.)
I find this discrepancy in academic terminology difficult to reconcile.
> The subject line of one e-mail read: “This is a terrorist threat! Take this seriously.” “I swear to God I’m going to kill you!,” part of the message to Biden said.
Not sure why you think he didn't threaten to kill. Seems he was found guilty.
I for one find bitcoin far more "intellectually gratifying" than the hiring thread, which, with great respect to our host, has no interest for me.
But copyright is interesting. Generally, copyright is held by the photographer. Who is the photographer in this case? The one who blindly operated the camera by remote control? Or the one who unknowingly pointed the camera to the subject? Perhaps there is no copyright here.
How about arresting a journalist in order to seize his iPad is like holding the owner hostage while his TV gets stolen?