Category Archives: Data

A buncha quick stuff

EFF highlights an Australian House Standing Committee report on the US DMCA, and whether or not it should be adopted wholesale by Australia under the Free Trade Agreement.

Meanwhile there’s an open letter to the OFLC about the banning in Australia of the grafitti video game Getting Up: Contents Under Pressure. (Mind you, Metacritic only gives it a 73/100 on XBox; 70 on PS2).

OPML 2.0 is out. Let’s hope it doesn’t break OPML 1 like RSS 2 broke RSS 0.9?

The Age on the retro games boom.

Pah, this sucks. After 64 years in Swanston Street, the Technical Bookshop in Melbourne has moved out to the boondocks of LaTrobe Street near Queen Street.

Play School dumps clock with Big hand, Little hand

Monday morning I discovered that Play School has dumped the clock with Big hand, Little hand. I was running late to work, and while Owen was being breastfed Play School came on, and I overheard the presenter reading out the time. No more Big hand on this, Little hand on that.

I remember that some kids got analogue clocks quickly when we learnt in grade 3, and others just didn’t get it. My dad has always said that digital clocks aren’t an appropriate way to measure time, especially in a wrist watch or wall clock – because that’s not the kind of time you’re interested in – 19:37 is actually half past seven, or maybe a bit after half past – the precision is false/meaningless precision.

Oh, and in case I’ve been misleading you, the hands are now called Long hand and Short hand; clearer to the kids because the hour hand, whilst shorter is also stubbier, which could make one think it was larger. And no longer in this day and age is shorthand as common as it once was, so the risk of confusion there is reduced. And in a subsequent viewing of Play School (I’ve been home sick – stupid baby), they were back to Big and Little, so perhaps the presenter misspoke.

Oh well, time marches on…


While we’re here, a little tip: time should only ever be stored and (inter-system) communicated in UTC. If you’re designing a database that has time fields, for The Love of Sweet Merciful God store the time as UTC, regardless of the hoops involved in adjusting to that time zone. Because, when it comes to query, and you’ve got to start allowing for the fact that when daylight savings ends there are two 02:17s – and one came before the other; in addition you have the difficulty of knowing if the time on the clock was wound forward/backwards correctly – Australia has so many states with different time zones, and a propensity to diddle around with when the changeovers are meant to happen. Whilst effective, it is not desirable to use the “solution” one company I worked for went for – shutting all the machinery down for an hour when the clocks rolled back (especially given this was at the peak of processing for the day, not some idle time – and I mean business processing, not running the computer centre!). And figuring out when something happened in one time zone, compared to another, is a nightmare if all you’re storing is localtime; but equally, getting comprehensible output is tough if you’re not storing localtime alongside UTC. Here endeth the lesson.


Thursday night I had a dream – no, stick with me, this is relevant and interesting. Anyway, for whatever reason I had to build an analogue-to-digital clock converter, out of Lego. Now, I know how I did it in the dream, and on reflection, it would have worked. As a hint, I used Lego Mindstorms (in the real world I don’t earn enough to own, or for that matter to have ever touched, Mindstorms).

How would you construct an analogue-to-digital clock converter out of Lego?

Why your life shouldn’t be completely online

Why your life can’t be completely online yet: Cameron Reilly on what happens when the only copy of your flight details are in your Gmail… and Gmail goes down. (Hey Cam, look on the bright side — assuming you knew you weren’t flying out of Avalon, there’s only a handful of possible airlines you could have been travelling with, and their terminals at MEL are pretty close together. Are you a fast runner?)

A foray into corporate blogging

I’ve convinced the company I work for to start a corporate blog. So far it’s early days, with myself (blogger extraordinaire) being the only one brave enough to post anything (apart from an introductory “this is what we sell” post), but I’m hoping the others will also contribute, as the company markets a mucho good product, and there’s a lot of good knowledge of B2B, XML, and development in general, locked up in the various brains around the place.

eVisionRSS feed

Online trip planners

Outlook now has links to MSN Mappoint, providing driving directions. Though I never drive in or out of central Melbourne unless I absolutely have to, I decided to see if it and a competitor, Multimap.com, could plot me a path home.

The main problems with these types of map sites is

  • the data is inadequate (often a problem with international companies trying to cover lots of cities), or
  • the mapping software decides you should do something wacky (which I’ll admit, is often down to the data again, though sometimes it seems to be the algorithms used)

Mappoint wanted to know which of two identical “247 Flinders Lane” addresses I wanted to use. I tried both, and both gave the wrong position along Flinders Lane. (Not bad, but a search for an address on Collins Street gave me 8 to choose from.)

Mappoint question

Mappoint also told me to drive down Kingsway/Queens Road, then do a right hand turn at St Kilda Road. Most Melbourne locals would know that you can’t do a right hand turn there. Like, physically, you can’t. Queens Road passes under St Kilda Road. If you want to do a right hand turn, you have to do a left a bit earlier and go via Union Street.

Mappoint directions

Multimap found the right spot in Flinders Lane. It then suggested I go left into Elizabeth Street (okay), left into Flinders (okay), then right into St Kilda Road — wrong! No right turn allowed there.

Rather than send me straight down St Kilda Road, it had me take a right via Albert Road to Queens Road, then left via Union Street back onto St Kilda Road. Pointless and confusing.

But it gets better. Rather than drive straight down St Kilda Road/Brighton Road/Nepean Highway, it got me to do a quick diversion around some of the side streets of Elsternwick, before turning back onto the highway. WTF?!

And according to Street-Directory, one of those side streets is actually blocked off to through-traffic. Pure genius!

Multimap directions

Lest you give up and decide to catch public transport, rest assured, the Connex trip planner is no better. Instead of telling me to walk half a block to Flinders Street station, it instead got me to unnecessarily wait for a tram to go three blocks to Flagstaff station.

In the past it’s provided even more stupid directions, suggesting you catch a tram in the wrong direction, then another back again, or needlessly change trains.

(PT umbrella organisation Metlink is working on a better planner, and are considering feeding their data into the new Google PT planner, too.)

It seems no matter which way you’re travelling, it doesn’t pay to trust the online trip planners just yet.

RSS isn’t mainstream yet

Scoble argues that RSS’s importance isn’t in how many people are using it, but who those people are.

He’s right, but the other point to make is that RSS isn’t mainstream yet. Email and the web are mainstream, but took years to catch on with the general public, even after being widely available. RSS is widely available, but only used by a minority of the general online population.

That will change, as the tools used by the great unwashed pick up and highlight RSS functionality. That’s not Newsgator or Firefox, but IE and Windows.

It’ll change as the influential early-adopters persuade others.

And it’ll change as the standard is sorted out — not just the XML, but how it’s advertised — that orange button needs to be ubiquituous, just like “www” and “.com” in URLs are now.

So if your site doesn’t support RSS now, it’s important to get it doing so very very soon.

Backup, backup, backup

I was sick at home for a couple of days last week, and while pottering about the house blowing my nose, found some old floppy disks. I decided to move all their data onto CD, and in the process found some old articles I wrote in 1997 for an abortive gig as a columnist for a US-based magazine. Some of them are still relevant, so I’ll re-post them here every Monday for the next few weeks.


In the computing world, stories abound of people losing large chunks of work. This never used to happen, because people used to use far more reliable, but arguably less productive, methods of working. Like paper. Okay, so if all your work was on paper, you could lose large chunks of it, but this tended to be because of something disasterous – an enormous fire, perhaps – and in that situation, life and limb is going to be the first priority, not your work.

Modern technology however, has brought with it a multitude new and exciting ways of losing all your work. Hard disks can crash, or develop errors. They can be accidentally formatted. Your files can be moved, deleted, corrupted, overwritten. This is why you need to take very good care of your files. Back them up regularly, or the day may come when your work is lost and you don’t have any way of recovering it.

A few years ago, I was working writing software for a big company. My colleagues and I had performed a true miracle of coding, and had delivered a piece of software that would change for the better the lives of hundreds of people working in that particular bit of the company. Okay, so it wasn’t going to solve third world hunger or bring world peace, but we were very pleased with it.

One Friday afternoon, I was looking on our shared network drive at the files that made up our masterpiece, when I noticed something odd. Some of the files and directories that I expected to be there, weren’t. I looked again. More were missing. They were disappearing before my very eyes.

I, not to put too finer point on it, panicked. I sent a system broadcast message asking anybody who might be listening “Why are the files on N: disappearing?” I looked again. The files stopped disappearing, but most were already gone. The phone rang. I answered it.

“Uh oh”, said the quavering voice of the LAN Administrator on the other end of the phone. He had been given the task of clearing up one of the file servers. He had used a utility’s PRUNE command to do it. A flawless plan. Just one small snag. Wrong server.

No problem, right? Go to the backups, right? Wrong. It just so happens that the LAN people at this place had been a little lax in the backups department. For about 3 months. Yes, THREE months. It was when we realised this that we decided to call this day “Black Friday”, and we spent most of the rest of the afternoon moping around the office looking miserable. You can bet that if there had been supplies of alcohol available, they would have been consumed quite rapidly.

As it happens, there was a consolation. I had copied many of our more important files onto my hard drive, a mere three weeks before Black Friday, “just in case”. Three weeks’ work lost wasn’t exactly a cause for celebration, but it was better than three months’.

I didn’t feel vengeance towards Mr Pruner. Mistakes happen. What wasn’t forgivable, in my book, was the conduct of his boss, whose responsibility it was to ensure that the backups happened, so that when mistakes like that happen, the files are recoverable. It’s just as well that he’s substantially bigger than me, otherwise murder might have been committed that day.

The moral of the story is this: Make sure your files are backed up. Frequently. Double-check that it’s actually being done. Triple check, even. If someone else does it, make a spare set yourself occasionally. If you don’t, then make sure there’s plenty of alcohol in the office fridge. Because when Black Friday hits you, it might be the only help available.

Office goes XML

Microsoft has announced the next version of Office will use XML by default — that is, Word, Excel and Powerpoint will use XML documents embedded in Zip files. They will also issue updates to those Office products back to the 2000 versions so they can use the new formats.

The XML will be documented, and open — to the extent that you will need to acquire a free licence from Microsoft to use it, on their terms presumably.

The terms of the licence will be interesting. You could contrast this to the MDB (Jet) format, which while it isn’t XML, and isn’t an open format, is quite well documented in its use via the various Microsoft libraries you can use to get at it (ADO/MDAC, DAO, etc). It’s interesting to note that Jet is royalty free, so you can give Jet databases to anybody if you have a Microsoft developer tool, though the one thing you can’t do is build a solution that does much the same thing as Microsoft Access. (It’s a similar story for all their other develop tools).

So the question is: will the MS licence preclude people from building, say, an alternative word processor or spreadsheet that can read and write the format? Will OpenOffice be able to use the format for interopability?

They imply no such restrictions will exist, with this to say on whether opposing products will make use of the format: Customers also know that the true value of a desktop application is not the format in which data is stored but the full breadth of capabilities offered by that application, along with the quality and security of the user experience that it providesSteven Sinofsky, Senior VP, Office.

Obviously switching to XML opens up a number of possibilities, making it much easier for third party applications to delve into documents to read/write data, without mucking about in the Office object models (which in turn ties you to COM and Windows). You could use XSLT to convert documents into other formats, or to display on new devices or applications.

It should lead to interesting developments, and let’s hope the other Office applications follow suit.