[doap-interest] doap:user?

[Thomas Vander Stichele]

Hi,

> See [1], the direction generally doesn't matter. With a DOAP-related
> prop however, it may actually matter, but should be from the project
> to the user: DOAP does a neat trick and integrates both projects
> and the software created by the project in a single vocabulary. This
> means that properties like license, tester, etc, have a a bit more
> complex semantics by not really describing "license of the project",
> "tester of the project", but "license of the software created by the
> project" and "tester of the software created by the project" 
> respectively. For consistency reasons, a doap:user prop could use
> the same pattern and should IMO be part of DOAP.

You didn't address the main concern: the fact that it is a lot easier
for a user of software to update a list of software he uses, than it is
for a piece of software to update its list of users.  Using software is
an active, unidirectional relationship, where the user initiates, not
the software.

The link you paste only says that you are free to choose who links to
who; this means that you should probably choose on other criteria, for
example convenience.  It is definately more convenient - and correct,
when changes are made - for the user to link to the software.

Thomas