... or Registry?
This is a more general point on authinetication. THere are (at least) two main categories
As a further complication, data might be in a catalogue (e.g. an observing log) which is parly public and partly restricted. Do we need to ask data providers to produce separate catalogues/archives? To conform to a standard code for identifying public and private parts?
In the radio archive context, we will have to tackle some of these issues in the next year or so and I thnk that some standards are needed. However to me it seems more a Registry problem than a workflow problem, except that there would need to be some way of passing the identity of the user to a data provider, to decide whether to respond to a query.
cheers
a
On Wed, 19 Jan 2005, Elizabeth Auden wrote:
> > I think it is more important at this stage to concentrate on a few more
> > issues such as:
> > Authentication
> > Community
> > Possibly Authorisation as well.
>
> There is a possible science case that would require authentication /
> authorization for propietary datasets. Silvia Dalla and I talked to some
> of the STP guys at RAL today, and Sarah James has some ideas involving the
> ground-based EISCAT data, part of which is propietary. I know that most
> (all?) of the NASA datasets are public, but do other members of IVOA have
> propietary datasets they'd like to work into workflows?
>
> cheers,
> Elizabeth
>
Received on 2005-01-20Z10:06:45