Norsk EU-medlemskap er sikkert som amen i kjerka

Norsk EU-medlemskap er sikkert som amen i kjerka, mener NHO.

Det er jeg enig i. Norge er i dag tettere integrert i EU, enn det EEC-medlemskapet som ble stemt ned i 1972.

Det er ingen heksekunst å spå om fortiden.

Representing taxonomies in OWL

I have a hard time representing a taxonomy in OWL.

The syntax is XML, but the structure is relational database.

eið is online

eið is now online with a link collection for the village Eiði in the Faroe Islands.

With a properly coded link, eið, it will even work in Internet Explorer. (See IBM for encoding.)

There is also an attempt at representing the same information for the semantic web (i.e. machine readable) at eiði.rdf. Where someone using a semantic search engine should be able to find e.g. two books that are written by painters. Which would be considerably more powerful then what Google can offer now, near the end of 2004.

The Japanese Patriotism Act

The deputy principal walked down the aisle between the wall and the teachers' seats and approached me and said, Please stand up and sing, said Mitsuo Kondo, 61, a martial arts teacher [...] So I said: I won't stand up. I won't sing.

Mr. Kondo, whose teaching contract was canceled as a result and who now is a part-time carpenter, said he had not opposed the anthem and flag until showing respect was required. He said he used to sing the anthem at the top of his voice.

(from New York Times)

The X in XHTML

The X in XHTML means Extensible. And in the browsers, it really is. If I add an element of my own, maybe mine:something, an HTML browser will ignore the mine:something tags, and display the mine:something content, if any.

But if I try to validate such a page, I get a problem, because it is invalid. Which is a real problem, because my blog will force validity on my entries.

What I need, is a DOCTYPE that accepts HTML as valid under the following two conditions:

  1. The page is wellformed XML
  2. The page would be valid XHTML if all tags from other namespaces were removed

Note that testing removal of elements from other namespaces would be too liberal, test by removing foreign tags with their content left in place.

Work by W3C is addressing ways to specify conformance for documents involving multiple namespaces. But they seem concerned with specific extensions like MathML, I want a DOCTYPE to handle general extensions.

I want my validator to say: The way you use your extensions may be bullshit, but at least it is wellformed bullshit placed in a valid XHTML context.

An example of the problem, is the G O Sars page. It contains a pair of geo:lat and geo:long elements, but to make the page valid, I had to place them in CDATA. That transforms them from elements to text. Fortunately, they are still treated as geo: elements by Blogmapper

Peppernøtter for voksne


Internet Explorer is the fastest for huge XML

IE6 is very much faster than FireFox or Mozilla, when it comes to locating words in huge XML files like

I didn't test Opera, because Opera doesn't display unstyled XML very well.

(IE is still a slow loader, though.)

Don't try this at home: Install this CA certificate

The Faroese Telecom is asking cusomers to Install this CA certificate.

This is a very dangerous habit to get your customers into. Even if they do trust this company, the certificate is downloaded unsigned, and may thus have been corrupted on its way.

Please! Føroya Tele can surely afford to buy a certificate that is authorized by one of the CAs that are built into the browsers with Verisign as one of the obvious choices.

Update is no more asking me to install a new (and unsigned) root authority. I am only asked if I am willing to accept an expired certificate for this session. Which I am, I wouldn't mind browsing my telephone bill on unencrypted http. But I do mind sites that get its customers into the habit of accepting expired certificates signed by unknown authorities. This page really is from, because I say so myself!.

certificate has expired

Make Love, not Spam

I really do feel like executing a spammer.

But spam should not be fought by counterattack, that will cause mostly collateral damage. Is a dDoS attack on really a good idea?

Spam should be stopped with sender verification, by requiring costly CPU cycles to send an email, and -- as a last resort -- content filtering.

RSS 0.91