...
- Map directory names and file names directly to an underlying (specified) file system.
- Save properties in a file called file-name.properties, where file name corresponds to the base file name.
- Save attachement references in a file called file-name.attachments.
Identifiers
Content resources are identified by a file name. In most cases, this name will have a file extention separated by a period, from which the MIME type may be deduced (via an extention map). All files also have a metadata file associated with it named the same, with a file extension of .properties. These properties may optionally be cached in a database to allow faster access to them.
Resources may have attachements - TBD.
All resources (and attachments) live in a collection. Resource identifiers must be unique within the collection they live in. Collections may contain sub-collections. Collections are simply named and correspond to directories in a file system. Collection names must be unique within the collection they live in.
Collection paths are defined against a local root. This root is associated with a context (usually a site). Local roots branch from a Sakai global root, which in turn is mapped to a file system location.
Issues
- Properties can only store string-based properties.
...