FOAF spec diagram


experimental foafspec diagram
Originally uploaded by danbri

I’ve been trying to capture the core terms of FOAF in a diagram. Here’s version two.

Notes: there are a few terms I’ve missed out, to avoid massive clutter: workInfoHomepage, geekcode, myersBriggs, currentProject, pastProject, dnaChecksum, membershipClass, sha1, fundedBy, theme, Online*XyzAccount, logo, phone. These are all underspecified, underused, or boring. Or all three :) The properties mbox and tipjar are the main quirks; they’re drawn like string-valued properties but are really relations. Some of the non-FOAF namespaces are done the same way too. Maybe it needs a footnote or notation for those?

I’ve included a few nods towards external namespaces; obviously these aren’t supposed to be complete.

Even this kind of diagram is a bit meta; there should be a companion diagram with instance level data using these terms. Work in progress. Suggestions and feedback would be much appreciated.

2 Responses to FOAF spec diagram

  1. ivan says:

    These things are always hugely helpful… so kudos for starting this…

    I was puzzled by the big ‘Thing’ blob there. I looked up in the latest foaf spec to see whether there is something new there, but then I realized that you meant owl:Thing… I think everything that is _not_ foaf should be very clearly shown. Which is the case, usually, because you add a namespace stuff for others, so this may be an exception. Maybe separating the foaf blobs from the others via a background colour would even be better.

    The ‘Thing’ is, actually, a bit disturbing there, because it is not clear to the casual user that, say, an Agent is a Thing, ie, it could be used as an object for, say, primaryTopic. (I must admit I do not know how to capture that either, but it is always easier to critisize:-)

    Adding those extras like sioc might be good but increases the clutter. I am not sure it helps here. If this was in SVG, I would say you should make that part clickable on/off, but that might be complicated for other formats… Maybe you should have two figures, one strictly on FOAF (well, the dc properties are useful, though) and the other with some ‘guests’.

    I understand to leave out a bunch of properties to avoid clutter… But listing all the chat ID-s seems to be unnecessary, too. Having 1-2 makes it clear that it is where those would be used…

    I hope this helps at least a little bit…

  2. [...] revision, after feedback from [...]

Leave a Reply