Please Help Me to Compile a List of UK Police Forces’ Wildlife Crime Pages

As a birder and general nature lover, wildlife crime concerns me. Whether it’s the poaching and smuggling of ivory and tiger parts, the disturbance of nesting birds, or badger baiting, I want it stopped.

Of course, it’s the responsibility of each police force in the UK to act against such crimes, and to take seriously reported incidents. Some forces appoint specialist “Wildlife Crime Officers”, under various titles. Some have web pages about such officers and their work against wildlife crime, like this excellent example from North Yorkshire Police. Others, sadly, do not.

I’m interested in finding out which police forces do have such officers, and which publicise their existence online. But that’s a big task, and I can’t do it alone. So I’m asking for your help.

Please have a look at this spreadsheet on Google Docs (many thanks to OpenlyLocal for the list of forces and their home pages). Find your own (or any!) force, and, if it’s not already listed search its site for a wildlife crime page. If you find one, add its URL to the spreadsheet. Otherwise, enter “none”.

I’ll find a permanent home for the results; hopefully that will encourage forces which do not have a page about wildlife crime on their website to add and maintain one.

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.

My Open Data Challenge to UK Local Government: a Wikipedia Page for Every Council

At yesterday’s excellent West Midlands “Open Data: Challenges & Opportunities” event, hosted by the West Midlands Regional Observatory, Chris Taggart (), who runs the very useful Openly Local website, aggregating data about councils and their elected members, mentioned the problems he has extracting linked data about councils from Wikipedia, via DBPedia, because Wikipedia tends to conflate places with their local authorities.

See, for example, the Wikipedia article on the Metropolitan Borough of Dudley; or those on , which (at the time of writing) has only a small section on its town council and Lichfield district (so a challenge there for Stuart Harrison, , and his colleagues!); and compare them with the separate articles about and ; or , the , and . The former, all-on-one-page, pattern is far more common. (Disclosure: I created some, and have edited all, of those articles.)

I suggested at the event that this problem could be solved if staff from each UK council simply started a Wikipedia article about their council, where none already exists.

As each UK council is, inherently, (to use the Wikipedia jargon) notable, there should be no issue with this, provided that they are mindful of Wikipedia’s policy on conflicts of interest (which explicitly allows for such editing), and the requirement that articles maintain a neutral point-of-view, and be referenced. Short “stub” articles can be created in the first instance.

(If council staff are hesitant to do so themselves, then I can help to pair them up with volunteer Wikipedia editors who will assist them, or create articles directly.)

Update: Added Dudley & Lichfield district examples.

When writing about the web, links are required

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.

Lists in Microformats: Suggested Optimisation

Based on my extensive experience of applying microformats to templates in Wikipedia (and other MediaWiki installations) I’ve come to the following conclusion…

For attributes which can occur more than once (such as nickname or category in hCard), lists having, or in container having, that property should be parsed as lists of individual instances of that property.

For example:

<div class="category">
<ul>
<li>ornithologist</li>
<li>driver</li>
<li>gardener</li>
</ul>
</div>

and:

<ul class="category">
<li>ornithologist</li>
<li>driver</li>
<li>gardener</li>
</ul>

should be treated as equivalent to:

<ul>
<li class="category">ornithologist</li>
<li class="category">driver</li>
<li class="category">gardener</li>
</ul>

BBC Balloon Release Complaint

Here’s a complaint I lodged with the BBC, on Saturday, 30 January 2010, with added links and image:

Prof. Jim Al-Khalili, on the BBC’s ‘Chemistry: A Volatile History’, (ep. 2) released a big, red, helium-filled balloon, with a string attached.

On its return to earth, the balloon will become litter. Balloons are harmful to wildlife, as documented by the Marine Conservation Society.

The Environmental Protection Act 1990 unequivocally makes it is an offence to drop ‘or otherwise deposit’ litter in a public place.

The Marine Conservation Society are campaigning to stop balloon releases, both by persuasion in the short term and, eventually, through prohibitive legislation. They are supported in that campaign by a large number of reputable organisations, including the RSPB, the RSPCA, the National Farmers’ Union, the Tidy Britain Group, Keep Scotland Beautiful, county bird clubs, various Wildlife Trusts and other organisations.

Please make it BBC policy to forbid the release of balloons, as many other organisations have done.

I’ve e-mailed a courtesy copy of the complaint to Prof. Al-Khalili. I’ll let you know what responses I get.

Manu Sporny recommends me on LinkedIn

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

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!

Bacchus Bar, Birmingham. Awful.

I spent yesterday evening, from 7–11, in , Burlington Arcade, Birmingham, one of Mitchells & Butlers supposedly “Classic Pubs”. Had I not been there as a guest of others, for whom I have great respect, I would have left.

The only guest ale was off.

The dirty plates left by the departing people whose table we occupied, and their and our empty glasses and bottles, were not collected once. The plates included uneaten food, which sat festering for four hours.

The men’s toilets were an utter disgrace: stinking, awash with urine – footsteps caused audible splashes; I’m going to have to have my trousers laundered – and clearly not attended to all evening. Everyone who entered, each time I was in there, commented. I was told the women’s toilets were little better.

A pile of vomit on the carpet outside the toilets was marked with a “wet floor” A-frame, but otherwise left for over an hour, remaining until after closing.

I have never seen such bad practice, even in run down inner-city pubs; let alone a supposedly prestige, and pricey, city-centre venue.

Update: I have contacted Mitchells & Butlers, and asked them to respond here. Their contact form includes several unnecessary yet mandatory questions, such as wanting my postal address (which I declined to give, using bogus data instead) and the number in the party, which must be a number, making it impossible for me to say “over 15”.

Machine Tagging Flickr

I’ve posted some more thoughts on machine- (or triple-) tags and microformats on Flickr, in their Flickr Ideas group.

Update: There is now a tool to automatically generate tags for Flickr images of living things; iNaturalist tagger.

I am not a Twitcher!

Three times this week, people have referred to me, in good faith, as a “twitcher”. I’m not, and I blame lazy tabloid hacks for creating this misconception, which I will now try to lay to rest.

I am a birdwatcher or, if you will, a birder. I like to be outdoors, with my binoculars and sometimes a telescope, to watch birds. I like to travel to different places, such as hills or the coast, to see different kinds of birds, but I also like to watch common birds, like Starlings, in my garden, or as I move around my home city.


[Picture: Common Starling, Sternus vulgaris, from Creative Commons, by Paul Stein; licenced under Attribution-Share Alike 2.0 Generic.]

I like to know their life histories, and to read about and study their behaviour, their conservation and their contribution to human folklore.

All together, this brings me a great deal of enjoyment, and helps me to de-stress after spending long hours at a desk in front of a computer, or in stuffy meetings, in my day job. I try to pay some of it back, by sharing my interest with non-birders, and beginners, and by doing voluntary work for the RSPB and the West Midland Bird Club, of which I’m a trustee.

Occasionally, I am pleased to chance upon a rare bird, or to travel a short distance to a local reserve, knowing one is present. The interest in seeing a new species this way is sometimes tempered by the fact that, if it’s a rare vagrant from Siberia or the Americas, it is likely to be exhausted and near death. At the very least, it will never get home or find a mate.

Twitchers, on the other hand, enjoy an extreme, compulsive type of birding, whereby they will hunt out such rarities, competitively, often travelling great distance, at great cost, and enduring considerable discomfort, to do so. They will often prefer to see one bird of a new species, involving a day or more travelling, over the opportunity to spend time looking at a whole range of other, more common birds (which some of them refer to as “trash birds”). There have been cases of twitchers paying hundreds of pounds to charter a boat or plane to get them to The Scillies or The Shetlands, and one once famously left his own wedding reception and missed the start of his honeymoon, to chase after a rarity.

Unlike some birders, who disdain them, I make no judgements about twitchers, and I know that some are very knowledgeable, and are just as likely as other birders to be involved in voluntary and conservation work.

But I’m not one of them. I trust that that’s now clear.