1 Feb 2007 03:37
Re: [foaf-dev] Adding FOAF support to mod_virgule (Advogato)
Thanks for the suggestions - I've made changes which will (hopefully) correct all the issues pointed out so far. I've added an rdfs:label tag to each project. I'm now wrapping all foaf:Project tags in foaf:currentProject. I've removed the homepage URL from the foaf:knows sections because I'm only able to construct the URL to the known user's Advogato home page, which may or may not be their canonical home page. It can be discovered by visiting the seeAlso FOAF instead. And I've added some self-referential foaf:PersonalProfileDocument taggage to make Tabulator and Disco happy. So here's the sample of the latest output: http://advogato.org/person/StevenRainwater/foaf.rdf Here's a little more detail on the project relation issue: While Advogato doesn't include any information about a temporal relationship between the user and the project (past vs current), it does include other information about the relationship. The website has a pool of projects and a pool of users. A user can associate themselves with a project by means of a relationship such as contributor, helper, documenter, developer, lead-developer, etc. For example, here's the Advogato page for the GIMP project: http://www.advogato.org/proj/GIMP/(Continue reading)
Okay, so based on Benjamin and Richard's feeback, I've done a third rev
of the project code and reduced it to just foaf:currentProject with an
rdf:resource that points to the project's Advogato page.
I'll take a look at the DOAP alternative later on. I'm planning to do
some major updates to the Advogato project code but that's down the road
a few months.
I tried Richard's suggestion for the foaf:knows links (e.g. adding
rdf:about tags using their Advogato profile pages). And I incorporated
Richard's suggested fix for the problem of matching the foaf:knows
records with the assocated FOAF files. I'm guessing this worked because
the Disco browser now shows a list of "knows" results that I can click
on to get to their FOAF records. But - it seems to work but only if I
add the "#me" identifier to the end of the initial FOAF URL I enter -
does that seem correct?
And thanks also to all the other folks who emailed me about minor bugs
in the format.
Here are a couple of example links for today:
RSS Feed