[phpwiki]
an issue to deal with when picking an application as the vocore is that
you'll need to map its abastractions and terms into the general system
environment. for example, we're using a mailing list as the vo core which
speaks of lists and subscribers. this is a general groups and members
concept. unless web interfaces are redefined to use a vo-specific naming
convention then users need to map these concepts themselves.
an advantage of using a mlist as the vocore app is that end users can
self regsiter for group membership and there is a concept of administrator
approval for membership. another aspect is that this instantly gives
collaborations an email communication channel to empower their
collaboration.
