Personal data usage: what your car really says about you

By -

Stumbled across this article on the motoring page of the Guardian newspaper.

Cars will soon be so linked into wireless networks they will be like giant rolling smartphones. Ford has already started to integrate web services such as Spotify into their dashboard systems and this looks like the first step to introducing a real-time data collection service to your car. This new vision of in-car big data goes far beyond the current engine management monitoring that garages use when you take your car in for servicing.

A few examples of this brave new world:

- Low on fuel? Soon a petrol station app may know before you do.
- Tyres need rotating? Your car may wirelessly alert your dealership when it's time.
- Ready for a lunch break? Your car can make a reasonable guess based on the hour.

Are these realistic? Well, according to the article "…more than 60% of vehicles worldwide will be connected directly to the internet by 2017, up from 11% last year, predicts ABI Research. In North America and Europe, that is likely to reach 80%.". That means a lot of new data streams to be harvested by car dealers, manufacturers, insurance companies, finance companies etc. Not forgetting law enforcement agencies! Our every movement within our car could be tracked and interpreted by all sorts of agencies. 

As always the issue is going to be how has access to all this information because at the moment few laws exist to govern who can see and use such data.

The article is here: http://www.guardian.co.uk/technology/2013/mar/12/cars-internet-data-privacy-debate.

Comments

Post a Comment

Popular posts from this blog

My query just got faster - brief introduction to 12.2 in-memory cursor duration temp tables

By -
Image
Image courtesy of wikipedia This post covers one of the new SQL performance enhancements that we incorporated into Database 12c Release 2 . All of these enhancements are completely automatic, i.e. transparent to the calling app/developer code/query. These features are enabled by default because who doesn’t want their queries running faster with zero code changes? So in this post I am going to focus on the new In-Memory “cursor duration” temporary table  feature. Let’s start by looking at cursor duration temp tables… Above image courtesy of wikimedia.org What is a cursor duration temp table? This is a feature that has been around for quite a long time. Cursor duration temporary tables (CDTs) are used to materialize intermediate results of a query to improve performance or to support complex multi step query execution. The following types of queries commonly use cursor duration temp tables: WITH Clause and parallel recursive WITH Grouping Sets S...
Keep reading

SQL Pattern Matching Deep Dive - Part 1

By -
Image
There has been quite a lot of interest in the new 12c MATCH_RECOGNIZE feature for SQL pattern matching. Therefore, I thought now would be the perfect time to start a series of quick deep dive posts that explain how SQL pattern matching works. Over the coming weeks I will cover the following topics in a series of posts. This is the start of a series of posts based on a presentation that I put together for the recent annual  BIWA conferenc e at Oracle HQ. The Oracle BI, DW and Analytics user community always puts on a great conference and this year was the best yet. You can download any or all of the presentations from this year’s conference by following this link . My pattern matching deep dive presentation started life about a year ago as a post covering some of the new keywords in the explain plan that are linked to pattern matching, see here . It has now expanded to cover a much wider range of topics. Firstly, a huge vote of thanks to my development team (Lei Sheng and Chun-Chie...
Keep reading

SQL Pattern Matching Deep Dive - Part 6, state machines

By -
Image
The obvious way to start this particular post is to pose a couple of simple questions: what is a state machine and why should you care? In general I would say that you don't need to know about or care about state machines. That's the beauty of using SQL for pattern matching. The MATCH_RECOGNIZE clause encapsulates all the deep technical modelling and processing that has to be performed to run pattern matching on a data set. However, there are times when it is useful, probably vital, that you understand what is going on behind the scenes and one of the most obvious situations is when backtracking happens. Therefore, the content covered in this post is a going to be a gently lead-in into my next post where I am going to discuss the concept of “backtracking”  and the dreaded  ORA-30009 error. Let’s start our voyage of discovery…when you attempt to run a SQL statement containing a MATCH_RECOGNIZE clause during the compilation phase we generate a finite state machine ba...
Keep reading