« July 25, 2005 | Main | July 29, 2005 »

Thursday, July 28, 2005

Privacy: Murderer Ratted Out by Customer Fidelity Card

According to an article in the July 28, 2005 issue of L'Hebdo, on October 29, 2003 an immigrant from Kosovo living in Winterthur, Switzerland murdered his wife with 20 blows by a hammer. At trial, he claimed that the murder was a crime of passion, and that he seized the hammer, which happened to be at hand, in a fit of anger.

Unfortunately for the defendant, when he bought the hammer immediately before returning home to commit the crime, he handed over his customer fidelity card, not wanting to forego the rebate points due for the purchase of the CHF 21 murder weapon. The store in question not only records the identity of the card-holder and the amount of the purchase, but a detailed list of each item bought. This database entry, introduced at the trial, sufficed to prove premeditated murder, for which the perpetrator was sentenced to 13 years in prison. (Yes, that seems a tad light for killing your wife with a hammer, but that's how murder sentences in Switzerland tend to run; come for the scenery, stay for the murder. Note, however, that the convicted was 73 years old and won't be getting out until he's 86.)

Both of the two largest Swiss retailers report they've issued about 2.1 million customer fidelity cards, which is a pretty remarkable market penetration when you consider that there are a total of 3.2 million households in the country. Most people don't care if the store keeps track of how much milk, bread, and cheese they buy, but when purchasing murder weapons, it's best not to let them swipe your card.

Posted at 21:09 Permalink

Reading List: Persistence, Macros, XHTML, and Tools Download

I have just completed an overhaul of the tools used to produce the reading list document. Previously, while direct links to books were persistent ("permalinks" which did not change when books were added to the list), links to lists of books by author or topic were ephemeral--most of them changed every time a new author or topic was added. The new version creates the names for author and topic index files by transforming the actual author or topic name into a unique form suitable for use as a file name, which guarantees that links to the HTML index files won't break. For example, is is now possible to link directly to books by E. E. "Doc" Smith, or books on economics.

In addition, the text files from which the reading list Web tree is built now may contain macros which are expanded into frequently-used HTML links. A complete link to a book on Amazon.com, including associate program information and target window, may be written as just "<Amazon ISBN>", where ISBN is the book's International Standard Book Number. (Did you know, by the way, that the process of transitioning ISBNs from the current 10-digit standard to 13-digit ISBNs is now afoot, with January 1, 2007 set as the date when the publishing industry is supposed to use 13-digit ISBN-13 numbers exclusively? . . .always scribble, scribble, scribble.)

The HTML files generated for the reading list are now XHTML 1.0 compliant, and a validator button has been added to the navigation panel which validates whatever document is shown in the main document frame. Since the comments for a book may contain arbitrary HTML markup, care must be taken not to use something which violates the XHTML 1.0 standard. The entire book list may be validated by displaying "All Books" and then clicking the validate button. (This is a big file, takes a while to transfer, and may time out; if it does, the individual year documents can be validated successively.)

Finally, the tools used to build the reading list are now available for downloading, as a GZIP compressed TAR archive containing the Perl program which generates the HTML tree and all the support files (style sheets, static HTML documents, images, etc.) it references. Little or no effort has been expended to make these tools and documents portable--while they'll probably work on any system with a recent version of Perl, you'll have to make lots of little changes to customise the results for your own site. This will involve digging into the code, which is utterly undocumented and completely unsupported--you are entirely on your own.

Posted at 16:28 Permalink