Public Appointments by RSS

In the words of Directgov:

A public appointment is an appointment to the board of a public body or to a government committee. Around 18,500 men and women hold a public appointment.

The public bodies involved are quite important, including health trusts, museum boards and regulators, some demanding specialist skills in law or social work, but many requiring general common sense and broad experience. So it’s important that the people who fill these posts are of the right calibre and reflect the diversity of our society.

The Cabinet Office has recently revamped its Public Appointments system, and you can now sign up to sophisticated email alerts about public appointments vacancies you might be interested in. As a publisher of vacancies, the central system also has an excellent API, enabling you to extract data feeds from the vacancy database to republish on your own site. There’s even some RDFa in the output should you wish to use that to mark-up the vacancy descriptions.

I’ve just created and added a dead simple RSS feed for the BIS-related public appointments to our homepage. But anyone can grab the code and set it up to generate their own feed, or indeed re-publish the vacancy data far and wide in any format compliant with its licence, in order to help spread the word about the interesting and varied positions available.

Hurrah for open data and APIs, and above all, hurrah to the Cabinet Office for building one in this case. Thanks chaps.

Why I’m going dark for purdah

When the General Election is called, and government enters the pre-election phase known as purdah, I’m going to suspend my personal blogging and tweeting at least until the results are announced.

Why? In a word, it’s too risky.

This will be the first election with really active social media. Last time around, Whitehall Webby (2007) was still a glint in the virtual eye, along with Facebook (2006) and Twitter (2007). Even Guido had been going less than a year (Sept 2004) only just outdone by Tom Watson – one of Parliament’s earliest blogging MPs (2003).

Now, things are different. The political blogosphere is enormous, connected and credible. Mainstream media figures blog and tweet alongside their primary channels, and use those new sources for stories and feedback. And like millions of others, including hundreds if not thousands of British civil servants and a number of old university friends now running for Parliament, I’m blogging and blathering in a variety of other social media.

Mainstream journalists covering my Department’s issues, politicians of all parties and party workers are amongst the 1,200 people who follow me on Twitter (along with a sprinkling of some exotic young ladies from Las Vegas who seem really keen to meet me). And I simply don’t know who’s reading this, which is generally where much of the fun comes in.

But elections (and, I’ve learned, reshuffles) are different: the rules on civil service behaviour are stricter, the scrutiny is much more intense, and the knives are sharper. Frankly, in a climate of pressure on civil service headcount, it would be unwise to stray too far from the pinstriped fold during this particular period at least.

It’s likely the Cabinet Office will be issuing updated guidance this year to help people in my position to stay on the right side of the rules, so watch that space. But personally and pragmatically, I’m not sure any rules will be enough to keep individuals truly safe given the nature and norms of media coverage of bloggers and tweeters currently. Pretty much any personal comment on a public service, a media figure or government initiative or public reply to a politician or even a colleague is going to be susceptible to selective reporting out of context or misattribution as an official or professional view. Sad but, I think, true. Safer simply to go mute.

For me, it should be an enjoyable break. I suspect there’ll be plenty of work to do on the other side

Be Brave

Photo credit: Sharon O’Dea

Well, that’s another UK Gov Web Barcamp wrapped up, and #ukgc10 was a corker, not least thanks to the sterling efforts of Dave Briggs to organise the thing, and the generosity of Google in hosting us.

It still impresses me that 120-odd people from all over the country would want to give up their Saturday to talk about government, technology, data and engagement. But it seems we still do.

A little local difficulty meant I missed the morning sessions, unfortunately, but still had a great time in my former colleague Kim’s session on social media for internal communications, Stefan Czerniawski’s session on improving transactional services online,  and Simon Dickson’s obligatory salon on WordPress (lots of practical questions and note-taking; we’ve clearly moved on from when WordPress was a just a wow new technology).

I jointly did a session with Anthony Zacharzewski and Paul Clarke on persuading politicians and bureaucrats of the value of digital engagement in a climate of cuts. I loved Anthony’s take on the language issues at stake, and his segmentation of the evidence which persuades political and administrative masters, which was bang on the money. My own slides are here:

In a nutshell, I suggested three approaches to making the case:

• Making digital engagement just part of the process of policymaking, not a special set of ‘innovative’ tools to be piloted
• Explaining the changing digital world and the digital engagement activity we do in terms of the real-world impact it has on our own people, our stakeholders, our customers and our costs (a tough one for policy-led environments)
• Pointing to the good company we’re in, not just the wide range of public sector examples of the use of these tools, but also the private sector application of them for customer service and business development

My bottom line was: this is a time to be brave, and argue the case for digital engagement in government as a driver of more efficient and effective policymaking and ministerial engagement – as well as a more cost effective route to service delivery.

Adding RDFa to a consultation

Recently, I’ve been involved in a project to ensure our consultations support RDFa markup, to make them indexable and reusable by third parties, including Directgov. Without duplicating the quite accessible and useful COI guidance, I thought I’d summarise here the process involved from the perspective of implementing the standard with minimal prior knowledge of the whys and wherefores.

Why bother?

As of Jan 1st 2010, it’s now a mandatory requirement for government sites. But more importantly than that, it’s a Jolly Good Idea to provide a low-maintenance way of enabling other systems and services to grab a list of consultations from your site, and identify the important metadata about them, including the closing date and how to respond. Short term, it will make services like TellThemWhatYouThink and Directgov more useful, but in terms of the bigger picture, it will expose the opportunity to get involved with policymaking to a wider audience, and reduce the hassle for those who are already part of our regular stakeholder group (by making possible new services such as auto email alerts, RSS feeds, cross-government updates and so on).

What’s involved?

RDFa offers a simple way to add meaningful information to existing web pages, which can be extracted easily by software (as opposed to hit-and-miss ’scraping’ of regular web pages). As a lay person, I’d say there are three key principles which I can articulate:

1. Be unobtrusive and minimalistic: taking this approach lets you add extra items to pages which aren’t seen by regular browsing visitors, but which are accessible to software robots looking for them. It’s also not ‘an extra thing’ to maintain and serve like an RSS feed, so reduces risk, in theory.
2. Offer clean data: through being consistent in how data about the consultation is described, the idea is that RDFa helps to extract very clean information about the consultation – for example, an unambiguous closing date, a response email address, an exact postcode, all in formats which can then be used in other ways (plotted on a map, listed on a calendar, turned into a mailform on a website etc)
3. Extend existing conventions: the most complicated aspect of implementing this particular specification is that the authors have gone out of their way to find existing wheels rather than reinvent their own. So they use Dublin Core metadata to describe authors and organisations; vCard to describe response contact information; plus nods to DBPedia and FOAF (Friend Of A Friend) to support these major semantic web initiatives. Only for the  gaps where specific consultation information needs to be marked up is there a new standard introduced, using the namespace (prefix) argot.

In a nutshell, the process involves tweaking the template for your consultation pages, adding extra metadata elements and attributes. This is only as easy or hard as your CMS makes it. It’s important that it’s right though – even a few ‘broken bits’ could render the page useless to a software robot trying to extract data from it.

How to do it

Read the COI guidance (and give it to your developer), which is the most comprehensive guide, with useful illustrated examples. There’s also a worked up HTML page showing how this works, and of course you’re welcome to look at ours (which I *think* are right, based on feedback from the gurus).

As an example (but again, you should read the official guidance) I found I needed to work through the following:

• ensure we have a single page per per consultation
• amend the DOCTYPE, if you’re using something like the standard XHTML strict/transitional version. Needs to tell requesters of the page that it contains RDFa
• add some attributes to the <html> element, highlighting the namespaces (vocabularies) you’re referencing in the document
• add Dublin Core metadata elements/attributes to your page <head> element if they’re not there already
• ensure we have a wrapper <div> around the consultation information which again references the namespaces (vocabularies) you’re using. This also identifies the name of the organisation publishing the document
• add some Dublin Core metadata attributes as <spans> within this <div> identifying this as a consultation
• add some Dublin Core attributes to key bits of the HTML, such as the consultation title, start date, closing date and description, marking these as such – and in the case of dates, ensuring there’s a machine-readable data format value in the attribute. Also add a unique identifier – a reference number – to each consultation (not something we’d done routinely before)
• ensure the contact details for responses is carefully structured using vCard format, with separate ‘Full Name’, ‘Street Address’, ‘Locality’ and ‘Post Code’ elements, suitably marked-up with attributes. Since vCard doesn’t cover the specific case of a consultation with an email reply address, for example, these elements are marked up with the new argot: namespace attributes
• add Dublin Core-based attributes describing the file attachments – the consultation document itself, and any related ones such as appendices or Impact Assessments

UPDATE: in retrospect, it was foolish to attempt a blog post about code without some code examples. I’ve tried and failed to find a half-decent code syntax highlighter plugin for WordPress, but the following couple of screenshots hopefully illustrate the before and after situations for the contact information part of a consultation:

Before, plain HTML:

After, with RDFa added (and marked up more semantically as a list item within the consultation metadata)

What help is available?

I worked from the examples given in the COI guidance and the pioneers in this at the Ministry of Justice. The COI Digigov team are your allies in helping to implement this, and should be able to answer queries and/or direct you to sources of further implementation advice and support.

In terms of online tools, you can see whether your RDFa is visible to suitably-equipped applications using Mark Birbeck’s tool or bookmarklet, if you prefer (and he should know; he invented RDFa).

Good luck!

P.S. If you Know About This Stuff and feel I’m giving duff advice here, please drop me a line in the comments or via the contact form and I’ll correct. Thanks.

Unleashing a Government response

A quick one – today at work we’re launching ‘Unleashing Aspiration’: the Government’s response to the review of access to the professions, which was led by Rt Hon Alan Milburn MP and reported last year.

The digital brief was, on the face of it, not massively exciting – it’s a long document, covering 88 recommendations, with a small but informed audience of policy, media and stakeholder visitors – many of whom will go through the whole document in detail almost however we publish it.

But this kind of document does set an interesting challenge for online presentation – it’s really as close as policy documents get to a faceted classification in information design terms, with responses to each recommendation organised by theme, by audience affected, and by the Departments who are leading on each – and with lots of embedded links to other initiatives. The policy team, though tight on resource, are interested in following the comment and discussion around each of the recommendations.

So it’s also a natural fit for WordPress, where the Themes are defined as WordPress categories, and we use WordPress tags to indicate audience and lead department. Commenting is built-in, as is the facility for tag and category descriptions, which provide a space for useful ‘virtual chapter’ overviews. By offering the ability to cut the document up in so many ways, it provides a variety of accessible entry points for different audiences, which is promising raw material for digital engagement outreach, for example to student communities or the third sector.

It’s not going to win any design awards – it’s intentionally quite neutral and clean with just some simple colour-coding – but I think it’s an unusual and potentially helpful approach to enable readers to get into a document of this kind through different routes. It’s also been a good training exercise for the team – props to Alistair Reid for getting his head around the anatomy of WordPress in barely a week, and doing rather more cut-and-paste than is strictly healthy.