Category Archives: social media

Everything at your postcode – proposal for a new website

13 Replies
0000-0001-5882-6823

Over the last few weeks, I have been imagining a website for UK citizens and visitors; where they can enter their postcode and be served a page or pages of hyperlocal links about everything to do with where they live. This post is me continuing that thinking out loud; comments — including the constructively critical — are actively solicited.

Links could be almost anything, from local government services (via DirectGov and OpenlyLocal) to public transport information; from maps to fun things. They would either link to sites which use postcodes as as an argument; or would be built using the target site’s postcode-lookup API.

The site would avoid the need for each hyperlocal website to compile its own list of such links.

Here are a few such links, based on a randomly-selected postcode, B23 6UH (I simply opened a local newspaper and picked the first advert that used a Birmingham postcode). Note that the first link is computed; the rest use the postcode directly.

User would also be able to suggest additional links if they find a good web service which takes a postcode as a locator — for now, please feel free to do so in comments on this post, and I’ll add them to the above list. Purely commercial links, like individual chains’ store locators, would be excluded (a few paid for links, clearly identified as such, might generate enough revenue to cover hosting costs).

As can be seen from the above, the site wouldn’t actually store or generate content; just links. The links could be clustered under headings, or on sub-pages, like “maps”, “local services”, and “fun stuff”.

It might also be possible for the site to determine the user’s nearest postcode, using their browser or device’s GeoLocation feature, or by selection from a map. The site would also accept partial postcodes, such as “B”, “B23” or “B23 6”.

The service could perhaps be “widgetised” for inclusion on other sites. And of course, it would be possible to link to the site using postcode as an argument.

The site would, of course, make data available in RSS, OPML and open data formats; and use microformats.

Unfortunately, though be willing to collate and maintain the links and code some HTML, I lack the programming and graphic-design skills to make such a site, which means that I must rely on the good will of others. Can you help? Should I organise a hack event (a day, or an evening) at a Birmingham venue, to work on this collaboratively?

Or does such a service — curated, rather than spammy — already exist? Would it belong better as an adjunct to an existing service like OpenlyLocal or DirectGov?

Over to you…

More police forces should publish web pages about wildlife crime officers

10 Replies
0000-0001-5882-6823

I maintain the West Midland Bird Club website. The club serves the four English counties of Staffordshire, Warwickshire, Worcestershire and the Metropolitan West Midlands, and so I wanted to write a little bit about the work of the relevant police services’ Wildlife Liaison Officers (WLOs), and to link to web pages about each of them.

I was surprised to find that none of their websites have a page about their WLOs, or their approach to wildlife crime in general. So I started to look at other forces’ sites, and found very few of them did.

What I Wanted

I decided it would be a good idea to collate a list of the few good examples that exist and conversely the forces which don’t have such a page, not least to encourage them to provide one.

A quick Google search showed that no such list is already in place, so my next step was to check — on Twitter, of course — whether anyone else was working on one. The answer was no, but two projects have more generic lists of police websites and related details in hand: OpenlyLocal and Podnosh.

I decided that I would have to make the list happen for myself, but I wasn’t going to do all the work. of OpenlyLocal kindly offered use of his data on police forces and their home pages and other contact details — it’s open data, under a CC license. That was in XML, though, and I lack the skills to manipulate it, so Chris kindly and quickly provided a dump into CSV format, suitable for use in a spreadsheet. A salutary lesson, there, to anyone publishing open data. While RDF and linked data is the way to go, so that it can be parsed and processed by machines in an sophisticated way, making a format like CSV available as well opens that data up to less technically-gifted users.

How I Did It

I copied the relevant columns from Chris’ document into my own, and made the editable spreadsheet available in Google Docs, for anyone to edit. I then blogged about it, inviting people to help me to full the missing column of wildlife crime pages. I was quickly retweeted by several people and organisations (thank you for that) and, significantly, the initiative was mentioned on the Guardian website by . This resulted in spate if activity, with most of the rows completed within a day or so after the mention. Interestingly, the spreadsheet filled up from the top, so it seems that unknown volunteers were helping with the first gap they came to, rather than that for their local force, which is what I had expected.

A few people shoe-horned prose comments into the URL column, so I added a “notes” column and moved their comments there.

After a few days, only a couple of gaps remained, so I filled these myself, and locked the spreadsheet prevent vandalism (any amendments may be posted below, as comments).

Findings

So, whet did we find? Of 51 forces, only 29 have a wildlife crime page — and some of those are patchy. Other forces don’t have one, but mentioned the work of their WLOs in press releases, progress reports and policy or strategy documents — sometimes in PDF files.

In some cases, a search of the force’s website for “wildlife” returns no result at all — a disappointing state of affairs.

PC Duncan Thomas, Wildlife Liaison Officer with Lancashire Constabulary

On the other hand, there were some great examples of best practice, including Lancashire Constabulary, Merseyside Police and North Yorkshire Police, from which other forces can learn. Note that they variously make use of video, and have links to wildlife conservation bodies.

Also of interest is this , reproduced on Coldean Residents Association’s hyperlocal site.

What next

This is what I hope will happen now:

  • Each police force should set up a locally-relevant web page about wildlife crime and their response to it, with relevant contact details, modelled on the best practice we found.
  • These pages should have short, permanent URLs so that links to them will not decay when forces change their technology
  • A central police website could ask an enquirer their postcode or address (or simply geo-locate their browser), and type of concern, then return the relevant page (whether it’s about wildlife crime, drug dealing or lost property) using the model adopted by LocalDirectGov
  • Websites listing details of all UK police forces’ details — like OpenlyLocal and Podnosh — could include their wildlife crime URLs
  • Wildlife websites with pages for each county (for example, Fatbirder, BirdGuides etc) could include the relevant forces’ wildlife links.
  • Local wildlife organisations (Wildlife Trusts, county bird clubs, RSPB Local Groups) should link to their local forces’ wildlife page

How you can help

  • Publicise this blog post and the open data that’s been genreated
  • Make use of that data
  • Write to your local force, if they don’t already have a page, and ask them to provide one — feel free to send them the URL of this post
  • Ask your councillor to encourage the local force to do so
  • Ask your local Wildlife Trust, bird club or related organisation to do the same
  • Let everyone know about the results, in the comments below, or with a pingback from your own blog post

I’ll notify national organisations like the RSPB, RSPCA and British Trust for Ornithology.

Meanwhile, if you wish to report wildlife crime in progress, call 999, or otherwise report it to Crimestoppers (who will treat the report as anonymous if you wish) on 0800 555 111.

Thank you

Finally, thank you to everyone who’s contributed to this project, to date.

Updates

20 August 2010: was missed, because it was on a separate site, where their site’s search didn’t find it. It’s now been moved to the main site, as a result of this post.

3 September 2010: Northumbria Police pages created in response to this campaign.

June 2011: Staffordshire Police page created in response to this campaign (per their e-mail).

When writing about the web, links are required

1 Reply
0000-0001-5882-6823

Today’s Telegraph has an interesting article about MPs (and their agents) allegedly bowdlerising articles about themselves on Wikipedia.

What it doesn’t have, though, are links to any of the articles, let alone to the edits under discussion (such as this edit).

The Telegraph needs to understand that the word “Web” in World Wide Web refers to the interlinking of articles on different sites.

Adding links to the articles and edits discussed would serve at least two purposes. It would provide evidence to support the allegations the paper is making; and it would be a convenience and a courtesy their readers.

Manu Sporny recommends me on LinkedIn

1 Reply
0000-0001-5882-6823

I hope you will forgive me for immodesty repeating Manu Sporny’s kind and fulsome recommendation of me, from my LinkedIn profile, for the benefit of those of you who don’t have accounts there:

I had worked with Andy in the Microformats community, developing international standards for the Web. During this time Andy not only excelled at providing technical feedback and review, but led several bold initiatives to standardize the classification of planetary-geo-location and living species on the web. While a logically consistent and wise technical contributor, his influence on the direction of the community was also vital. Andy’s role in questioning and influencing the core philosophy and community process was and continues to be deeply appreciated.

I’m genuinely touched by that. Thank you, Manu!

Manu Sporny is CEO of Digital Bazaar.

Twitter: A microformat in lieu of a protocol

8 Replies
0000-0001-5882-6823

In May of this year I wrote about the problems of URLs for a given Twitter user’s profile, or for an individual post or “status” being different, depending the Twitter client in use. I suggested a new protocol for Twitter links. [You might want to read that, before the rest of this post]. I can’t believe I didn’t think of this simpler solution sooner!

The answer (in the short term) is to use a microformat (or a microformat-like “poshsformat”, if you prefer to call it that) for each case. Let’s say we use the classes twitter-user & twitter-status.

User-agents (that’s jargon for browsers) could then employ a script (such as those used by GreaseMonkey, or a Firefox extension) to ignore the encoded URL and substitute the equivalent for the user’s preferred Twitter client instead.

For links to user profiles:

<a
href="http://twitter.com/pigsonthewing">
Andy Mabbett
</a>

would become:

<a
class="twitter-user"
href= "http://twitter.com/pigsonthewing">
Andy Mabbett
</a>

and:

<a
href="http://accessibletwitter.com/app/user.php?uid=pigsonthewing">
Andy Mabbett</a>

would become:

<a
class="twitter-user"
href=" http://accessibletwitter.com/app/user.php?uid=pigsonthewing">
Andy Mabbett</a>

Likewise, for individual statuses:

<a
href="twitter.com/pigsonthewing/status/1828036334">
something witty</a>

would become:

<a
class="twitter-status"
href="twitter.com/pigsonthewing/status/1828036334">
something wittyg<a>

and:

<a
href="accessibletwitter.com/app/status.php?1828036334">
something witty<a>

would become:

<a
class="twitter-status"
href="accessibletwitter.com/app/status.php?1828036334">
something witty<a>

and:

<a
href="m.slandr.net/single.php?id=1828036334"
something witty</a>

would become:

<a
class="twitter-status"
href="m.slandr.net/single.php?id=1828036334">
something witty</a>

To simplify matters, the rules for extracting the user ID or the status update could be the same in both cases:

  1. Parse the value of the href attribute of the element to which the class applies.
  2. If there is a question mark, use everything after that.
  3. Otherwise, if there is an equals sign, use everything after that.
  4. Otherwise, use everything after the last slash.

That would deal with all the examples in my earlier post.

So, if you’re using a user-agent which is aware of this microformat, and find on a page:

<a
class="twitter-user"
href="http://twitter.com/pigsonthewing">
Andy Mabbett<a>
said
<a
class="twitter-status"
href="m.slandr.net/single.php?id=1828036334">
something witty<a>

but your preferred Twitter client is Dabr (one I recommend, BTW!) then your browser would treat (and possibly render) that as:

<a
href="dabr.co.uk/user/pigsonthewing">
Andy Mabbett<a>
said
<a
class="twitter-status"
href="dabr.co.uk/status/1828036334">
something witty<a>

Simples!