Characteristics of desired proposed standards:
* Strong community leadership to support and use standard
* Potential for impact
* Potential for approval
* Simple standard is better
* Potential for spillover to other communities
What types of standards?
* Two "flavors"
* Standard - Documents Operational Use
* Tech. Note - Builds community awareness
* Describe science content (e.g. Content standard for a level-2 precipitation product)
* Describe interface (e.g. Data Access Protocol, Web Map Server)
* Describe metadata (e.g. DIF, ECHO)
* Describe File Format (e.g. HDF, GeoTIFF)
Soliciting Community Standards
* Propose community practice or convention in science content, interface, metadata, or other to be a standard or tech. note
* For a Standard:
* Identify at least two implementations
* Demonstrate benefits of operation using the practice
* For a Tech. Note:
* Identify current use
* Show potential benefit of broader acceptance
* PROVIDE COMMUNITY LEADERSHIP
Community Leader Responsibilities
* Identify someone in their community who will document the proposed Standard or Tech. Note as a Request For Comment (RFC) according to SPG guidelines
* Work with the community to get an extended review of the proposed standard
* After approval of proposed standard, the leader will work with the community to implement the standard or practice and broaden operational use.
|
|
