04/09/15 TC

SPG Telecon Notes for September 15, 2004 2pm ET telecon

Attendees:

Rich Ullman, Yonsook Enloe, Jingli Yang, Ming-Hsiang Tsou, Chris Lenhardt, Helen Conover, Siri Jodha S. Khalsa, John Evans, Ron Kwok, Glenn Cunningham, Gi Kong Kim, Allan Doyle, Ananth Rao, Keith Stark, Larry Sugarbaker

Next SPG ALL telecon : Wed Nov 17 at 2pm ET (no Oct SPG telecon due to Oct meeting)

Next TWG004 telecon : Wed Sept 22 at 3pm ET

New Action Items:

• Sept 16 midnight – Sam Bacharach will send out revised RFC003. The revisions will clarify immutability and versioning discussed and agreed upon at today’s telecon.
• Sept 22 – Rich Ullman to send Oct meeting Plenary talk to SPG email list
• Sept 22 – SPG ALL – send Yonsook names & email addresses of potential ESE community (particularly oceanographic) stakeholder reviewers of the DAP 2 spec
• Oct 18 – Rich Ullman will bring his wireless hub to the Oct 18-19 meeting to provide network capability for potential SPG demos

Decisions:

• Agreed that RFCs may have minor edits during the approval process. The TWG will decide during the Approval process what constitutes minor edits. After the Approval process, the SPG will decide what constitutes minor edits.
• Whenever an RFC is revised with minor edits during the approval process, the revised RFC will have a new version number.
• An Errata page will keep a running list of future minor edits that will be incorporated into a new RFC version at appropriate times during the Approval process.
• A version numbering scheme was adopted. A “0.xx” indicate an RFC that has not been approved yet. The “.xx” may be incremented for each revision that contains minor edits before Approval. The “0.xx” will be changed to “1.0” after RFC Approval. All revisions after final Approval will result in whole number increase of the revision number. The version numbering scheme is documented on the SPG website.
• RFC 003 – next steps – want to close out the RFC 003 and have that approved. After we go through the Approval process with the DAP 2 and with other specs, the RFC 003 may have further revision. However, it would be beneficial to have an approved RFC003 in the near future. After Sam completes the revisions on Sept 16, the SPG should approve the RFC003.

Notes/Discussion:

• The “How to Submit” guide, the RFC 002, and RFC 003 have been “synched” with the info on the SPG website and also with making the “Motivation” section and the “evidence of Implementation” section more robust in RFC 003. These changes were continuously emailed to the SPG email list during the email discussions since our SPG telecon two months ago in July.
• Changes to RFC 002 have been made to document a revision in the original “immutability” idea. From our initial process run through with the DAP 2 spec, we find that we need to allow minor edits to the submitted RFC. Changes to the RFC 003 need to be made to clarify the “immutability” idea. Sam will do that.
• RFC 004 – DAP2 status. TWG has been formed and met via telecon. A couple of volunteers are working on drafting written guidelines to send to reviewers reviewing the DAP2 spec. We plan to finalize on these reviewer guidelines next week and start the DAP 2 public review process. Rich has contacted HQ about names of stakeholders to specifically include in this public review. Got response from Martha Maiden, Mary Cleve, and Ron Birk. These are people we want to make a special effort to make sure they comment on the spec. We are soliciting other stakeholder names from the SPG. Send names to Yonsook by Sept 22. We will also take names after that date too.
• Oct 18-19 ESDWG meeting – Rich will do basically the same presentation at the Plenary part that he did at the ESIP Federation meeting in August. For the WG breakouts, we need to plan two breakouts. For the first one, James Gallagher, author of the DAP2 spec, has been invited to speak about the tech aspects of DAP2, the community support for DAP2 and its potential impact, and his feedback on the RFC experience/process so far. For the second breakout, the FGDC speaker will discuss her lessons learned in the FGDC community standards activities.
• Plone email gateway is working. All SPG email is viewable and searchable on the SPG website. TWG email lists are not connected to this gateway. TWGs need to have certain amount of confidentiality in their evaluations.