Site: To-Do List

This file contains pending tasks for the site package.

• Completed tasks
• Keywords
• Oldest Entry (at end.)

1. Bug problems when a document renames itself.
   If an ordinary document renames itself, e.g. by using <filter> to invoke mv, it can no longer be found. This is because the original SiteDocument node is still present. The correct solution is a rename operation that does the right thing. (2000-12-05)
   
2. Hole need write-and-create-backup op.
   See corresponding wish in ../dps/to-do.html . (2000-12-05)
   
3. Bug problems when directory tree changes
   Deleting a directory out from under a running PIA causes a null pointer exception. Adding a real one doesn't hurt, but it isn't seen, either. Really need to check timestamps up the parent chain when real or virtual directory is null.
4. Bug pia: broken for config files and tagsets
   Can't specify a tagset relative to pia:, for example. For includein config files, at least, it's because they're not loaded using the Subsite under construction. (2000-06-01)
   
5. Bug Loop in tagset inheritance not detected
   If a tagset includes or inherits from itself, loading should resume from one level up in the Subsite tree, or from /lib if at root already. (1999-12-14)
   
6. Bug Subsite config loading and caching not thread-safe
   (1999-11-19)
   
7. Bug Subsite not loading stripped tagsets
   There is also no indication of where a tagset is actually loaded from. (1999-10-14)
   
8. Impr Use attributes for property handling
   Using attribute defaults (which we don't have), let properties have attributes ``map="prop"'', ``list="prop"'', and ``inherit="yes"''. (1999-10-13)
   
9. Bug Do not keep config nodelist around
   Process the nodes on the fly instead of collecting them; probably want a ToResource output to handle them with. (1999-10-08)
   
10. Check locateChildFile for virtual links
    (1999-09-28)
    
11. Bug default= not relative to document.
    ... so ".." ends up with /home or worse. (1999-09-23)
    
12. Check may need special handling for include in xcf files.
    ... in order to avoid initializing child resources before their parents. May actually need a dummy Subsite for this. (1999-09-22)
    -- so far it seems to be working, though. An alternative might be to invalidate caches where necessary.
13. Hole Need convention for accessing real, virtual, etc.
    Suggest pseudo-subdirs -r, -v, -d, etc. -pia, -usr for PIA_HOME, HOME. (Could also use r:, v:, d:, pia:, usr:.) Maybe -/r (1999-09-22)
    
14. Impr Want a way of getting at an overridden doc.
    Could maybe do this with a virtual container, e.g. -v/foo. (1999-09-09)
    
15. Bug Subsites don't get reconfigured when changed.
    subsiteCache is always used. If a config file is changed or a directory added to the virtual path, an existing Subsite won't notice. Minor problem, and very hard to fix without the ability to safely re-read config files. (1999-09-17)
    
16. Bug DOCUMENT must be parsed with correct tagset.
    (1999-09-16)
    
17. Bug Need "realizable" flag.
    Hard to tell which things are pure virtual, and which can be realized. (1999-09-16)
    
18. Impr Should have ImaginaryDoc
    parent of Listing; initialize with either config. or string. Having a parsedContent field in ConfiguredResource is silly. (1999-09-15)
    
19. Bug Need specialized Namespace for properties
    Needs to know where to save itself, and needs to be synchronized for sharing across threads. (1999-09-13)
    
20. Hole FileRoot needed
    We need something with a default configuration (for MIME types) and the ability to handle paths under a document root, in order to make it possible for TopProcessor to use resources everywhere. (1999-09-13)
    
21. Impr Listing should show virtual path
    and indicate which path element each document is in. The latter will probably require a getFlags method on Resource. (1999-09-09)
    
22. Impr All resources need config and property fields.
    This is most clearly seen in Listing. (1999-09-08)
    
23. Note W3C's RDF for config?
    Resource Description Framework appears to be an XML DTD for describing resources. The spec is here. It uses tagnames as property names, inside an <rdf:Description about="URI"> element. Namespaces are used to specify groups of properties (schemas). Properties can also be attributes if their values are strings. Containers use ref:Bag, rdf:Seq, and rdf:Alt elements, but Description elements don't nest inside them; they do nest in Description elements, which are virtual bags. (1999-09-07)
    
24. Impr use pure DOM nodes for config(?)
    There may be cases in which it's convenient to use a different representation for the configuration. Might actually be better to use an Output. (1999-09-07)
    
25. Hole Defaults in extension map
    
    • "/" for containers
    • "" for documents with no extension
    • "*" for documents with an unknown extension.
    (1999-09-07)
    
26. Hole Agent initialization
    Need a way to initialize agents. For now just keep the current scheme, with the Root (Admin?) agent loading a file. (1999-09-07)
    
27. Hole Links
    We need full support for links (i.e. references to FileResource's that are not realizable. (1999-09-07)
    
28. Note SiteMachine should allow header changes.
    Either by delaying headers until first non-blank content, or by recognizing an extension/tagset as capable of generating headers. (1999-09-03)
    
29. Bug Subsite.locateChild needs work
    Needs to have extension in inner loop, search path in outer. Currently it's the other way around because it's inherited from AbstractResource, which doesn't have a search path. (1999-09-03)
    
30. Impr Need a way to turn off caching in Subsite
    Do the basic lookup in ConfiguredResource, and use it if no location cache exists. Check a flag to see whether to build the cache. (1999-08-23)
    
31. Note alien resources.
    An ``alien'' resource is a link (alias) to something outside the site, with no real counterpart. An alien resource cannot be realized. Best represented by a FileResource. (1999-08-23)
    
32. Impr Generate metadata from extension
    The tagset stuff should eventually be considered a special case of mapping metadata from a file's extension. (1999-08-20)
    
33. Impr generate README on realize
    Note that when a container is realized, one typically wants to construct a README file pointing to its virtual source. This might actually be done using an agent! (Which implies that they're not just for the PIA, so a pia Agent might be an extension of a site Agent.) Sounds like we may want agents that ``listen'' for events on a Resource. (1999-08-20)
    
34. Impr tagset for directories.
    Generating the index for a container that doesn't have a home.xh document ought to be done by applying a tagset to the container's configuration element. We can use a pseudo-extension of ``/'' for this. (1999-08-20)
    
35. Hole utility to retrieve a processed document
    This would correspond to ``cat'' the way List corresponds to ``ls''. More generally, this should be able to realize and otherwise operate on documents as well. (1999-08-20)
    

Description of Keywords

Bug

A (typically small) problem with a simple, unambiguous description of its symptoms.

Hole

A piece of missing, but important, functionality.

Goal

A target capability (includes a date)

Check

Something to check for; a potential stumbling block or place where the implementor may have cut corners in the heat of the moment. For example, Y2K problems.

Improvement

A desirable improvement.

Proposal

A proposal that will need to be discussed further.

Wish

A desired improvement of low priority.