AutoTag: AutoLink/SmartTags done right

In all the debate about Google's AutoLink feature I've seen virtually nothing about how the AutoLink/SmartTag (AutoTag anyone?) concept could be made to work better with the notable exception of Don Park who was right on the money weeks ago Fixing AutoLink. Obviously there are points of principle that need to be debated; the right of an author not to have their content altered and allowing users to escape from a mass of inward-looking links.

But rather than complaining and hoping the problem will go away, how about trying to address these issues by building a better AutoTag?

  1. Require authors to opt-in by requiring them to make their content explicitly auto-taggable. For example have them mark-up such content [see previous post] 
    <span class="autotag" type="address">
This is an address
</span>
  2. The first time auto-taggable content of a particular 'type' is found, ask the user if (a) they want such content auto-tagged and if so then (b) which of a selection of services do they wish to link to.

An additional benefit of (1) is that it can be easily extended to handle different types of content - no need to code the magic required to identify content and its 'type'. Consequently it would be possible to identify both books and films by name.

With respect to (2) it should be noted that Google already provide access to a variety of mapping services, but they default the service to their own.

From my perspective as a user, there is a lot to be gained from AutoTag functionality done right. And it doesn't stop at linking up to remote web services. The same approach can be used to link from web pages to desktop applications. For example it is frustrating to have to cut information from a web-site and then paste it piece-meal back into a form to update contact/event information, especially when there are perfectly good machine readable formats to do the job.

Clearly it is unreasonable to expect a lone web-site author to do the work required to convert the human-readable information they have at hand into the arcane machine-speak required to talk to Outlook, let alone a range of desktop and service based apps. But perhaps the same author could be persuaded to wrap a few angle-brackets around what they know to be the crucial information. The problem could be solved with the help of a few remote 'helper' services that could accept text fragments, parse them and return suitably formatted and mime-typed responses.

I don't know how difficult it is to write an IE toolbar or a Firefox extension, but I'm hoping/guessing that most of the heavy-lifting is being done by the services that are being linked to. Thankfully there are mapping services that can deal with addresses and don't have to be talked to politely using coordinates.

What we need is a neutral switch embedded in the browser that can route auto-taggable content from the web-pages we view to the services of our choice.

Technorati tag:

Comments

Post a Comment

Popular posts from this blog

A Review of hReview

microformats may well represent a path from where we are today to the [lowercase] semantic web. If so, one of the first waypoints along such a path could be the emergence of aggregators capable of taking advantage of suitably marked-up content. Applying a 'microformat' approach to tagging, Technorati introduced the rel="tag" approach to marking-up tags. Technorati also supply the corresponding aggregation service, e.g. see posts tagged with microformat . Given this minimalist approach to tagging, the hReview specification comes as something of a surprise. It seems to represent a format developed independently of the environment in which it is most likely to be used. The rel="tag" approach makes a major, simplifying assumption. This is that the tag refers 'to a major portion of the current page (i.e. a blog post)' . I am assuming that it could apply equally to a blog entry in an RSS/Atom feed. Thus an aggregator can associate a tag with two p
Read more

SmartLink

Image
In a previous post I tried to describe how I thought technologies like SmartTags and AutoLink ought to behave. With greasemonkey in Firefox I've been able to build a proof-of-concept demonstrator. For the moment I'm calling it Smart Tag/Auto Link. SmartLink is based upon the idea that content authors should mark-up content that can be 'smart-linked', using standard XHTML constructs. This has two advantages: it effectively provides an 'opt-in' mechanism for content providers it doesn't require 'magic' to identify what can be smart-linked and thus provides a much more extensible approach. of course there is one fairly major disadvantage: there isn't any suitably marked-up content out there, with the exception of some test posts I've put together for the purpose. Getting Started If you want to know a bit more about SmartLink then click here . Alternatively if you want to see how SmartLink behaves and you're using Firefox t
Read more

Speculations about developing with iCloud

It's been three months since Apple revealed it's vision of the cloud to the world. After its introduction, much was written (e.g. It Just Works ) about how iCloud compares 'philosophically' with others, most obviously Google. Now, supposedly close to launch and with iCloud in the hands of developers, there seems to be surprisingly little written about how that philosophy translates into developing a modern iOS app. Apple promises consumers that things 'will just work'. Just keep using apps in the same way and they will magically remain up-to-date across all your devices - in truth I'm not sure more magic was promised. Apple might be making a similar offer to developers. In principle iCloud means that an ObjectiveC developer with XCode can create and distribute apps containing this magical ingredient without having to learn any new skills, without having to develop any cloud-based components at all. What's more, with relatively little extra work, they c
Read more