Possible Issues

From FOAF

Jump to: navigation, search

Possible Issues can be a holding pan for issues raised on IRC, mailing lists and in Other Communities that may need resolution.

[edit] foaf:publications

egonw asked in #foaf about the use of foaf:publications. It is not clear exactly how foaf:publications is intended to be used. It lists having a range of foaf:Document, which means that one would expect having to write something like this: :me a foaf:Person; foaf:publications _:smith1997. _:smith1997 a foaf:Document. but this replicates the functionality of foaf:made/foaf:maker. This is probably not it.

Common usage would suggest that it's used by academics and other professional thinky-writey people to point to a list in HTML form of published papers and books. Examples of this are DanC and yvesr. This use is consistent with other properties in the FOAF specification - for instance foaf:workplaceHomepage and foaf:schoolHomepage which most often point to an HTML document. Clearer guidance as to how this is to be used would be useful.

Here is an example of the syntax that egonw is wanting to use.

[edit] FOAF Rapid Response Squad

An idea I had was to help social networks and other social software and services should have a simple e-mail point-of-contact for help implementing FOAF. Anyone want to implement this? Perhaps we need a broader SemWeb Rapid Response Squad for people implementing FOAF/SIOC and other formats. Thoughts?