« July 2005 | Main | September 2005 »

August 19, 2005

Building a feed for our calendar

19 August 2005 This week we'll describe two ways to build a feed which can be used to disseminate the events calendar which we built last week. The easy way to build a feed is to use a Weblogging tool such as Movable Type. Simply build a weblog with only one entry which we'll update regularly to give us the two months rolling calendar. Movable Type does all the hard work, and all we'll do is cut and paste the calendar information into it. You can see how that might look here. And of course, the entry is made available as a feed automatically by Movable Type.

For those who are interested in what a feed really consists of, let's also build one manually.

A feed in its simplest form is a file with a specific format, in our case, RSS 2.0. While there are other formats (such as Atom), for the moment, RSS 2.0 is the most common. It is quite a flexible format and as you'll see it is not that difficult to create.

RSS 2.0 feed dump
First there are the XML and RSS pre-ambles:
<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0">
Everything happens in a "channel":
Give the feed a title and link to the parent page:
<title>Tax Due Dates</title> <link>http://www.activeweb.com.au/index.php?option=com_ content&task=view&id=18&Itemid=28</link>
Describe the feed:
<description>Due dates for Australian Tax Office submissions and payments</description>
The language it's written in (Strine):
The way it has been generated:
A link to the RSS spec:
Ask to be read no more often than every 60 minutes:
At last, this is where we get down to business. A fee can have more than one item, ours only has one.
For us the title of the item is the same as the feed's title:
<title>Tax Due Dates</title>
The feed represents the event calendar at:
And here is the payload of the feed:
<description> This is where we put our Calendar data </description>
Here is the publication date of the item:
<pubDate>Mon, 15 Aug 2005 17:00:00 +1000</pubDate>
Every feed needs a globally unique identifier, we'll use the feed's URL for that.: <guid isPermaLink="true">http://activeweb.com.au/cal/taxfeed.xml</guid>
Here is the publication date of the feed:
<pubDate>Mon, 15 Aug 2005 17:00:00 +1000</pubDate> <lastBuildDate>Mon, 15 Aug 2005 17:00:00 +1000</lastBuildDate>
And close the "brackets"
</channel> </rss>

The full feed can be seen here .Of course, we would not normally create this manually. Using a tool like Movable Type or doing it programmatically is a much better option. The purpose of doing it manually here, was to take the magic out of it and show how it's done.

Posted by Marius at 11:57 AM | Comments (0) | TrackBack

August 12, 2005

Building our Tax Calendar

12 August 2005 Last week I promised to follow up on my quest to find a practical solution for building an online events calendar. Something like the one on this site, but with a convenient way of building a list of events, regularly feeding it to the web site and giving users a simple way of importing the events into their calendar (hopefully, not just Outlook).

A good way of thinking of the Web today is as "small pieces loosely joined". We'll therefore try and build the calendar without writing any code, using readily available standards, software components and services.

The calendar should be easy to update remotely. Using RSS means that a feed will periodically update the calendar on the site, while also giving users the option of getting updates without going to the host web site. The Mambo CMS which is used on the current website already has a component which accepts RSS feeds, so that issue has already been solved for us.

Despite the fact that commentators feel that calendar interoperability is a train wreck, for the moment, RFC2445 is what we've got and hope that we can make a simple application like this work without re-inventing the wheel. As it happens, there is an event database , EVDB, which already exists, uses existing standards and does almost everything we require.

EVDB site showing tax calendar

While it is tuned for time & place style events, it wasn't hard to enter the events and build a calendar with the tax dates. EVDB already has ICAL and RSS exports, so it looks like we have our solution. Unfortunately, a few practical issues get in the way. We're looking to build a feed which simply lists all due dates for a rolling two month period, rather than individual posts as they are created. EVDB features a developer API to access the database and build whatever we like, but for the purpose of this exercise, we want do this project without programming.

The little ICAL button on EVDB's individual entries, however, implements the import feature just like we would like to use in our calendar. It allows us to download that entry or import it directly into a calendar. Looking at the content of the file, we see it is pretty straight forward:

DESCRIPTION:Payments for August 2005 due.
In principle, we have a solution:

Now that we've built the calendar, next week we'll find a practical solution for building a RSS feed.

Posted by Marius at 11:39 AM | Comments (0) | TrackBack

August 05, 2005

Seven hundred thousand calendars

5 Aug 2005 If you use Google to search for the words "online calendar", you'll get 725,000 results. Online calendars are something people need or think they need. And even more interestingly, something software developers like to build!

The trouble is that interoperability between calendars is a mess. Even though a standard (RFC2445, or iCal) was created back in 1998, interoperability between competing internet calendar software is a mess. I haven't been a great user of calendars such as the one in Outlook, but for a recent project, I was called upon to make recommendations for an online calendar. It was for use in a calendar listing like this tax calendar. Accountants amongst my acquaintances will probably copy the entries and pencil the dates on their paper calendars. But now that we're starting to use vCards to import contact details into systems, why not have a solid standard for importing and updating calendar entries as well? When you find an event description on a web page, it should be as simple as a click a link to import that event into a diary and another link to subscribe permanently to events on that calendar.

The Web changed the way our customers perceive technology. They simply expect things to work. Things need to get easier. More widely accepted, simple standards, less vendor lock-in. Today, there is no widely accepted solution for what I described above. Next week, we'll look at what's available today and how we might apply it.

Posted by Marius at 05:20 PM | Comments (2) | TrackBack