Review of the Contacts documentation about qabel.github.io HOT 5 CLOSED

I read through the chapter http://github.com/Qabel/intern-doc/wiki/Qabel-Client-Contact-Drop-Messages again and thought about the fields defined there.
If we just want to store the information needed for the communication between the Qabel clients then the field "module_data" should not be there. This could/should be stored in the person modules data. That would make more sense anyway as the persons the actual user wants to communicate with are only identifiable for him by their names/mail addresses/... (person information) and not by the technical information (contact).

Example of a Chat module:

a.) If it would be defined like it is right now:

The chat module asks the contact module for the list of all contacts. Then it has to ask the contact module for every contact the person associated with it in order to get the names/nicknames/.....

b.) If it would be defined like I described it:

The chat module asks the person module for the list of all persons. Then it can show a list of names/nicknames/... (person information) to the user. The user chooses a person and then the chat module asks the person module for the contact of that person.
AND (only) the Qabel related information is in the contact.

from qabel.github.io.

@f-porter: This is related to #20 and we start a discussion already there

from qabel.github.io.

Sorry. It was to earlier. Hit the wrong button

from qabel.github.io.

@k-c13 yes, it is related to #20 but I think @f-porter mentioned something important here and at the first look I would support his suggestion. Let's discuss this on Monday.

from qabel.github.io.

Contacts should keep the possibility. I.e. "module_data" should be there. @f-porter example is based upon an 1-to-n relation between contacts and persons. This is not the case.

from qabel.github.io.