[db-wg] Organisation object proposal

Hello,

> However, none of these provide an easy way of mapping resources to a
> particular organisation. A user looking up data must first find an
> object containing information about a contact point at that
> organisation and then, assuming all of that organisation's objects
> refer to this contact information, perform an inverse query  on the
> Database to obtain a list of objects referencing the specified person
> or role.

what are the legitimate, operationally justified, reasons for compiling this
kind of information?
Who is going to decide what is an organisation and what is only part of
another organisation? E.g. Universities have different kinds of relations
to their institutes, which may or may not be part of the university and even
if, it may be subtle to decide whether they are subsidiaries or not.
The same holds for companies, where subsidiaries are often separate legal
entities. So, unless the ORG object should help build a business (relations)
directory, which I guess is not the goal, what is it good for?

-Peter