Difference between revisions of "NASA ACCESS09: Tools and Methods for Finding and Accessing Air Quality Data"
From Earth Science Information Partners (ESIP)
| Line 1: | Line 1: | ||
{{NASA_ACCESS_AQIP_Backlinks}}<br> | {{NASA_ACCESS_AQIP_Backlinks}}<br> | ||
| − | ==== | + | == Outline == |
| − | + | === Problem === | |
* Lots of data resources in NASA, elsewhere | * Lots of data resources in NASA, elsewhere | ||
* Not available as data as services | * Not available as data as services | ||
* if it is a service, e.g. openDaP, may need rich clients, hard coded, loose coupling not easy | * if it is a service, e.g. openDaP, may need rich clients, hard coded, loose coupling not easy | ||
* Even if reusable service is available it cannot be found. | * Even if reusable service is available it cannot be found. | ||
| + | |||
| + | * The Users Dilemma (direct problem) | ||
| + | ** There are '''no data''' for what the user needs | ||
| + | ** If there are needed data, the '''user can not find them''' | ||
| + | ** If the user can find them, she '''can not access''' them | ||
| + | ** If the user can access then, she does not '''know how good they are''' | ||
| + | ** If he knows how good they are, she '''can not merge''' them with other data. | ||
| + | |||
| + | * Providers Dilemma (indirect problem) | ||
| + | ** There are no users for the data | ||
| + | ** If there are users, the provider can not find them | ||
| + | ** If she can find the users, she does not know how to deliver the data | ||
| + | ** If she can deliver them, she does not know how to make it more valuable | ||
| + | ** If the she can make it more valuable... | ||
| − | + | === Solution === | |
* Service Orientation, while accepted has not been widely adapted for serving NASA products | * Service Orientation, while accepted has not been widely adapted for serving NASA products | ||
* SOA allows the creation of loosely coupled, agile, data systems | * SOA allows the creation of loosely coupled, agile, data systems | ||
* SOA -> requires ability to Publish, Find, Bind (Register, Discover, Access) | * SOA -> requires ability to Publish, Find, Bind (Register, Discover, Access) | ||
* While, binding to data through standard data access protocols, publishing and finding requires metadata system | * While, binding to data through standard data access protocols, publishing and finding requires metadata system | ||
| + | |||
* Metadata system for publishing and finding content has to be jointly developed between data providers and users. | * Metadata system for publishing and finding content has to be jointly developed between data providers and users. | ||
Revision as of 15:40, May 30, 2009
Air Quality Cluster > AQIP Main Page > Proposal | NASA ACCESS Solicitation | Context | Resources | Forum | Participants
Outline
Problem
- Lots of data resources in NASA, elsewhere
- Not available as data as services
- if it is a service, e.g. openDaP, may need rich clients, hard coded, loose coupling not easy
- Even if reusable service is available it cannot be found.
- The Users Dilemma (direct problem)
- There are no data for what the user needs
- If there are needed data, the user can not find them
- If the user can find them, she can not access them
- If the user can access then, she does not know how good they are
- If he knows how good they are, she can not merge them with other data.
- Providers Dilemma (indirect problem)
- There are no users for the data
- If there are users, the provider can not find them
- If she can find the users, she does not know how to deliver the data
- If she can deliver them, she does not know how to make it more valuable
- If the she can make it more valuable...
Solution
- Service Orientation, while accepted has not been widely adapted for serving NASA products
- SOA allows the creation of loosely coupled, agile, data systems
- SOA -> requires ability to Publish, Find, Bind (Register, Discover, Access)
- While, binding to data through standard data access protocols, publishing and finding requires metadata system
- Metadata system for publishing and finding content has to be jointly developed between data providers and users.
- Generic catalog systems - metadata collection of not only what provider has done but also tracking what users need
- Communication along the value chain, in both direction;
- Metadata the glue and the message
- Market approach; many providers; many users; may products
