Email and chat accounts should be displayed under Contacts

[pafcu]

Email (foaf:mbox) and chat (foaf:OnlineChatAccount) are common ways to contact people and should be listed along other contact information in generated HTML.

[haschek]

I agree, and for foaf:mbox and Foaf chatid properties (like
foaf:jabberID) it should not be a problem to output this contact
information. foaf:OnlineChatAccount is harder to understand, because
Foafpress itself doesn't know anything about the 1000 chat systems in
the world, e.g. it cannot know that

<foaf:Person>
  <foaf:name>Max Mustermann</foaf:name>
  <foaf:account>
    <foaf:OnlineAccount>
      <rdf:type rdf:resource="http://xmlns.com/foaf/0.1/OnlineChatAccount"/>
      <foaf:accountServiceHomepage
               rdf:resource="http://jabber.example.com/"/>
      <foaf:accountName>mustermax</foaf:accountName>
    </foaf:OnlineAccount>
  </foaf:account>
</foaf:Person>

must be interpreted as a jabber account mustermax@jabber.example.com.

Please provide some examples and suggestions how to process them.
Maybe we could add some events, that someone can add plugins for
special cases.

[pafcu]

foafpress does not necessarily need to know the actual protocol, just that it is some type of chat account. Maybe e.g. an rdfs:label can then be used to give a human readable protocol name? In some cases it should also be possible to give the account name as e.g. xmpp:username@server (c.f. mailto:username@server) which will even result in nicely clickable hyperlinks. Again, foafpress itself doesn't have to know which protocol is actually used (except to pick an appropriate icon). Anyway, there are not THAT many different popular chat protocols and I think that at least supporting some would be better than to support none.

[haschek]

I guess you are using that kind of statements. Can you please send me
your Foaf URI that I can use your Foaf as real life example when I add
this feature later.