====== BTL WG ======

===== Work Items =====

==== Issues ====
  * Clarification Requests
  * SSPC requests
    * Interpretation requests
    * Proposals
  * test definitions
    * missing, bugs
  * test script implementations
    * missing, bugs

==== Documents ====
  * BTL Test Plan
    * Test definitions
  * Certification Handbook
  * Implementation Guidelines

===== Issue Management =====
  * {{:bacnet:lori_btl_workflow_documents.pdf|Lori's BTL workflow idea}}
    * "Internal Task List" and "Running Change List" can be represented by "Version" and "Milestone" fields of an ITS
    * documents can be referenced in corresponding issues is a seperate field (hyperlink to document storage (SVN, GoogleDocs, ...)
    * :?: Why should addenda be necessary? Why not collect changes (addenda, errata) into a minor version Test Package (e.g. 9.1, ...), which is released regularly?
    * "Summary of changes" could be all resolved issues with a certain Milestone 
  * :!: BTL-WG Meeting Minutes 2011-11-14 2c: efficiency improvement discussion

===== Analysis =====
  * Why are not all files on the FTP?
    * most current work item files
      * e.g. wID0044
    * most current draft test plan and test definitions
      * e.g. TP9.0c-5
  * Where can one find out what work items made it into which test package version?
    * work-to-do: ACCEPTED and "TestPkg Rev"
  * Why do we not keep the most current work-to-do in one place on the FTP?