1. Design of API
   - The API decided upon by the group must be the
      standard that all vendors conform to.
   - The API should be feature complete with regard
      to basic operations needed in modern applications
   - Last point means that the API might change with time
      as long as revision numbers can be used to make sure
      that as few applications as possible are broken as
      few times as possible.
   - The group must strive for a stable API (as long as it
      don't hinder new technologies).
   - The group must strive for an API without bloat.
   - All D compiler vendors must distribute a standard
      library implementing this API.
   - The API should be consistent over different platforms.
   - The API must follow the API style guide.
   - The API should not be just a wrapper for C APIs. As an
      example, the Windows API should be provided in own
      (preferebly standard) packages and shipped with the
      compilers (like the Windows headers are with C
      compilers).

2. Mantainer of sample implementation
   - The group should mantain a sample implementation
      (the first iteration should probably be Phobos).
   - The sample implementation should be as stable as possible.
   - The sample implementation should strive for correctness
      before optimizations.
   - The implementation should be as independent as possible.
   - The implementation should follow the code style guide.