Difference between revisions of "Interoperability and Technology"

From Earth Science Information Partners (ESIP)
Line 15: Line 15:
 
Upcoming meetings 3pm ET ([https://www.esipfed.org/get-involved/community-calendar calendar])
 
Upcoming meetings 3pm ET ([https://www.esipfed.org/get-involved/community-calendar calendar])
  
[[File:ITI_Sept_IoW_Kyle-Onda.png|thumb|IT&I IoW September 2023]]
+
<!--[[File:ITI_Sept_IoW_Kyle-Onda.png|thumb|IT&I IoW September 2023]]-->
  
September 14th: [https://internetofwater.org/about/people/kyle-onda/ Kyle Onda]
+
October 19th: [https://www.ogc.org/about/team/scott-simmons/ Scott Simmons]
  
Water data standardization: Navigating the AntiCommons
+
Improving standards and documentation publishing methods: Why can’t we cross the finish line?
  
We all know interoperability rests on data standards and API standards. Many open standards are less prominent in the open water data space than proprietary solutions. This is because proprietary data management solutions are often bundled with very easy to use implementing software and more importantly—client software that address basic use cases. We’re giving people blueprints when they need houses. Community standards making processes should invest in end-user tools if they want to gain traction. The good news is that some of the newest generation of standards is much easier to develop around which has led to some reference implementations that are much easier to create end-user tools around than previously.
+
OGC and the rest of the Standards community have been promising for YEARS that our Standards and supporting documentation will be more friendly to the users that need this material the most. Progress has been made on many fronts, but why are we still not finished with a promise made in 2015 that all OGC Standards will be available in implementer-friendly views first, ugly virtual printed paper second?This topic bugs me as much as it bugs our whole community. Some of the problems are institutional (often from our Government members across the globe), others are due to lack of resources, but I think that most are due to a lack of clear reward to motivate people to do things differently.Major progress is being made in some areas. The OGC APIs have landing pages that include focused and relevant content for users/implementers and it takes some effort to find the owning Standard. OGC Developer Resources are growing quickly with sample code, running examples, and multiple views of API resources in OpenAPI, Swagger, and ReDoc.
  
 
===== ESIP Vision =====
 
===== ESIP Vision =====

Revision as of 07:06, October 4, 2023

Welcome to the Information Technology and Interoperability Committee Wiki
Committee Chair: Dave Blodgett

Get Involved

The IT&I committee provides a venue for a monthly community webinar on current Information Technology and Interoperability topics. In early years, the webinar series was known as the "IT&I Rants and Raves" a title the committee is bringing back starting in 2023.

Rants and Raves are designed to get smart people to share insightful, provocative views of what's great and what's not about technology and interoperability in modern Earth science. We welcome, high energy talks on personal pet peeves: topics that you can't believe in this day and age we're still dealing with, or solutions that you can't believe that in this day and age more people aren't using.

Upcoming meetings 3pm ET (calendar)


October 19th: Scott Simmons

Improving standards and documentation publishing methods: Why can’t we cross the finish line?

OGC and the rest of the Standards community have been promising for YEARS that our Standards and supporting documentation will be more friendly to the users that need this material the most. Progress has been made on many fronts, but why are we still not finished with a promise made in 2015 that all OGC Standards will be available in implementer-friendly views first, ugly virtual printed paper second?This topic bugs me as much as it bugs our whole community. Some of the problems are institutional (often from our Government members across the globe), others are due to lack of resources, but I think that most are due to a lack of clear reward to motivate people to do things differently.Major progress is being made in some areas. The OGC APIs have landing pages that include focused and relevant content for users/implementers and it takes some effort to find the owning Standard. OGC Developer Resources are growing quickly with sample code, running examples, and multiple views of API resources in OpenAPI, Swagger, and ReDoc.

ESIP Vision

To be a leader in promoting the collection, stewardship and use of Earth science data, information and knowledge that are responsive to societal needs.

Information Technology and Interoperability Committee

The Information Technology and Interoperability Committee of the ESIP Federation is a standing committee created to:

  • ensure that data, information and services can be readily exchanged and integrated to improve Earth science data, information, products and services; and
  • encourage the use of standards and protocols relevant to interoperability;
  • encourage the use of best information technology practices to ensure the quality, usability and breadth of standards and protocols relevant to interoperability.

Archive

ISRSE 2009 Demonstration Information

More recent technical workshop information is integrated into the meeting content pages accessible from the home page.

Summer 2007 Technical Workshops

Metadata Catalogs

Committee Members

Summer 2006 Technical Workshops

Winter 2007 Technical Breakouts

IT

Client Side Technology Infusion Working Group

2010 Rant and Raves Webinar Series and Telecon Information

Summer 2010 Technical Workshops

Solicitation for Outreach Package Development

Summer Meeting 2010, Knoxville, TN Meeting Notes

Winter Meeting 2011, Washington DC

2011 Rant and Raves Webinar Series and Telecon Information

Jluly 12-13 Summer Meeting, Santa Fe, NM