This is a post about location (for a change); but it doesn't have to be about location as it's all about mistaking a vital element for the end game itself. I should explain.

I recently got contacted by a gentleman in the US who was looking to register a lot of domain names, in a manner which recalled the rush to buy domain names in order to make a profit as the dot com boom rushed headlong to become the dot bomb bust and which resulted in the unlovely pass-time of domain squatting.

After seeing a lot of mention of location, location based services and location based mobile services in the media, the position of location based services on Gartner's most recent hype curve and seeing a lot of acquisition activity in the location space, he was looking to register domain names with LBS in them.

Hyperlinks in the form of web links are the lifeblood of today's internet and world wide web. Examination of your web server's log files, either directly via tools such as Webalizer or indirectly via analytics services such as Yahoo's or Google's can show you who's visiting your web site or blogs.

But who's visiting your site isn't the whole picture; following a hyperlink is an active process. To complete the picture you need to find out who's linking to your site, which is a passive process.

If you're running a blog you may be able to use trackbacks or pingbacks to find out when a site links to you, but only if the linking site support the trackback or pingback protocol and then only if this is enabled on both sides of the ping relationship.

So what about those sites which don't support trackbacks or pingbacks or who don't want to be discovered that they're linking to you?

I've never run or hosted my own search engine. I've run and hosted web servers, mail servers, proxy servers and caching servers (I'm even contemplating running my own URL shortener), but never a search engine. There was a time when I ran an enterprise instance of Alta Vista back when I coded for a living and was part of the team building Factiva.com, but that doesn't count.

If I had have run my own search engine I would have known just how important canonical URLs are and that having multiple copies of the same content hosted on different domains would cause search engines to penalise you and loose search engine ranking, fast.

I've never been a massive fan of Crowded House but 1991's Four Seasons in One Day could have been written with this weekend's weather in mind. We started with Winter (cold, wet, miserably damp), followed by Spring (heavy showers, glorious sunshine and the odd rainbow or two), followed by Summer (clear blue skies).

Last night I was at LBi in the old Truman Brewery on London's Brick Lane for Mashup's Location ... It's Moving On. I've spoken at a Mashup event once or twice before but this time the organising team threw caution to the wind and asked me to chair the panel discussion.

Prior to kicking the panel discussion off, I attempted to gently suggest some topics to my fellow panelists that we might want to discuss.

We started off with a quick review of my Theory of Stuff and how it applies to deriving value from location and location data and briefly visited Gartner's hype curve which puts location based services on the so called Plateau of Productivity. This is a good thing apparently. I then presented the panel with a series of  "yes, but" style trade offs to mull over.

• Smartphones vs. other phones; 21% of phones expected to have GPS by EOY 2009, but what about the other 79% without?
• LBS and LBMS vs. other (older) location systems (APIs and so on); LBS and LBS apps get all the publicity but what about key location APIs, platforms and services?
• "where's my friends" vs. creating value and creating data; "where's my friends" doesn't work as a (sole) business proposition but creating value added data does -- FourSquare and Gowalla are creating geotagged local business listings from check ins.
• "where's my business" vs. location based advertising; Tesco and Starbucks are the latest companies to launch apps to drive customers to their premises, but what's needed to drive location based ads?
• "where I think you are" vs. "where I say I am"; For a user, being able to be their own source of truth is imperative, but how can you reconcile this with your business needs?
• "where you are" vs. "where you've been"; (AKA tracking vs. privacy) How to walk the fine line between providing enhanced relevance via a user's location and being accused of tracking them.

As Paul Clarke has pointed out on his blog, not once, but twice, "I assert that train operators know where their assets are: it would be irresponsible if they didn't. And that this information is held within their internal systems".

Here's a good use case for his proposed solution ... wheresmytrain ...