up:
Navigating Enid

  1. Frontends to Enid, for example WebEnid should implement these features:

    1. Displaying parent links

      1. This is arguably the most important idea of Enid as it enables contextualization.

    2. Folding of subentries

      1. This helps getting a quick overview of complex/deep trees and reading only the parts one is interested in.

    3. Loading deeper entries at request

      1. For reasons of performance and data size, Enid frontends are recommended to load deep subentries only at request.

      2. This feature allows for free navigation in an Enid dataset while still being zippy and fast.