Peter, Stefano, Glenn, Benno,
I've been thinking about this and I thought I'd mention an idea Peter
ran by me (I hope that's OK, Peter).
Peter's suggestion: One possibility would be that the client notify the
server that it is aware of the fact that a display policy is required
for a given data set. Without this the server responds with an error.
One slight twist on this would be to have clients include this
'announcement' in every request and to encode the copyright/use info in
every response. This would map easily into the DAP's design and would be
easy to implement using web services stuff, as Stefano points out.
I suppose the copyright/use policy could be large; do you all know of
any such cases? What I'd like to avoid is a plan that involves
maintaining state at a server or multiple trips to the server. I'd also
like something that will work in both human and machine clients.
James
--
__________________________________________________________________________
James Gallagher The Distributed Oceanographic Data System
jgallagher@xxxxxxxxxxx http://unidata.ucar.edu/packages/dods
Voice/Fax: 406.723.8663
