{"id":84,"date":"2010-01-31T20:58:38","date_gmt":"2010-01-31T20:58:38","guid":{"rendered":"https:\/\/rwec.co.uk\/blog\/?p=84"},"modified":"2010-01-31T20:59:10","modified_gmt":"2010-01-31T20:59:10","slug":"a-blog-entry-is-not-a-database","status":"publish","type":"post","link":"https:\/\/rwec.co.uk\/blog\/2010\/01\/a-blog-entry-is-not-a-database\/","title":{"rendered":"The Non-Semantic Web: A blog entry is not a database"},"content":{"rendered":"

There has long been a hope – an expectation<\/em>, even – that the Web will somehow develop into something “smart”; that it will move from being a mere store-house of information to something that will actually “know the answers”.<\/p>\n

But the vision tends to overlook the nature of both computers and humans. On the one hand, humans have a limited memory, and a flawed ability to apply consistent logic; on the other hand, we have abilities at creatively interpreting knowledge and ideas that are far beyond the capacity of any computer so far designed.<\/p>\n

<\/p>\n

Big Calculators<\/h2>\n

Artificial Intelligence is a fascinating area of research – it’s what I studied at University – but it is one that has had something of a reality check over the years. At first, it seemed like only a matter of time before computers of some sort or another would exceed all human abilities, ushering in a technological utopia – or perhaps an apocalypse. But it turns out there are things computers are really good at<\/em> and things they’re really bad at<\/em>.<\/p>\n

The classic example is chess computers: when researchers started building them, the reasoning was that since it takes an intelligent human to play chess, a computer that could play chess would be intelligent too. Eventually, they built a computer that could consistently beat the best human chess players; unfortunately, they discovered that that’s all<\/em> they’d built – they hadn’t broken through to a new level of computing, they’d just broken down chess into a very long list of sums. And computers are good at sums<\/strong>.<\/p>\n

Another example is neural networks – the wonderfully futuristic sounding “Multi-Layer Perceptron” is a learning system based on simplified mathematical models of neurons, the building blocks of the human brain. You can “teach” such a network to recognise things, and it starts seeming very clever. But researchers realised that you don’t really need the clever model at all, because it’s all just maths – and indeed you can make a so-called “N-tuple Neural Network” that consists entirely of lookup tables, with no real maths involved, and certainly no “brain”. And while there are now very handy machines that can recognise faces, it’s still no use trying to have a conversation with one<\/strong>.<\/p>\n

Whose Markup is it Anyway?<\/h2>\n

The “Semantic Web”, at the moment, is like that early AI research – it all seems just around the corner, if only we all try a little bit harder. In fact, the Web has already come a long way, and while the basic language of HTML remains the same, its usage has changed dramatically over the years.<\/p>\n

At first, HyperText Markup Language<\/em> was a very simple way of “marking up” documents in the big text repository that was the World Wide Web – separating out paragraphs, marking headlines and important bits, and, of course, turning text into “anchors” which “hyperlinked” documents together. As it grew, the Web demanded more, prettier, pages, and HTML grew into a rich, presentational<\/em> language – with colours, tables, images, even simple animations. Then, the needs to automate complex and interactive systems meant HTML had to become a structural<\/em> language as well – one that could identify blocks of a page, take them apart, and join them back together in a different order.<\/p>\n

At this stage, a question arises, which is just how much structure does a document need?<\/strong> Two technologies readily associated with structural<\/em> HTML are XHTML – HTML with the added rigidity and tools of XML – and the DOM<\/abbr> – a way of look at a document as a big tree of “nodes”. This is an extremely useful way of looking at a page with lots going on – you can work dynamically with the navigation controls, or the interactive comment system, without touching the main content area. But how useful is it inside<\/em> the content? In the sentence “I really<\/em> like structure”, the word “really” is wrapped in its own HTML element, but not because of any structural significance<\/em> – it’s just there for presentation.<\/p>\n

Now, we’re told, HTML needs to evolve further, into a semantic<\/em> markup, which doesn’t just separate out the blocks, it labels them all meaningfully<\/em>. I’ve used italics as an example deliberately, because a common misconception is that the <i> tag is bad – it’s presentational<\/em> – and <em> is better – it means emphasise this<\/em>, rather than draw this in italics<\/em>: much more semantic<\/em>, surely? And so the Rich-Text control I’m typing in right now has a button labelled “I” – the recognised icon for italics – which inserts an <em> tag; it even replaces <i> with <em> if you edit the HTML! This is, obviously, a complete misunderstanding – a straight find-and-replace can’t magically gain us meaning<\/strong> – but the fact is, it’s what people<\/em> are used to, and it’s people<\/em> that write the content.<\/p>\n

So this is the second conflict facing the Web – authors don’t want to add all this information. The real reason <i> is discouraged is that when it’s not<\/em> being used for emphasis, the machine has no way of knowing why it is<\/em> being used: it might be to indicate a foreign phrase, like in situ<\/em>, in which case we could indicate what language it is; or it might be the name of a publication, like The Times<\/em>, in which case we could label it with some appropriate global identifier. But the fact is, a human reader won’t gain anything from this, and content is written by humans, for humans<\/strong>.<\/p>\n

Playing to our Strengths<\/h2>\n

In the end, the Semantic Web will not be built by insisting that I tell WordPress that in situ<\/em> is Latin – who would it help if I did? A blog entry is not, and never will be, a database – it’s a big block of text, or perhaps a few medium-sized blocks of text, with some decoration and links thrown in. The structural<\/em> markup can help us divide up those blocks, and mark off the bits of the page which aren’t part of the blog entry at all; the semantic <\/em>markup will improve how those blocks <\/em>get labelled.<\/p>\n

If you want to find pages about a particular topic, what you need is a really big index, and that’s a good job to give a computer; if you want to find “the right page” about a particular topic, it’s up to you to decide what “right” means. We can help the computers to help us – by making articles that explicitly label their own topics, for instance (as long as you can trust them, but that’s another issue). We can even decide that sometimes we do want to embed little bits of data<\/em> in our content<\/em> – if we know an address might be useful to someone, we could label it with an appropriate microformat<\/a>, so they can more easily feed it to another piece of software. But if they want to look up what in situ<\/em><\/a> or Perceptron<\/a> actually means, we can leave it to a human to look it up in an appropriate index.<\/p>\n

This may be a disappointing prognosis if you were hoping the web could tell you the answers without you having to read the articles, but think of it as a division of labour: the computers can get better at categorising <\/em>and filtering <\/em>the content, we can carry on being good at understanding <\/em>it.<\/p>\n","protected":false},"excerpt":{"rendered":"

There has long been a hope – an expectation, even – that the Web will somehow develop into something “smart”; that it will move from being a mere store-house of information to something that will actually “know the answers”. But the vision tends to overlook the nature of both computers and humans. On the one […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[58,59,61,60,62,56,55,57],"class_list":["post-84","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-ai","tag-artificial-intelligence","tag-html","tag-language","tag-markup","tag-semantic","tag-semantic-web","tag-web","post-preview"],"_links":{"self":[{"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/posts\/84","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=84"}],"version-history":[{"count":6,"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/posts\/84\/revisions"}],"predecessor-version":[{"id":90,"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/posts\/84\/revisions\/90"}],"wp:attachment":[{"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=84"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=84"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rwec.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=84"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}