Proposal Template

Guidelines on the completion of a Proposal for submission to the IODE / JCOMM Standards Process

Introduction


The IODE/JCOMM Standards process seeks to identify and approve Proposals that support the collection, management and exchange of oceanographic and marine meteorological data with an emphasis on improving the interoperability of these data.   As envisioned, these Proposals will provide mature, proven practices including:

  • well tested methods for managing data or information that if widely used would provide greater consistency in treatment;
  • methods that encourage the convergence from multiple solutions to a problem, to fewer, more robust solutions;
  • methods that can be used widely in the marine meteorological and oceanographic community;
  • vocabularies which permit unambiguous and machine processable data and information descriptions.

This guide outlines the template for Proposal submissions to the IODE/JCOMM Standards Process and describes the content to be included.   Use of this template for the Proposal ensures the information provided is as comprehensive as possible in order for (1) the efficient evaluation of and movement of the Proposal through the IODE/JCOMM Standards Process and (2) planning the intended application and dissemination of the proposed standard.  

Send proposals to This email address is being protected from spambots. You need JavaScript enabled to view it.

Please consult the document that describes the Standards Process.

Template Guidance


The Proposal template contains ten main elements and provides content descriptions for each.   Proposals may be comprised of a single item (vocabulary, operating procedure, etc.) or multiple items     If a series (multiple items) is proposed having a common purpose and justification, a common Proposal may be drafted including all elements to be clarified and enumerating the each individual item.   Consider this template as a €œcover sheet € to the more comprehensive materials associated with the Proposal.


Title:   Titles should provide an indication of the subject, scope and purpose of the Proposal (for example: Adoption of ISO 3166-1 and 3166-3: Country Codes)

Scope:   Provide a clear indication of the extent of the Proposal €™s application.   Identify any specific data communities (based on data management functions, types of data, observations, etc.) to which this Proposal could apply.   Indicate any known limitations or exclusions where the Proposal is not adequate.  

Envisaged publication type:   Briefly describe the target audience for this Proposal and any outreach plans to be considered.  

Purpose and Justification:   Provide details based wherever practicable.

  1. Describe the specific aims and reason for this Proposal, with particular emphasis on the aspects of standardization covered, the problems it is expected to solve or the difficulties it is intended to overcome.
  2. Describe how this proposed standard supports data management, exchange or interoperability.   When applicable include mention of what data management functions (e.g. date transport, quality control, archive, €¦) the proposal supports.
  3. Describe the main interests benefitting from or affected by the proposed standard, such as industry, consumers, governments, distributors.   Identify any relationships and/or dependencies.
  4. Describe the feasibility of implementing the proposed standard.   Include any factors that could hinder the successful establishment or global application of the Proposed standard.   Are there any associated issues?   Identify resource implications resulting from the recommendations.
  5. Considering the needs of other fields or organizations, indicate the timeliness, target date(s), or if proposing a series of standards, suggest priorities.     List any statutory requirement or other driving factors.
  6. Describe the possible benefits gained by the implementation of the proposed standard. Alternatively, describe the loss or disadvantage(s) if no standard is established within a reasonable time.
  7. Indicate whether the proposed standard is or may become the subject of regulations or may require the harmonization of existing regulations.   Describe any impacts of this activity.


Current Operational Implementations:   Provide information about organizations, programs or projects which currently use the Proposed standard as part of an operational environment.   If there are none, please indicate organizations that are testing the standard.

Relevant Documents:  

  1. Provide the reference(s) to all documents or materials associated with this Proposal (e.g. standards, specifications, regulations).   Where Proposals comprise multiple documents or files, include a brief description of the relevancy of each as well as any dependencies among these materials.
  2. Attach copies of all relevant documents or materials to this proposal.   Where copyright policies restrict the attachment of the documents, indicate these by providing a listing along with the resource through which these documents may be obtained.


Cooperation and liaison:    

  1. Existing Community:   List relevant organizations, bodies, work groups or related projects which currently use the Proposed standard and through which cooperation and liaison could be extended to the broader community.   Include organizations, programs, etc. supporting the submission of this proposal.
  2. Expanded Community:   List relevant organizations, bodies, work groups or related projects not currently employing the Proposed standard and with which cooperation and liaison should exist.  


Contact information:   Provide the contact information of the Proponent.   This individual acts as the key point of contact for interaction with the ETDMP Chair on this proposal.   Include the Proponents name, organization, email address, and telephone number.

     Name:
     Organization:
     Email Address:
     Telephone Number:

Proposal version:   Define version of proposal if proposal was amended during evaluation process early (for example, v.1, date).

List of Acronyms:   Define all acronyms used.

Other Attachments:   Provide a listing of any additional attachments to this Proposal.   Attachments many include letters of endorsement, technical reviews, lessons learned documents, etc.

User Login