http://www.nooron.org/know/nooron_project This is the Project Management knowledge base for Nooron.

These are the different types of agents (actors) for whom use cases may be written. Generally, these specific types will be defined as part of a particular software project.

These are the activities which people (or other actors) need to perform.

BrowsingUser

BrowsingUser

BrowsingUser

EvaluatingUser

EvaluatingUser

EvaluatingUser

EvaluatingUser

EvaluatingUser

EditingUser

Create an instance of class EmailMessage in your Outbox knowledgebase and that triggers the sending of it.

These are the various states which a Task may be in.

Tasks are the activities to be performed to complete the project.

Permit writing only when the user is visiting from some fixed IP address list, or when they have entered one of a list of userids.

3

Nooron_0_2_1

future

Devise a system of request parameter hashing so that output is only regenerated when needed and that intermediate forms as well as encodings of them are appropriately cached and delivered. For example, nooron_pattern_language.dot would be cached as would nooron_pattern_language.dot.pdf. The .dot would be regenerated only when the knowledge or template changed. The .pdf would only be regenerated from cached .dot when the .dot changed. A system of hashes based on canonical forms of the requests with knowledge, template and preferences mixed in ought to do it.

8

EncodingPipelines

complete

Put wrapper functions around all kb read operations which cache the output keyed on the paremeters.

3

Nooron_0_2_1

complete

Create a Central Registry of Nooron Apps where the apps themselves exist remotely.

3

ThroughTheWebEditing NooronAppRegistry RemotelyInheritNooronApps

future

Combine Criteria and Evaluations with the App Registry so that Nooron Apps can undergo collaborative filtering and collaborative amelioration.

6

ImprovingContent CentralAppRegistry

future

When adding frames which are instances of a nooron_app_class, those instances should be created in the appropriate nooron_app_data kb.

3

Nooron_0_2_1

complete

Criteria and Evaluations

24

FormActions CriteriaAndEvaluationsOntology

future

Create initial ontology for Criteria and Evaluations.

24

Nooron_0_2_1

future

http://www.nooron.org/know/nooron_pattern_language/CriteriaAndEvaluations

Delete items in the disk cache when they are stale.

3

CachedOutput

future

Combine Criteria and Evaluations with the App Registry so that Nooron Apps can undergo collaborative filtering and collaborative amelioration.

6

FilteredKnowledgeAcquisition

future

Create distributed system for using collaborative filtration to discover evolving apps.

6

CentralRegistryOfEvolvingApps

future

Connive to insert images into docbook output, URLs for the remote renderings and cached files for the local renderings (such as PS and PDF). This is the tricky part, refactoring the code so that the name of the appropriate cached version of the image is emitted in the docbook output. This is starting to strain [indeed!] the whole business about the cached files having those silly MD5 names. Maybe its time to make the cached file names exactly match the paths in the URLs which invoke them.

4

CachedOutput

future

Deliver a pykb export of somekb at the URL /know/some_kb.pykb Make raw knowledge surfable. Support backup, export, mirroring, interoperation and distributedness.

2

Nooron_0_2_1

future

Ensure that sequences of extensions (e.g. tar.gz, .dot.svg, or .dbk.pdf) properly transform the output. All relationships between content-types and their legal encodings to be managed as knowledge.

6

Nooron_0_2_1

complete

Acquire knowledge from multiple instances of the same Nooron App.

6

EvolvingAppRegistry

future

Attach appropriate constraint slots on the slots in the PRIMORDIAL_KB.

2

Nooron_0_2_1

future

Write create_individual and create_class npts which are limited by authorization stubs. method:add_slot_value

2

FormGeneration AuthorizationStubbedIn OkbcConstraints

complete

Create very simple forms automatically by using widgets based on slot type.

5

FleshOutPrimordialSlots

complete

D'oh. ZPTs don't seem to be recursive. Quintuple blast! Either develop workarounds, query Guido on the nature of the fix, dive in and do it or rethink ZPTs. Workarounds might include iterative approaches to some things, or leaning on OKBC Procedures for some formatting work. Sigh. The longterm goal is certainly to have the Garment mechanism capable of recursion though, so a fundamental solution is preferred.

4

EncodingPipelines

future

Put pictures (.jpg,.svg) from graphviz in html.

2

CachedOutput

complete

Create forms to support project management and pattern language maintenance.

6

FormActions

future

Use Criteria and Evaluations to improve knowledge (including frames and garments)

6

CriteriaAndEvaluations

future

Create a chainable security engine (compatible with IPListSecurityEngine) which permits per-kb-type, per-KB, per-Class, per-Slot, per-Facet and per-Individual security controls. The security engine would be more robust if included in PyOKBC (rather than tacked on at the Nooron level) but this is unclear. This is a large task and perhaps ought to be broken up into smaller bites. The first priority is to ensure that transformers can't be hijacked to perform arbitrary operations on disk. The second priority is to ensure that arbitrary read and write operations can't be performed under the aegis of KB reading and writing.

20

UserBasedAuthorization

future

Ensure that NPTs can live in subdirectories of /know (such as /know/pert) and be accessed appropriately.

4

Nooron_0_2_1

future

Create KB containing information about Nooron Apps.

2

NPTsInSubdirs

future

This is a dummy START job marking the state which was current when nooron_pert was begun.

0

complete

Users enter an url (root-relative or absolute with fqdn) as their userid and a password which when crypted must equal a crypted value in the NSBA-KB at the url.

6

Nooron_0_2_1

future

http://www.nooron.org/know/nooron_pattern_language/NotSoBasicAuthentication

Create very simple forms automatically by using widgets based on slot type.

5

FleshOutPrimordialSlots

future

2

DocBookWithPictures

future

Implement Tom Munnecke's xmlrpc code for authenticating against Friendly Favors as the first Pluggable Authenticator for Nooron.

3

PortToPython22 UserBasedAuthorization

future

http://www.favors.org

Figure out what the heck is interferring with PyOKBC running on Python 2.2 and then fix it.

4

Nooron_0_2_1

future

Ensure that save_kb is working for PyKb.

3

Nooron_0_2_1

complete

Fix bugs in get_slot_values, etc..

3

Nooron_0_2_1

complete

Make it possible for someone to create a nooron_app_instance which points to a nooron_app_wardrobe which actually lives on a different machine, and have it all work.

8

SubdirsAsKBs DownloadableKBFiles TellKb

future

Solve the 'starting on port 80' problem.

2

Nooron_0_2_1

complete

Decide which KBs to keep in the distribution. Will simply adjusting the location of /know in the startup script suffice? Create backup mechanisms for the newly independent /know directory. Possibly setup CVS management of the KBs. Examine the distinction between ontologies, wardrobes and app_instances. Is there more factoring which should happen at this time? Perhaps separate the app cores from the app instances. This leads into the remote inheritance issue and the nooron/noosphere distinction.

4

ThroughTheWebEditing

future

Make subdirectories of /know, (e.g. /know/pert) themselves be KBs. They need to be surfable and representable as .tell or .pykb, ultimately.

3

Nooron_0_2_1

future

Get TellKb working correctly for reading and saving.

3

Nooron_0_2_1

future

Make it possible to at least add and edit frames.

3

PyKb_save_kb HighPriorityForms CreateInNooronData RunOnPort80 PyOkbcCorrectness

future

Permit read, write, modify and other registerable capabilities based on the who the user has authenticated themselves as. Seriously examine capabilities as implemented in E before tackling this task.

50

NotSoBasicAuthentication AuthorizationStubbedIn

future

http://www.erights.org

Defer to a user's preferences in their NSBA-KB for things such as the garment to default to for instances of each class. Maybe when authenticated users surf a nooron site, when they visit a kb, it should be with their NSBA-KB as a parent, to avoid complicated look-aside.

4

NotSoBasicAuthentication

future

Expose the create_kb method.

2

KnowledgeDrivenSecurity

future

http://www.ai.sri.com/~okbc/spec/okbc2/okbc2.html