Logos support self-debugging and documentation for forum question responses by making it easier for users to identify features available to them and for people answering questions can point users to for them to understand why a feature is not available.
Such a feature would show four overlapping types of features;
- There are features available to everyone. These would always be in bold.
- Features owned from feature packages or "leased" from subscriptions. Bold would indicate owned, normal indicate leased, italics neither owned or leased
- Features requiring a particular dataset: list the datasets beside the feature - bold if owned or leased, italics if not available
- Features requiring the download of particular resources - using an example from those meeting the rule of required resource giving priority to those in the users' library - bold if downloaded, normal if owned or leased but not downloaded, and italics if no appropriate resource is owned.
Adjust the attributes for which I use bold, italics, natural with any encoding scheme you would like.
Furthermore, verify that the minimal download algorithm includes resources required to make features work. It currently leaves some holes.
