Redfoot: Roadmap

Roadmap ( Page )

Near Term

Tutorials and documentation!
New/improved editor javascript etc.

On Deck

Scutter
Remove requirement that aspects be loaded with a base of exactly the site URIRef.
get rid of the static hypercode being served up via mod_rewrite, and add some filesystem syncing ala StaticPage for the rest of the hypercode bits to enable easy editing, and an automatic sync mech.
Add hook between kernel and store
need to beef up the kernel to support who can get at what data... at the moment there's controls for who can see what page... but all the rdf/xml is still available to everyone. A way to attach restrictions context by context in addition to page (or page part) should go a long way.
Add virtual contexts for assertion in there natural context -- assert triples to their natural context on add... and on a remove of a triple on a specified context delete the triple from its natural context if it's the only one left.
Redfeet usecases (to help drive rdflib journaling support).
Map out the hosting options and requirements.
Another pass through Common HTTP Implementation Problems, a first pass through it has been done.

Long Term / Research

Research XUL. See XULPlanet. Also XULRunner, PyXPCOM, Luxor-xul, Python for XUL scripting, Giving Python legs with XULRunner

Redfoot's Developmental Direction

As Redfoot evolves into a feature-rich webised operating system, users might be particularly interested in the effects of the complex interactions between different Redfoot servers before full deployment. For example, due to the light-weight and device independent design of Redfoot, Redfoot can be deployed onto mobile and location sensitive devices such as Cell Phones, PDAs, even RFID-aware computing systems. This will further realize the vision of the RDF/Semantic Web being an overarching framework that blends the reality between networked documents and physical resources. As the RDF-based Redfoot introduces itself with our physical realm, the ability to ensure system security and health would become necessary. Therefore, devising new ways to test and verify the safety and liveness properties of a collection of Redfoot servers is highly desirable. The distributed and asynchronous nature of multiple servers requires a different set of software development tools that are used for developing AJAX or traditional server/client software applications. The ability to automatically compose and test multiple interactive processes across different networked machines becomes a key issue. Moreover, since Redfoot and Hypercode is intended to be modifiable by a wide range of users, providing verification and testing features to average web users is also a practical challenge. Therefore, modern model visualization, generation and verification tools might be necessary enabling features to make Redfoot popular.

Links

TODO: move these to bookmarks?

Redfoot