The design of Reptile includes a small but powerful feature set. This page
provides a brief overview of these features and their current development
status. Bugzilla and the mailing lists are used to discuss details and
specific implementation issues.
Feature |
Status |
Ability to plugin new content as XML and render a UI via XSLT based on
content type/namespace.
|
DONE |
Ability to layout pages with multiple columns with content rendered within each
channel as a control.
|
DONE |
Need a reptile "uplevel" content syndication format. This should
basically be like RSS on steroids. RSS 1.0 doesn't provide the rich
functionality that is needed for Reptile. A good example is an image
for each channel.
|
DONE |
Multiple pass content rendering. This is necessary so that we can
support multiple content feeds, multiple user interfaces, multiple
content types, and reputation all driven via XML and XSLT.
|
DONE |
Ability to mark channels as "read" so that only new (unread) URLs are
shown as content is updated in the background.
|
DONE |
Ability to group content feeds into multiple "layers" so that we don't
have to have 100 channels on one page.
|
DONE |
Support all RSS formats including RSS 0.90, 0.91 and 1.0.
|
DONE |
Supports OCS content feeds.
|
DONE |
Should support fully disconnected operation and not have any reliance on
a persistent Internet connection for its operation.
|
DONE |
Ability to add services or features markup which we could use to offload
to external service provider. An example would be using a micropayment
service, an external/remote reputation service, or a language
translation service like babelfish.
|
DONE |
Meerkat style functionality: http://www.oreillynet.com/meerkat/
|
DONE |
Need to be able to create personal RSS channels and then publish them
via a users personal OCS file. This should support quickly publishing a
new URL, adding a description and inserting a time stamp. Users should
also be able to delete/update existing entries.
|
UNDER DEVELOPMENT |
Integration with the Sierra Reputation Management Framework (RMF) so
that all resources can have reputation.
|
UNDER DEVELOPMENT [2] |
Ability to keep "buddy" lists to that you can jump directly to that
users "home page". This way I could have a "Fellow Reptiles" list with
an entry of "Fen" and then view his syndicated content.
|
PENDING |
Reptile should support the act of running as a web server and not JUST a
P2P client. IE I should be able to have someone visit my Reptile system
via the Internet like slashdot.org, etc.
|
PENDING |
Integration with P2P networks (Freenet, Jxta) so that Reptile users can
have a mechanism to contact each other and exchange reputation
information and syndicated content.
|
PENDING |
Public Key authentication based on Nyms. This provides Reptile with a
fully distributed authentication model which can preserve privacy (if
used correctly).
|
PENDING |
We need to be able to 'plugin' the different type of reputation metrics
so that when we want to change them this doesn't involve rewriting
Reptile or Sierra. This should be a simple mechanism where we point
Reptile (via its properties file) to an XML metric-value configuration
file. This should contain a set of human values and their computer
readable form.
|
PENDING |
All users should have a 'channels.xml' file which contains the list of
channels that user publishes. This is used so that Reptile load a users
channels.xml and then offer a list of channels that user publishes.
|
PENDING |