DB User Intf Proposal

>
>Andrew,
>
>I had a quick look and it looks nice. There's a few things that need
>sorting out:
>
>- this is not very good for people who maintain lots of data. I would
>in such cases prefer to just send it in using email or something else.
>I prefer my own editor over Mosaic.

Agreed.  It seems like it might be good for short editing operations like
editing a short AS object, or one or two network objects.  But if one
wants to make wholescale changes, being able to use sed/awk/parsing programs/
ftp/etc is probably easier.

>
>- 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?

>
>I am basically stating what you say in your last paragraph, we should
>realize in what cases this is useful and in what cases there may be
>other ways that may be easier.
>

Agreed.

>-Marten

-Andy



-------- Logged at  Wed May 18 20:55:55 MET DST 1994  ---------