Category Archives: WordPress

http://wordpress.org/ WordPress: Semantic personal publishing platform

Uncle Squared

FOAF, General, WordPress

Things haven’t been less hectic since my last progress report — I’m now officially entitled to the title “Uncle”, as my sister yesterday finally gave birth to Silke, her lovely daughter and my wonderful niece:

Silke, Gry og Hans

To top it off, (Aunt) Katrine’s brother and his wife came home from China tonight, bringing with them their new daughter Isabel, just as lovely and wonderful:

Isabel

In other news, Katrine and I entered the bubbly housing market — we bought a house on Lellinge Allé, just outside central Copenhagen. We will be moving after October 1st, after which you’ll all be more than welcome to stop by! :-)

Elsewhere, Katrina is in the news and photo streams, and Tim Bray’s retrospect about Nawlins reminded me of when I was there, specifically of when I was walking down Basin Street and got “hustled” by a guy who claimed to be able to tell “where I got my shoes” for $10. Since I brought them from Denmark, I figured I’d be safe accepting the challenge, but he simply replied “On your feet”. Laughing hard, I just had to fork it over.

ObSemWeb: Prompted by Danny Ayers, I finally got around to releasing a new version of the FOAF Output plugin. It’s now at 1.17, with a few fixes and tweaks added since the last release (but still not tested with WP 1.5 and later).

WordPress Plugin: Weighted Interests

Release, WordPress

I recently ran into Matt Kingstons’s Weighted Categories plugin. It was inspired by flickr’s tag list, showing tag usage with a font size for each tag proportional to the number of photos tagged.

I decided to clean it up a bit and make it work on pages that didn’t include all posts, and then turned it into an example of how to extend the FOAF Output Plugin profile page (example, download, source).

The current version is 1.1 (released 2005-01-02).

Changes since 1.0:
  • Fixed problems when no interests were found.

This plugin requires the FOAF Output Plugin. Note that only categories that are classified as interests by the FOAF Output Plugin (that is, the ones that have a URI in their description) are included in the list. If you wish to show all categories, simply change the line that gets the list of interests:

$cats=get_foaf_output_interests(falsetrue);

In case you are interested, here’s the CSS I added to my global stylesheet to make it look like it does:

.profile dl dd.weighted-interests { 
  text-align: center; 
  padding: 0.5em; }
.profile dd.weighted-interests li { 
  list-style: none; 
  display: inline; 
  margin: 0.2em; }
.profile dd.weighted-interests a { 
  text-decoration: none; }

SKOS Output from WordPress

FOAF, RDF, Travelling, WordPress

Waiting for the bus to the medieval banquet at Dunguaire Castle for the FOAF Galway Workshop (photos), I remembered I had tweaked the FOAF Output Plugin to also output SKOS concepts — and possibly mappings to others’ categories.

Get it before your neighbour, the FOAF Output Plugin, version 1.11 — the Galway Release…

See also the SKOS development toolshed.

In passing, being here in Galway/Ireland is great, not only do I get to meet a lot of smart and interesting people, very much like at FOAF Camp, I also get to add another country to my list of visits…

WordPress Plugin: seeAlso’s

FOAF, RDF, Release, WordPress

What is now several weeks ago, Christoph Görn hacked a bit on my FOAF Output plugin, and asked for seeAlso links to be included. Short of the mythical WordPress triple store (factory?) I couldn’t see a better way to do it than building on the concept from the Semantic Visits add-on: Using the link manager.

I challenged Danny Ayers to write the plugin/add-on, but he’s been busy lately, with the RSS book and all, so here it is, the seeAlso’s Plugin (view source). While I was at it, I also fixed a few buglets in the FOAF Output Plugin and added trust ratings for friends and bio:olb.

The current version is 1.0 (this blog entry will serve as a changelog).

Continue reading WordPress Plugin: seeAlso’s →

Visit Revisited

OWL, Vocabularies, WordPress

A few days ago, Norman Walsh was kind enough to let me know that there was something wrong with the way I had put together the visit vocabulary.

It turned out that I had mixed together some URIs while surfing around the DAML vocabularies, and the URIs I used to identify each of the states were wrong — the right ontology is http://www.daml.ri.cmu.edu/ont/USRegionState.daml.

The visit vocabulary has been updated to reflect this, and the WordPress plugin Semantic Visits has been fixed, you should upgrade if at all possible.

In addition to the fixes, it has been clarified that the right ISO 3166 country code for the United Kingdom is “GB”. This warranted a fix (or more precisely an addition) in the image generation code at MyWorld66, and Douwe Osinga was quick to respond — it now accepts “GB” as well as “UK” (for backwards compatibility reasons only, use “GB” from now on), thanks!

While I was twiddling, I added support for Canadian provinces — also supported by MyWorld66’s Visited Canadian Provinces and a DAML ontology for Canadian States and Teritories, for those that have had the privilege of visiting those parts of the world.

This last part turned out to be a little harder than expected, as the Canadian regions are divided into states and territories, and that required some investigations into OWL — I think I got it right, but if not you’ll likely see yet another correction soon…

Also, it turned out that there was an issue with the terms used to indicate the code, name, and other state properties — the terms are defined in the general DAML State Ontology as e.g. http://www.daml.ri.cmu.edu/ont/State.daml#code, but in the DAML US Region and State Ontology and the DAML ontology for Canadian States and Teritories they are used as e.g. http://www.daml.ri.cmu.edu/ont/CanadianState.daml#code.

I’m still not sure whether the error is because of a typo with regards to the default namespace declaration, or if it’s a misunderstanding of the semantics of owl:imports (actually daml:imports). In any case, I have decided not to propagate the error, so the WordPress Plugin and the vocabulary documentation uses the properties that are defined — but not used until now.