History of KendraBaseProjectPlan|
KendraBase Project Plan |
|
Kendra Tools Project Plan |
|
Introduction |
|
Introduction |
|
Requirements |
|
Requirements |
|
* See also KendraBaseScenarios. |
|
Terminology |
|
Terminology |
|
Organisation |
|
Organisation |
|
Further Document Requirements |
|
Further Document Requirements |
|
* See KendraBaseProgress |
|
Users |
|
Users |
|
Tools |
|
Tools |
|
Trials |
|
Trials |
|
Concepts |
|
Concepts |
|
**The [Principle of least astonishment]? should apply as far as possible **Ditto [programming by example]? |
|
* Truth ** There is no absolute truth in this system only relative truth - "delayed opinion". ** When presenting data it will be cached somewhere. There should be metrics stating: *** When it was cached. *** When the original data was last updated prior to caching. *** How reliable the data is based on how often the data is updated. **** A person's name may be cached and not updated for a year but it is still has a high reliability since it's not likely to be changed. |
|
Features |
|
Features |
|
** Initial translations of website and forums can be done by machine to get content but then must enable users to suggest better translations. This is not about having different content/areas for different languages but about having trusted translations of entities/objects (words and text) so that everybody knows what everyone else is saying even if it's in a different language. It's about breaking down the barriers rather than building them up. |
|
** Initial translations of website and forums can be done by machine to get content but then must enable users to suggest better translations. |
|
** Every user will get a firstname.lastname@public.kendra.org.uk alias. ** Users can subscribe to other users to get every email sent by them or received by them. ** All email sent and received via Kendra aliases will be publically archived - though this is an optional feature for the system - promotes personal responsibility for what one says (?). ** Add/validate emails like Yahoo! and most other subscription services. ** Add multiple emails to system. *** Send all emails to me to this group of email addresses. *** Let me post using the following list of email addresses. ** DanielHarris wants: any email sent to daniel@kexxxxxxrg.uk to be publically archived. Senders to this email address get an auto-reply either "sorry this email doesn't exist, did you want one from this list..." or "your email is parked awaiting your authorisation/agreement to have it archived in public on the website. Click on one of the following: **** yes - link to web **** no - link to web **** yes - send email **** no - send email *** Users have to be registered to send to the private address of DanielHarris. And I reserve the right to make public anything you send to the private address. Do not send email you wish to be kept secret. *** When sending to someone@public.kendra.org.uk you'll get authorisation email saying you will continue to get this email until you set your preferences in your profile. |
|
** Every user will get a firstname.lastname@public.kendra.org.uk alias. Users can subscribe to other users to get every email sent by them or received by them. All email sent and received via Kendra aliases will be publically archived. |
|
* Tools interface ** Fully customisable! ;-) ** See KendraBaseMockups for ideas on how users rate or comment on text or whole pages. * Auto-input ** There are many existing database and flat file Internet resources. These resources are updated by their owners sometimes. When adding or updating data from these resources into KendraBase we need to do this via automation that will check for updates and modifications and mark them as such. * Query Builder ** Make a really nice way for people to make queries to the system with drop down menus. See KendraBaseQueryBuilder. * Data Pivoting Everywhere * Drafts ** Authors must be able to store drafts of their content. In a sense that's just another type of permissions setting where one can define the audience and availability of the content. * Permissions: ** Basic: *** Can be viewed by everyone *** Can only be viewed by the author ** Then: *** There's a difference between an item being not viewable by public and not even appearing to exist. The question is whether it gets counted in a search results or not. So, that's an extra level of privacy. *** Complex permissions by building up rules much like KendraBaseQueryBuilder. So, things like: **** Can only be seen by my group "Friends" or "Family". **** On a Tuesday. **** By people in China. **** Licensed under the GPL or BSD or whatever. **** Give me 5 quid first. ** Pervasive Hierarchical Permissions *** At the top of the user stack we have the owner or system administrator of the KendraBase. They set up users and groups and define capabilities and ranges/restriction. These users in turn can then define capabilities and ranges/restriction for users below them. Kind of like reselling... Technology |
|
Technology |
|
*** Take a look at OneClickWatchMe which I think could do some of the job quite easily. |
|
* Resource discovery ** How will each KendraBase host/server know how to find other siblings? There are lots of ways of doing this and we should be able to use them all! Perhaps to start off with we could just have a simple lookup table replicated within each KendraBase server. Other ways could be more like peer to peer networks but this takes out direct connection between servers but probably need to do this if KendraBase is to scale. Keep options open. Start simple. |
|
Ideas |
|
Ideas |
|
Reference websites |
|
Reference websites: |
|
* http://ontology.teknowledge.com/ |
|
* http://esw.w3.org/topic/OwlAndRdf |
|
Possible targets for trialing Address Book: |
|
Targets for trialing KendraBase * Http://www.kendra.org.uk - of course! |
|
* http://www.planet-lab.org/php/overview.php |
|
* http://www.freewheelers.co.uk/ with around 4000 people could be good live test bed. Possible targets for trialing KendraBase * http://www.planet-lab.org/php/overview.php See also |
|
* http://www.freewheelers.co.uk/ with around 4000 people could be good test bed. See also: |
|
* Human readable semantic languages * is a and has a * KendraBase design and implementation notes Database ideas * [Beyond Relational Databases] |