Like I said in my previous entry, I’m looking into the world of FOAF. With the help of some comments by Jim Hughes and Morten Frederiksen and especially by watching and looking closely into other people’s FOAF files, I recontructed my file and expanded it. The FoaF Explorer was very helpful as well as it visualises FOAF files which is very useful for those less technically inclined like me. That and the w3c rdf validation service mercilessly pointed out numerous errors I made.
The FoaF Explorer teached me I was using a deprecated namespace for the nearest airport information and looking at Morten’s file in the Explorer let me figure out how to get those buttons linking to GeoURL and various maps. Some info popped up twice which after some puzzling taught me it matters where exactly you put the information, before or after the list with people you know.
If you want to look at what my FOAF file looks like, here’s the link to my ‘Explored FoaF’, which I added to the sidebar as well. Meanwhile I surf the web, from one interesting FOAF related page to another, being sucked into all kinds of stuff new to me, features, discussions, problems, competitive efforts, XML, the semantic web etc. …
And Daisy? You have a built-in FOAF file because you’re using Typepad, which is made up from your blogroll, as I find out at Marc Canter’s blog. Your blog description has become your one-line bio, your dog is depicted and I’m not on your blogroll
Have a look for yourself
Some other ways of looking at FOAF files are FOAF: Web View where mine looks like this and here is how it looks like in rdfweb. The first teaches me people I know I listed by their nicknames only, are listed with a ‘ – [blank space] ‘ and the second doesn’t show them at all.































Hell fire and spitoons. I have absolutely no idea what this is all about but I promise to make time to read about it at the weekend.