Skip to main content
Table of contents

Publishing

How the world taxonomy works

GOV.UK aims to organise content with a single taxonomy, the topic taxonomy, however due to legacy reasons there is a disassociated branch of this taxonomy known as the world taxonomy. The world taxonomy is used to tag guidance to particular world locations, for example Latvia: doctors is content tagged to the Living in Latvia section of the world taxonomy. The full list of world location pages can be seen on https://www.gov.uk/world.

For each world location in the world taxonomy there are a number of consistent child entities such as Passports, Trade and Invest, Coming to the UK, etc. This varies for some place, for example Syria. There are also generic versions of the world location child pages that aren’t tailored to a specific location, for example Passports and Trade and Invest.

You can view the hierarchy of the world taxonomy in content-tagger (requires access to content tagger on integration).

Differences between topic taxonomy and world taxonomy

Whilst world taxons are treated in the same way as the topic taxonomy on a data level, they are a separate entity and do not share the same root. All taxons within the topic taxonomy are either level one taxons (which are represented in the Content API of the GOV.UK homepage) or descendants of those. World taxons however are outside of this structure and are descendants of the /world/all content item.

The two taxonomies have different shapes. The topic taxonomy has 21 top level items and these can increase in specificity for up to 5 levels (for example: Education, training and skills > School and academy funding > Initial Teacher Training funding > Subject Knowledge Enhancement (SKE) funding). The world taxonomy has over 200 top level items and these only have a maximum one additional level of specificity (for example: UK help and services in Afghanistan > Passports and emergency travel documents)

GOV.UK has approximately 4000 published taxons, of those nearly 2500 are world taxons meaning that they represent a substantial majority of all taxons.

Unlike the topic taxonomy only content associated with specific organisations is allowed to be tagged to world taxons and only particular document types may be tagged to them. This is because the world pages are intended to be curation mechanisms for the Foreign Commonwealth Office and organisations that have similar concerns, rather than content tagged to a topic.

World taxons are rendered differently on the frontend to topic taxons. Compare https://www.gov.uk/education/running-and-managing-a-school with https://www.gov.uk/world/yemen.

Problems with world taxonomy

The world taxonomy is not a well known part of GOV.UK and has a number of quirks that can make it problematic for developers working on GOV.UK. These quirks can produce a number of hard to diagnose problems.

Any application that either tags content to taxons or pulls taxons out of the Publishing API has to consider them. Tagging to taxons requires an application to consider whether they will be accidentally overwriting any tagging to the world taxonomy. Pulling taxons from the Publishing API requires determining whether each item is part of the topic taxonomy or the world taxonomy.

The rules regarding which departments and document types world taxons apply to are only enforced by Whitehall, not by content-tagger, meaning that these rules are not applied uniformly.

There is a world location format that was the predecessor to the world taxon pages. This is still used for a number of things (atom feed, tagging in Whitehall, rendering the world page) therefore we have two similar coupled concepts that are needed to be kept in sync.

Content associated with a world location is tagged to the previous concept of a world location rather than a world taxon. For example Information and events for UK nationals living in Portugal has no links to Portugal and instead is linked to the now defunct Portugal world location. The consequence of this is that web links need to be created based on the old world location concepts title (which is a fragile process that needs manual overrides when it breaks) and that these content relationships cannot be mapped in data-science tooling without understanding this quirk.

World taxons are treated the same as topic taxons in content tagger, the only clue a user has that they are dealing with something different is the /world part of their path.

The structure of the world taxonomy is dense and repetitive. This results in a poor user experience for anyone tagging to it via Whitehall for example.

The /world page is unconventional for GOV.UK as it is not represented by a content item and it is instead only represented in router while being rendered by Whitehall. There is a content item at /world/all which redirects to /world, however the data from this content item is not used to render /world.

History

The world taxonomy is a product of the work done by the Worldwide Publishing team in Q1 2017. The work brought consistent information structure to the 229 countries represented on the world pages.

This project occurred around 2 years after work had begun on the GOV.UK taxonomy which was under active development at the time. It’s unclear whether the intention was for this to be a part of the single taxonomy or always intended to be separate.

Future

The future for the world taxonomy is unclear. It is considered an undesirable part of the GOV.UK stack due to its close coupling to the topic taxonomy yet with an information structure that does not lend itself to classification, thus not really a taxonomy. However there is not a drive towards separating it or clear decisions on what should replace it, which therefore means it may remain a part of GOV.UK for the foreseeable future.

Editing the world taxonomy

Taxons within the world taxonomy can be edited via the same means as editing topic taxons.

This page was last reviewed on 5 February 2020. It needs to be reviewed again on 5 August 2020 by the page owner #govuk-developers .
This page was set to be reviewed before 5 August 2020 by the page owner #govuk-developers. This might mean the content is out of date.