SDS:Feb 4 2009 Meeting

From Tetherless World Wiki

Jump to: navigation, search

Agenda February 4, 2009

Peter, Patrick and Stephan

  • I moved the project information to the bottom of the page, it's just in the way. Feedback?
  • January 28 and February 2 recap/update
    • On the 28th we said "ppt client, during handshake, will pass the credential during authentication. The BES will return a token that future requests to the BES will need to match to that credential." ... why did we say that the BES would return a token? We can't see a case where this token would be worth while.
      • For now we will not pass back a token
      • We need to have another discussion to work on this again. We were certain that we wanted a token passed back like this, but can not recall why we decided this. Has to do with the OLFS being able to use this feature. But because the OLFS has 10 stateless connections to BES listeners how can we do this unless everytime a new user comes in with a credential the OLFS passes the new credential to the BES and the BES passes a token associated with this credential back to the OLFS. Any future requests by the user will require the token that the OLFS passes along to the BES so that it can use the associated credential.
    • delegated credential support - further discussion?
      • share with Globus folks and OPeNDAP folks
      • Authorization is done on the NCML file, not the individual files that make up the NCML file. So there's only one authorization call made, for the NCML. This is done at the first BES.
  • Do we want to have gpg signed downloads for all of our releases (OPeNDAP page on how to do this)
    • yes ... and also do checksums. Need to set up an email to do this. OPeNDAP uses security@opendap.org.
  • Case 71 - "Design Document for NcML aggregation (rough draft)" - due today
  • OOI
    • OPeNDAP work - possible IOSP (I/O Service Provider), AMQP (Advanced Message Queuing Protocol), Aggregation
      • AMQP - could be a replacement for PPT in direct connections to the BES, or it could be a protocol used to an OLFS-like middle-tier which connects to the BES using PPT.
    • Semantics
      • leverage VSTO
  • WHOI
    • starting to ramp up on semantics and some OPeNDAP work
    • March visit might have WHOI folks come up for meetings, installs. Need to have escience framework up and working by then.
  • Stephan's work with LI on migrating the project web sites - building a new RNI site
Email from Stephan to Peter and Patrick

I think it would be beneficial for every project on the TW wiki to be a collection of pages linked by a consistent project-scope
navigation mechanism.  I want to have a navigation mechanism similar to the project section sidebar we use on the hao.ucar.edu
websites, but more importantly I want a consistent alternative to just dumping everything on one page with a generated TOC at
the top, such as http://tw2.tw.rpi.edu/wiki/r2d2/index.php/SPCDIS.

I found an example navigation bar on wikipedia at
http://en.wikipedia.org/wiki/Template:Evolution3

Using that as a framework I hacked together this
http://tw2.tw.rpi.edu/wiki/r2d2/index.php/Template:TestNavigation

With this in mind, I think the 'Project Template' should create a series of pages, each with the navigation sidebar.  My example
sidebar has no semantics in it, but I can see a scenario where instance information on the project is used to generate the sidebar
template.

What are your thoughts?

Feel free to edit the template as you see fit, you should be able to logon to the tw2 wiki using your normal tw account. 
  • Two new project starts
    • MDSA
    • SAM (Smart Assistant for Mining)
  • trip next week
    • Sunday arrival at Dulles
      • Peter gets in at 9:09pm
      • Stephan and Patrick get in at 8:53pm and will wait
      • Meet at United baggage claim #4 near escalator, taking bus from there
    • Monday meeting
    • Agenda for Tuesday - Thursday
Personal tools