See Readme.doc or Readme.pdf for more information about some of the issues below.
Also see known_bugs.txt for implemented features with reported problems.
A plus sign (+) indicates additional items after the 0.5.2 release

Unimplemented feature requests:
- Implement support for demograpic archetypes
- Implement support for strict CEN 13606 archetypes without openEHR additions
- Implement import tool for SNOMED CT distribution files to TermViz
- Optimize and re-enable TermViz  terminology visualization tool in the editor 
  which allows browsing and making terminology bindings from SNOMED CT in a 
  convenient way.
- Implement a connection to an archetype service which allows archetypes to 
  be version controlled.
- Installer and/or Java Web Start
+ Fix look & feel for Mac (probably by adding detection + manual l&f selector)
+ Update help files and add help for newly added features
+ Clarify meaning/names of buttons in the formats view
+ Clarify in doc & help what the archetype repository setting should point to
  and document how to open slots in a new editor instance in the same JVM
+ Improve drag-n-drop behaviour e.g. insert/move and when moving things in 
  and out of clusters 

Unfinished but experimentally enabled features:
- The interface view is far from fully developed and the interface generated
  from some archetypes or parts of archetypes may be blank, incomplete and
  incomprehensive. Also usability of the view needs to be vastly improved.

Redesign:
- Make the editor validate archetypes against the openEHR specifications, 
  XML-schema or the reference model classes of the Java reference implementation.
  The current validation is hard-coded and will throw away unknown elements.
+ Better documenation and error alerts before "unknown" elements are thrown away
  now before we get time/possibly do the validation redesign described above.
- Use Java Internationalisation (I18N) and externalize text strings to enable
  easy translation of the editor into other languages
- Switch Log4j’s logging application LogFactor5 to the newer application Chainsaw
  and make the editor alert the user when something has been written to the log.
  Currently log messages do not appear automatically in the log window even though
  they are written to the console and to the log file (in the root directory of 
  the application). THe log File has to be opened manually in the viewer.

For redesign issues also see the file Readme_implementers (in the source 
distribution or the Subversion repository).

Site(s) & Mailinglists:
+ Create and add video (screen capture) instructions for 
    Installation
    Sample archetype development
+ Add Jira for CRs/PRs when it has been installed on the openEHR servers
+ Check that archiving of mailinglists starts to work