This isn't a conventional web site. We need a feature, maybe along the lines of moodle, so we can track areas and subjects that have been read on a scatter shot basis. The same system can bookmarked for highlights and used for both audit and educational purposes. Applies to both personal use by individuals, or by groups for things like certifications.
See comment below. Also:
- Site management and writing could use a "queue" - as specified in the BCC notes - that helps to manage loose book pages for weaving into books. Writing those pages is an "author" job. "Cataloging" those pages, weaving them into the "story" is an editorial job. This same type of task occurs for things like outside references. The web pages are filled with "links." to things. The links need semantic encoding applied and "cataloging" as AIR relationships. This is a "weaving" process that weaves elements like W3C specifications and Wikipedia articles as part of a "knowledge" set.
- This is why Wikipedia is an excellent and necessary open catalog of ideas, an online encyclopedia. But it operates at a different level and function than AIR or EATS. DBPedia comes closer. But still not there. Both are useful as components of the EATS knowledgebase, accessed "in place." We don't need to, or want to replicate. We just want to index, tag, classify, and "point" to their component elements.
- Brute force might do that as an incremental, "en masse" task. By scanning our content, identifying links without semantics, which happen to point to Wikipedia, putting them on a tickler, and then working that tickler, we get a much better quality of work accomplished, prioritized for the articles that matter to us. (Some day, if it matters, we'll catalog the whole thing.)