November 5, 2009

From Earth Science Information Partners (ESIP)
Revision as of 16:11, November 25, 2009 by Carolbmeyer (talk | contribs) (New page: ==November 5, 2009 Telecon== 1-3 pm EST <br> Phone: Meeting Number: 877-326-0011<br> Meeting Code: *7884944*<br> GoTo Meeting Link: https://www2.gotomeeting.com/join/975746403 ===Topi...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

November 5, 2009 Telecon

1-3 pm EST
Phone: Meeting Number: 877-326-0011
Meeting Code: *7884944*
GoTo Meeting Link: https://www2.gotomeeting.com/join/975746403

Topics

(feel free to add agenda items)
1. Recap of Last Meeting
2. Update on Small Group Call
3. Crafting Mission/Objective Statement for Group
4. Proof of Concept Components

Ontology basis
Registries Utility
Display Integration and Analysis Tool
Use Case - Location &/or Research or Policy Question

5. Organization of ESIP Winter Meeting Activities
6. Date of Next Call - December 3rd

Meeting Docs

Participants

  • Chuck Spooner
  • Bill Sonntag
  • Ed Washburn
  • Carol Meyer
  • Jim Etro
  • Brian Rogan
  • Jami Montgomery
  • Rob Raskin
  • Phil Yang
  • Luiz Bermudez
  • Will Pozzi
  • Montira Pongsiri
  • Mike Brewer
  • Rick Hooper

Notes

Recap of the past meeting.


A discussion of the ontology basis

Rick Hooper was planning on getting the ontology in good enough shape to update our registry. Then try to expose this to a user group. It won’t be quite ready for the January meeting but will be good enough to show it to a user group.

Luiz summary of the state of ontologies: “ There are a number of groups trying to do this but there are no definitive answers. There are some pieces missing that still need to be included. We have the pieces but we need to know what are the next steps. Are we going to use Hydroseek? What are we trying to show? What ontologies are you going to use to map the interfaces? “

He will be talking with his working group to see how this will work.

There was a discussion on whether the group should also work on developing a water portal for this cluster?

Registry services – for international and reuse purposes, the largest extent of standards deployment is for international marine assessment for climate issues.

There was a general discussion of what is Hydroseek going to look like?

This is not a fine tuned issue yet. For the purposes of demonstration, we are going to try things this way with a lot of disclaimers, with changes to come from users.

The discussion was about various browsers that would work with Hydroseek and other catalogs.

The topic needs further exploration. There are a lot of ideas and it would be good for us to work towards one tool. Both Hydroseek and SciScope have good points but they need to be flexible enough and to be open sourced.

Is the need to deploy this into a client actually the second stage and the need to operate should be first? It seems as if this is a difficult question to answer since you have to know how well it works first.

Will Pozzi raised the issue of a finding a way to use this methodology for information searching. May we have to expand the ontology to cover droughts. There is a lot of work needed to be done in the drought sector. This could be an import case study to look at the client.

Rick Hooper presented the CUASHI hierarchal ontology. They have been using the groups that EPA/USGS has come up with. It’s a viewer than can be used by anyone. The URL is on the wiki in the water cluster.

Chuck Spooner felt that an operational model is needed

Winter Meeting Discussion Carol began the conversation about the winter meeting.

There needs to be time to get people up to speed on what the cluster is all about and how an ESIP meeting works. A “this is our starting point” is important.

It’s important to discuss the ontologies with the general community. People who are participating in this series of telecons will step on to lead discussions and other activities with new participants.

Some of the follow-up meetings with CUASHI and Microsoft will help to facilitate what will occur at the meeting. Some of what will happen at the meeting is still up in the air.

Is there something we can point to, to frame the conversation? Context is an important part of the conversation. This would make perfect sense if we had a defined software product but we aren’t there yet. At the moment we have different groups doing different things. It is the nature of the community.

In terms of the winter meeting, we do want to present what we are working on in the context of user cases. This is a tool you can actually use. The desktop client is getting all of our attention right. How we introduce this to a non-technical group needs to be done in the context of what can it do for them?

Within the ESIP community, this is an easy sell. How do we organize ourselves when we are meeting face to face to get the most mileage out of that time?

Bill asked if the 1-4 agenda he posted on the Wiki would work as an agenda as well for the winter meeting? If needed, it could be parsed and prepared for the winter meeting.

Some of this may be served as a poster session rather than rehash what has been discussed and people can self select what they would be involved in. Is the proof of concept idea working?

What is the best way to convene this group and the Semantics group during meeting?

What topics can we have at the meeting?

User groups Ontologies Semantics Tools discussion -Open Source and HydroSeek

There was a discussion about making the best use of the poster session. This would include the capability to have demos and then use the breakout sessions to use the tools. In the poster area we should also be able to do demos.

CUASHI would like to see a use case and show what it can do.

It was felt that it might be beneficial to have a discussion with Peter Fox and Jim Hendler to see how to merge the groups (water and semantics) at the meeting and what could be discussed.

Next Steps -crafting a mission and objectives statement -have a conversation to how to craft a January call -Look at the components of a proof of concept -Work with the people in the office on user cases


Meeting ended 2:20 PM

Action Items