Just over I year ago I posted the first government social media release, using an in-development microformat, hRelease. Since then, I have issued 7 more releases using this format (you can see them all on the e-government site). During the course of that year the markup has evolved as I worked with the hRelease working group, ably led by Shannon Whitley, to move the proposed standard up to draft status.
This week saw another incremental shift as I published the first of these social media releases (SMR) with commenting enabled. Most of you will no doubt be wondering why I have buried the lead (SSC has a blog?
), but I figure that there are plenty of other capable people to spread the word.
In any event, IABC has now taken up the leadership of the Social Media Release and, as I will continue to contribute a public sector perspective to the process, I thought that it might be helpful to share some observations about the the impact for SSC of issuing semantic media releases over the past 12 months.
How effective is it?
Naturally, it depends upon where you draw the bottom line: media pick-up, comments, saves to social sites, there are any number of valid approaches to the issue. In most of these cases, however, these releases would have to be judged abject failures.
Another way of making the same point: at the launch I was chatting with a journalist, and I asked him if there was any value in the SMR for him. He stared blankly back. Figuring that I was talking passed him, I tried a more practical tack. Was he finding the del.icio.us links helpful? The reply? What’s delicious?
.
Now that doesn’t mean that the del.icio.us links are a waste of time. There are currently six people who have at least a passing interest in what is being bookmarked, it just so happens that none of them work in the local media…
On the other hand, a couple of hours after the portal launch SMR went out, I issued this traditional release about changes to the ICT branch. The result? See for yourself.
Is it worth the candle?
Marking up your releases semantically does impose an overhead. Is that a justified use of resource? I would argue yes. Journalists here may be slow to pick up on the new format, but with every release, you are making an investment in the future capability of the namespace.
If all government news releases were marked up using this format, the newzealand.govt.nz search tool could return search results for all news items restricted to a certain geographic area, or about specific topics, within timeframes etc. These results could in turn be parsed into news feeds for local or topic specific sites (including those outside the .govt.nz domain), thus creating far more public value than an individual agency release buried on its site.
Another point that I have made in the past is that public sector communicators can’t afford to think of metrics solely in terms of media. They are a primary audience, but we have a responsibility to ensure that these news releases are discoverable and accessible by the widest possible constituency.
Conclusion
Whether or not hRelease makes it to a draft microformat stage is really an academic issue for me. I will continue to mark up the releases as semantically as possible and to argue for others to do the same. Yes, you should cover the basics and write sharp, factual and informative news releases. The question you should also be asking yourself is, why don’t I spend at least as much time ensuring that the release is as well crafted semantically as it is grammatically. That just is the reality of communicating in the age of the Internet.









3 Comments
Top work and very Agile of you (”just do it” and all that).
I totally agree with your 3 points about why use micro formats – it makes the information far more available, findable and most importantly usable. Usable in ways we cannot think of at the moment.
Thanks Mike. Doing it is the easy part: convincing others to seize the nettle is a little more challenging…
This is one of the situations where a computer could actually help … if only those that write CMS (and the like) incorporate the functionality – it’ll come as the likes of Yahoo! and Google start to support/push it AND browsers start to display/use it.
I think then people will see the benefit to themselves and then out to the wider world of ‘data sharing’
Could be a little like “RSS” – the technology is irrelevant to the users as automagically it starts to “appear”