URI, URN and URL. Still confused after RFC 3986

I am still confused about URIs and URLs after reading RFC 3986 1.1.3 (via RAW).

Can http: URIs be used to identify non-digital objects? The W3C clearly thinks so: the namespace for this code is identified by the URI http://www.w3.org/1999/xhtml.

But the same string is the URL for an HTML page.

Quoting RFC 3986:

The term "Uniform Resource Locator" (URL) refers to the subset of URIs that, in addition to identifying a resource, provide a means of locating the resource by describing its primary access mechanism (e.g., its network "location").

My problem: The web page and the namespace are different resources. Something is located on the network, but that something is not the resource identified by the URI. The difference will be more obvious if the URI http://ships.reg.fo/FD/530 identifies a ship. Whatever you access by the link http://ships.reg.fo/FD/530, it will not land some 20 tons of ship on your desk.

Still, I find it very useful that http://www.w3.org/1999/xhtml describes the object identified by http://www.w3.org/1999/xhtml. Otherwise, we'd have to google for pages with DC:subject="http://www.w3.org/1999/xhtml". But the RFC says the resources identified and accessed are the same, it does not allow for accessing the metadata of the identified resource.

How do I express in RDF that the HTML page http://www.w3.org/1999/xhtml has the namespace http://www.w3.org/1999/xhtml as DC:subject?

One possibility might be placing the HTML description at http://www.w3.org/1999/xhtml.html, and make http://www.w3.org/1999/xhtml redirect there. But even a redirect is a resource, and a redirect is certainly not a namespace.

Longest domain name in the world?

Schtzenbruderschaft St. Johannes 1831 e.V. Langenholthausen




Grokker - interesting GUI, but not worth paying for

I have just tested Grokker.com. The user interface looks very interesting. But the clustering data displayed are too bad to really evaluate the GUI. I did a cluster in Eii, Grokker assigned clusters to common words like vi and a, that is equivalent to clustering on the, and and I in English. There were two clusters inside each other, both labelled Vi, none of them contained any links. When clustering on tank, Grokker identified storage, but did not identify any cluster for main battle tanks.

I'd very much like to see the Grokker interface applied to the data of music map, or maybe the late hoppa.com directory.

But the clustering of Grokker is—in its present pre-alpha state—not worth paying for. Clusty.com from Vivisimo is free and better. (Or was when I first wrote this in 2005. Many a good idea have died since then.)

Official URI

The need for officially sanctioned URIs

SPARQL and finding books by painters

My first stab at SPARQL is an attempt to query the semantic web for books written by painters. Actually, I think it is a search for anything created by a painter. But I can't test it, so who knows.

We still need Loran C as a backup

Much as I'd like to get rid of the AM noise from the Loran C at Eii, we do need Loran as a backup for the satellite navigation systems.

Quoting Megapulse:

  • dissimilar failure modes to Satellite Systems
  • difficult to jam due to high power levels

OpenOffice documents may now have one root

According to Committee Draft 2 section 2.1, the OpenOffice format will now support OpenOffice documents in one single XML document.

This is good news.

The present format, with five or more XML files zipped together, is really--like Microsoft Office--only suitable for human editing. The single root XML format will make XSLT based processing possible, combining human editing with automated workflows. One XSLT may extract chapter headers form a text document, another create a spreadsheet from a naked data XML. The sky's the limit. For the first time, OpenOffice has something MS Office has not. And will never get - Microsoft won't ever use an open format for Office.

Update: OpenOffice 2.0 beta supports the OASIS OpenDocument XML format as the default file format.

Trafikkregler i Trshavn

En introduksjon for nykommere

  • Vikeplikt for trafikk fra hyre? Denne lov glder ikke Frerne.
  • Trshavn er planlagt og bygget for fotgjengere. Derfor er det for lite plass til bilene. (Og slett ingen plass til fotgjengere og syklister.)
  • Det er nesten ingen fotgjengerfelt, derfor har fotgjengere samme rettigheter utenfor.
  • Fotgjengere har vikeplikt i fotgjengerfelt.
  • Bruk blinklys nr du svinger. Ikke etter at du har svingt, ikke fr du svinger, men mens du svinger.
  • Husk riktig plassering i kjrebanen: Godt til venstre fr en hyresving, og godt til hyre fr en venstresving.
  • Trafikk i innersving har vikeplikt for trafikk i yttersving. (Det er uhflig tvinge noen til kjre omveier ved presse seg fram i innersving.)
  • Trafikk ut av en blindgate har vikeplikt for trafikk inn i blindgaten.
  • Trafikk i motbakke har vikeplikt for trafikken som kjrer ned bakken, srlig p glatt fre. (Det er jo lettere stoppe nr du kjrer oppover.)
  • Ikke stopp for bllys i speilet. Det er bare en rnebil med bl lykter som kjrer over et sandkorn med lavprofildekk. (Politiet bruker ikke bllys hvis de vil stoppe deg, de bruker lyshornet.)
  • Skulle bllyset likevel vre et utrykningskjrety, skal du i hvert fall ikke stoppe, for store deler av byen har midtrabatter som gjr det umulig kjre forbi.
  • Og utenfor byen: Bruk nr- eller parkeringslys hvis du ligger frst i ken i mrke. S er det ikke ndvendig dimme hvis noen skulle vge seg p kjre forbi. Bedre fre var.

Windblown Tracks

Car tracks outside our house today, the loose snow having been blown away.

Windblown tracks

RSS 0.91