NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [Fwd: THREDDS and lightly restricted datasets]

Hi James-
The standard WMO40 policy statement is not that large (in terms of words it's a short para.). The point is that the user must accept the policy and we then store that acceptance in a file for future reference. Of course it's not just a display issue but a use (private sector mostly) and a re-distribution policy. Most state that qualified data providers cannot re-distribute a dataset for 48hrs after creation. These data sets are small in number but a bigger (more important one in my mind) are 'restrictions' by scientists- not wanting their data "out there" yet. A scheme to allow access by colleges via DODS would be most useful. Glenn 
James Gallagher wrote:


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
  • 2004 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: