DB User Intf Proposal

 * >- how many people would have to have authorisation? You may end up
 * >with *many* people who need authorisation. It's basically a scaling
 * >issue, which we will have whatever we do with large amounts of data
 * >maintained by different organisations.
 * 
 * I'd been thinking that you'd need as many authorizations as you have 
 * guardians.  But I think I understand what you're saying.  You're saying
 * that right now, not all objects are guarded and therefore people can make
 * changes to certain objects without having accounts.  And you're wondering
 * if I'm proposing that for anyone to be able to change data in the database,
 * would they have to have a userid and passwd, yes?

Yes. WHere does it stop? 

I am in the middle of a brainstorm session on the whole guarded
attribute/object procedure, because I think it can and has to be done
different. Expect some ideas tomorrow or Friday. I want to get some
feel on what the right direction for the implementation for the
principle of guarded information should be.

Cheers,

-Marten



-------- Logged at  Wed May 18 23:08:25 MET DST 1994  ---------