Extrinsic Policy

To be considered for HPFF recognition, a proposed extrinsic must demonstrate the following things. It should be noted, however, that meeting these criteria does not guarentee acceptance of a proposed interface by HPFF.

• conformance to HPF rules for calling extrinsics,
• significant new functionality,
• existing practice such as users, implementations, etc.,
• institutional backing with evidence of ongoing support,
• coherent documentation,
• non-proprietary interface definition, and
• copyright goes to HPFF for interface, with permission to use (royalty free).

If a proposed extrinsic is accepted by HPFF, then:

• HPFF will recogize the interface and reference it in documentation, but HPFF does not assume responsibility for the extrinsic or its interface.
• The sponsor of the extrinsic must continue to conform to the HPF interface rules for extrinsics. The interface HPFF approves must not change without HPFF approval.
• The sponsor must assume responsibility for any CCI requests concerning the extrinsic.

A list of recognized extrinsic interfaces will be included in HPF documentation, with the following guidelines:

• There should be a single page introduction to the extrinsic which contains:
  • the name of the extrinsic,
  • a brief abstract of functionality,
  • a brief and informal description of the interface,
  • information about platform and system availability, and
  • reference and contacts for formal documentation, continued responsibility, and additional information (e.g. compiler availability).

• There should be about two pages with short examples of usage.
• A short paper with the formal definition of the interface and an informal description of the functionality of the extrinsic.