anchor.diff:  ** Panel definitions
   ** Part definitions
   
  +TODO
   
   UberFire Metadata Concepts
   ~~~~~~~~~~~~~~~~~~~~~~~~~~
   
   These concepts are expressed in the `uberfire-metadata` package,
  -which appears to be a full-text search and indexing feature (TODO: is this correct?)
  +which is a flexible metadata framework that index and search content.
   
   The UberFire Metadata module includes an API submodule which defines
   the following concepts, and one implementation of the API (a "metadata
   backend") that relies on Apache Lucene:
  +
  +TODO
   
   * Metadata index engine
   * Metamodel store
  
positive.code: +
  Signal a resource has been modified within a VFS. Raised by VFS.
  
  UberFire Backend API Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  These concepts are expressed in the `uberfire-backend-api` module, which
  TODO: characterize this module; it's (mostly) not just for the server-side.
  
  * Deployment
  * Organizational Unit
  * Repository
  * Configuration (server-side only): ConfigGroup, ConfigItem, ConfigurationFactory
  * VFS (Virtual Filesystem)
  
  
  UberFire Client API Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
negative.code: ** Each file in the VFS supports change tracking, revision control, and update notification
  ** File types can be associated with custom viewers and editors
  ** The contents of the VFS can also be searched using a performant full-text search engine
  * Application components can be written in Java or JavaScript. Components can interoperate
    regardless of which language they are implemented in.
  
  