Extensions to GSA Standards


 

Standard Extension Development Timeline graphic

An extension is an addition to an existing GSA standard developed separately from GSA for eventual inclusion in a GSA standard. The extension is designed to provide new capabilities by extending the functionality of an existing GSA standard. Once approved by the Technical Committee or by the BOD, the extension becomes a standalone document under the ownership of GSA and is maintained by the appropriate Technical Committee. The functionality represented by the extension is incorporated in the next minor or major revision of the GSA standard, whichever comes first. Redundant functionality will be identified by the committee, which will determine if it's necessary.

Extensions are unconditionally donated to GSA for inclusion into the applicable GSA standard. Once GSA accepts the extension, GSA takes ownership of the document, any associated schema files, and their copyrights. The donor maintains intellectual property rights.

Extensions are treated as part of the normal standard development process. Submitters of extensions must be opted-in to the committee charged with development of the standard being extended.

The following sections describe the process of incorporating extensions into the applicable standard.

EVALUATION OF PROPOSED EXTENSION

  1. The submitter of an extension will provide the documentation and any associated files (such as schema) for an extension to a standard for evaluation by designated GSA Staff. GSA Staff will make every effort to respect the proprietary nature of such submissions.
  2. Designated GSA Staff will review the documentation and any associated files and provide a report to the submitter within a mutually agreed upon time frame. The extensions will be reviewed on a first come first served basis, regarding:
    1. Errors - Errors must be corrected prior to inclusion in a version of the protocol. Errors are defined as:
      1. Schema validation errors, if applicable.
      2. Incompatibilities with the existing GSA schemas, if applicable.
      3. Incompatibilities between the schema and documentation, if applicable.
      4. Incompatibilities that cause the extension not to interoperate with the standard it is extending.
      5. The use of GSA-assigned manufacturer IDs or other manufacturer-specific information in error codes, event codes, enumeration values, examples, and other aspects of the protocol and related schemas, if applicable.
      6. The use of namespaces and namespace prefixes that do not conform to conventions established from time-to-time by designated GSA staff.
    2. Recommendations - Recommendations for improvements may be provided to the submitter. Upon submission of the extension to the Technical Committee, any recommendations not implemented by the submitter may be disclosed by designated GSA staff to the Technical Committee.
    3. Redundant functionality - The submitter will be informed about the details of the any redundant functionality that is included in the extension. Upon submission of the extension to the Technical Committee, redundant functionality will be disclosed by designated GSA staff to the Technical Committee.
  3. Designated GSA Staff will work with the submitter of an extension to resolve any issues and to facilitate the inclusion of the extension in the standard being extended.

INCLUSION OF EXTENSIONS IN GSA STANDARDS

  1. Once all relevant issues have been resolved, the submitter will submit the documentation and any associated files for the extension to the Technical Committee for consideration. The submitter will also clearly articulate the business need for the extension. The committee will process all submissions on a first come first serve basis.
  2. A mutually agreed upon time frame for evaluating the extension will be determined by designated GSA Staff, the committee Chair and the submitter. This time frame must not be less than fourteen (14) days. For major extensions, such as new classes, at least thirty (30) days should be allowed. Within the agreed time frame, designated GSA Staff, the committee Chair, and the submitter will identify deadlines for comments and responses as well as the date planned for the Formal Meeting to vote on the extension.
  3. Questions and comments from the Technical Committee must be presented to the submitter by the deadline established for the extension. The submitter is under no obligation to respond to questions or comments presented after the deadline.
  4. The submitter will actively participate with the Technical Committee during this process and will respond within 7 days to questions or comments presented by the Technical Committee. All responses must be submitted at least seven (7) days prior to the date planned for the Formal Meeting to vote on the extension. If the submitter does not respond as required, the committee Chair may suspend or terminate work on the extension. In such cases, the committee Chair, with the approval of designated GSA staff, may suspend the submitter's right to submit or resubmit extensions for up to three (3) months.
  5. The time frame for evaluating the extension may be extended by mutual agreement of designated GSA Staff, the committee Chair and the submitter. In such cases, new deadlines will be announced and a new date for the Formal Meeting to vote on the extension will be established.
  6. A Voting Committee Member may make a motion at a Formal Meeting to accept the extension into the standard. If the committee does not accept the extension, the submitter may amend it and resubmit for consideration by the committee at a future time or the submitter may request that the BOD review the extension for approval. The BOD may affirm the committee's decision to reject the extension or may reverse the committee's decision and approve it. If the extension is rejected, the submitter may modify and resubmit it to the committee or may withdraw it from consideration. If the BOD approves the extension, they will notify the committee so that an appropriate document may be prepared.
  7. If the extension is approved, the extension documentation is formatted, and GSA will release the extension upon final approval by designated GSA Staff, the committee Chair, and the submitter. Provided that there are no changes to the content of the extension, a final vote by the Technical Committee is not required to release the extension.