14 February 2007

MyBlogLog

Just found out about MyBlogLog. Found it on the site of Clicky. Somehow they can show a list of who else is visiting my blog. Mmmm. Let' s check it out. I'll let you know if I think it's fit for my blog.

Clicky

Just found a new Web Statistics tool: Clicky. Clicky not just gathers usage statistics, but also collects information about which individuals visit your blog, or at least their IP-addresses. I've added their Javascript Tracking code to the Stats-box to the right, and it works just fine.

11 February 2007

BlogPulse (2)

It costed some time, but it seems that step-by-step BlogPulse is recognizing my blogs. Just click the title of this posting.

7 February 2007

What is this GeoURL about?

To the left of this page, in the Varia box, one finds one more little icon or label:

GeoURL


What is this about?

GeoURL is a location service, which locates your website in Meatspace and associates sites near your site to it. Look eg at sites near my blog: http://geourl.org/near?p=http://ableijs.blogspot.com/.

How does it do that? Well just by looking at your metadata.
There are several ways to this. GeoURL uses 2 of them:

1. ICBM (Why ICBM? Old Usenet historical precedent.)
Add the following metatags to the -section of your XHTML-page:

<meta name="DC.title" content="THE NAME OF YOUR SITE" />
<meta name="ICBM" content="XXX.XXXXX, YYY.YYYYY" />

where XXX.XXXXX is the latitude (south is negative), YYY.YYYYY is the longitude (west of Greenwhich, UK is negative).

Also notice the use of Dublin Core to denote the title of the blog. See: Expressing Qualified Dublin Core in HTML/XHTML meta and link elements. This should be preceded by using the profile attribute in the <head>-tag:

<head profile='http://dublincore.org/documents/dcq-html/'>

denoting the use of Dublin Core Metadata, and by the line:

<link href='http://purl.org/dc/elements/1.1/' rel='schema.DC'/>

denoting the meaning of the prefix 'DC'.

2. Using GeoTags.
Add the following metatags to the <head>-section of your XHTML-page:

<meta name="DC.title" content="THE NAME OF YOUR SITE" />
<meta name="geo.position" content="XXX.XXXXX, YYY.YYYYY />
<meta name="geo.placename" content="Place Name, Country-or-State"/>
<meta name="geo.region" content="ISO 3166 Country code or ISO 3166-2 Country Subdivision code"/>

where again XXX.XXXXX is the latitude (south is negative), YYY.YYYYY is the longitude (west of Greenwhich, UK is negative).
The ISO 3166 Country code for the Netherlands = "NL", while the ISO 3166-2 Country Subdivision code for the Utrecht province is NL-UT.
Some other services, notably Syndic8, use geo.country instead:

<meta name="DC.title" content="THE NAME OF YOUR SITE" />
<meta name="geo.position" content="XXX.XXXXX, YYY.YYYYY />
<meta name="geo.placename" content="Place Name, Country-or-State"/>
<meta name="geo.country" content="ISO 3166 Country code"/>

Once again you need to tell what this 'geo.'-thing means.
This should be done by by using the profile attribute in the <head>-tag:

<head profile='http://dublincore.org/documents/dcq-html/'>

denoting the use of Dublin Core Metadata and alike profiles, and by the lines:

<link href='http://purl.org/dc/elements/1.1/' rel='schema.DC'/>
<link href='http://geotags.com/geo/' rel='schema.geo'/>

denoting the meaning of the prefixes 'DC' and 'geo'.

3. Syndic8 uses yet another method, not supported by GeoURL: The Getty Thesaurus of Names (TGN).

<meta name="tgn.id" content="id from the TGN database" />
<meta name="tgn.name" content="Place Name, Country-or-State" />

Also here you should tell what this 'tgn.'-thing means.
This should be done by by using the profile attribute in the <head>-tag:

<head profile='http://dublincore.org/documents/dcq-html/'>

denoting the use of Dublin Core Metadata and alike profiles, and by the lines:

<link href='http://purl.org/dc/elements/1.1/' rel='schema.DC'/>
<link href='http://www.getty.edu/research/conducting_research/vocabularies/tgn/' rel='schema.tgn'/>

4. Making full use of Dublin Core: Expressing Qualified Dublin Core in HTML/XHTML meta and link elements.

Start with the profile attribute of the <head>-element:

<head profile='http://dublincore.org/documents/dcq-html/'>

denoting the use of Dublin Core Metadata and alike profiles, and with the lines:

<link href='http://purl.org/dc/elements/1.1/' rel='schema.DC'/>
<link href='http://purl.org/dc/terms/' rel='schema.DCTERMS'/>

denoting the meaning of the prefixes 'DC' and 'DCTERMS'.

Then add the Dublin Core Metadata:

<meta name="DC.title" lang="en" content="THE NAME OF YOUR SITE" />
<meta name="DC.creator" content="YOUR NAME" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.ISO3166" content="ISO 3166 Country code" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.TGN" content="id from the TGN database" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.Point" content="east=YYY.YYYYY; north=XXX.XXXXX; name=Place Name" />

where again XXX.XXXXX is the latitude (south is negative), YYY.YYYYY is the longitude (west of Greenwhich, UK is negative).
Syndic8 expects you to be more descriptive about the creator, following an obsolete version of the Dublin Core:

<meta name="DC.creator.e-mail" content="YOURNAME@yourdomain.com" />
<meta name="DC.creator.name" content="YOURNAME" />


5. You can put these al together:
Start with the profile attribute of the <head>-element:

<head profile='http://dublincore.org/documents/dcq-html/'>

denoting the use of Dublin Core Metadata and alike profiles, and with the lines:

<link href='http://purl.org/dc/elements/1.1/' rel='schema.DC'/>
<link href='http://purl.org/dc/terms/' rel='schema.DCTERMS'/>
<link href='http://www.getty.edu/research/conducting_research/vocabularies/tgn/' rel='schema.tgn'/>
<link href='http://geotags.com/geo/' rel='schema.geo'/>
<link href='http://dmoz.org/rdf' rel='schema.dmoz'/>

denoting the meaning of the prefixes 'DC', 'DCTERMS', 'dmoz', 'geo' and 'tgn'.

Then add all the Metadata:

<meta name="DC.title" lang="en" content="THE NAME OF YOUR SITE" />
<meta name="DC.creator" content="YOUR NAME" />
<meta name="DC.creator.e-mail" content="YOURNAME@yourdomain.com" />
<meta name="DC.creator.name" content="YOURNAME" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.ISO3166" content="ISO 3166 Country code" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.TGN" content="id from the TGN database" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.Point" content="east=YYY.YYYYY; north=XXX.XXXXX; name=Place Name" />
<meta name="tgn.id" content="id from the TGN database" />
<meta name="tgn.name" content="Place Name, Country-or-State" />
<meta name="geo.position" content="XXX.XXXXX, YYY.YYYYY />
<meta name="geo.placename" content="Place Name, Country-or-State"/>
<meta name="geo.country" content="ISO 3166 Country code"/>
<meta name="geo.region" content="ISO 3166 Country code or ISO 3166-2 Country Subdivision code"/>
<meta name="ICBM" content="XXX.XXXXX, YYY.YYYYY" />
<meta content='Top/OPEN DIRECTORY CATEGORY' name='dmoz.id'/>

Note that I added also the Open Directory category, to keep Syndic8 happy.

In this way almost every location service can understand where you are located in Meatspace.

So how can I use this with Blogger?

  1. Login.
  2. Choose Customise (from the top bar) or choose Layout from your Dashboard.
  3. Choose Edit HTML.
  4. Edit the template as follows:
<head profile='http://dublincore.org/documents/dcq-html/'>
<b:include data='blog' name='all-head-content'/>
<title><data:blog.pageTitle/></title>
<link href='http://purl.org/dc/elements/1.1/' rel='schema.DC'/>
<link href='http://purl.org/dc/terms/' rel='schema.DCTERMS'/>
<link href='http://www.getty.edu/research/conducting_research/vocabularies/tgn/' rel='schema.tgn'/>
<link href='http://geotags.com/geo/' rel='schema.geo'/>
<link href='http://dmoz.org/rdf' rel='schema.dmoz'/>
<meta name="DC.title" lang="en" content="THE NAME OF YOUR SITE" />
<meta name="DC.creator" content="YOUR NAME" />
<meta name="DC.creator.e-mail" content="YOURNAME@yourdomain.com" />
<meta name="DC.creator.name" content="YOURNAME" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.ISO3166" content="ISO 3166 Country code" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.TGN" content="id from the TGN database" />
<meta name="DCTERMS.spatial" scheme="DCTERMS.Point" content="east=YYY.YYYYY; north=XXX.XXXXX; name=Place Name" />
<meta name="tgn.id" content="id from the TGN database" />
<meta name="tgn.name" content="Place Name, Country-or-State" />
<meta name="geo.position" content="XXX.XXXXX, YYY.YYYYY />
<meta name="geo.placename" content="Place Name, Country-or-State"/>
<meta name="geo.country" content="ISO 3166 Country code"/>
<meta name="geo.region" content="ISO 3166 Country code or ISO 3166-2 Country Subdivision code"/>
<meta name="ICBM" content="XXX.XXXXX, YYY.YYYYY" />
<meta content='Top/OPEN DIRECTORY CATEGORY' name='dmoz.id'/>

Note that you have to alter the <head>-tag, have to keep the <b:include>- and <title>-lines, and have to add the <link rel="schema.*">- and <meta>-lines.

I've done this with my template, and added http://ableijs.blogspot.com/ to the GeoURL-database (http://geourl.org/add.html). So now everyone can look up my place in GeoURL (http://geourl.org/near/?p=http://ableijs.blogspot.com/), as well as lookup sites mear me in Meatspace. People also can lookup my town in Multimap or Mapquest.

5 February 2007

What about those RDF, RSS and Atom icons?

To the left of this page, in the Varia box, one finds three little icons or labels:

RSS 1.0
Atom 1.0
RSS 2.0


What are these for?

In fact they are links to a XML version of this blog. With this version it is possible that not only other persons, but also other programs can read this blog. Just like the links to the first 5 hid lines of my Live Space you find to the right. There are standards how to do that, not one, but a number.

My favourite is RDF/RSS 1.0. This one is based on the Resource Description Framework, which is a W3C Recommendation (http://www.w3.org/RDF/). This RDF is part of the W3C Semantic Web Activity, which tries to turn the world wide web into a web of data, which has meaning not only to humans, but also to machines. RDF is a generic framework, within which vocabularies can be for different goals. RSS 1.0 is such a vocabulary for Site Summaries (RDF Site Summary). del.icio.us uses RDF, and so does the Open Directory Project.

RSS 2.0 is not a successor, but a derivation or a fork, which is popular mainly (but not only) at Microsoft. RSS 2.0 does not obey the rules of the semantic web. More information: http://en.wikipedia.org/wiki/RSS_(file_format).

Atom is an attempt to leave al this confusion behind. It is an Internet Proposed Standard (RFC 4287), but unfortunately no longer part of the semantic web efforts. Atom is the favourite of Google, which bases its GData-protocol on it.

Link to dutch version of this posting: http://ableijs.spaces.live.com/blog/cns!A5676E446DB7316!152.entry