Nooron Software and knowledge evolving to meet human needs.
AnonymousUser ||
User: Pass:
|| join
you are here: http://www.nooron.org  / know / nooron_app_architecture __ kb.html

nooron_app_architecture

get_slot_value(here,:DOCUMENTATION)
This knowledgebase is the very heart of the Nooron App Architecture. This is the ontology which gives Nooron Apps (such as Pattern Language, FAQ, Web Log and PERT) their rich features. It establishes the slots for managing a hierarchy of skins. It defines different kinds of nooron_app_component: KBs which are either nooron_app_ontologies, nooron_app_wardrobes, nooron_app_data or nooron_app_instances which by being separate make possible a wildly flexible strategy of knowledge recombination. This approach will also support the automatic generation of management screens for adding, editing, versioning and deleting information.
get_kb_direct_parents:
PRIMORDIAL_KB, convenience_procedures, common_transformers,
get_kb_direct_children:
pattern_language_ontology, computing_systems_ontology, project_ontology, faq_ontology,
get_instance_types:
:KB, :THING,
get_kb_classes
frame :DOCUMENTATION
AbstractClass An abstract class is one which is never directly instantiated because its purpose is to be a superclass for other classes which may themselves be instantiated.
nooron_app_component Nooron app components are knowledgebases which have features which are made use of by code/NooronApp.py
nooron_app_ontology This is the ontology for a nooron app, equivalent to a relational database schema or to a set of class definitions for an object oriented system. Knowledge bases of this kind depend on nothing, except possibly other ontologies. It would, for example be fine to create a nooron_app_ontology which extended another.
nooron_app_data KBs of this kind contain 'INDIVIDUALs' which are instances of the CLASSes defined in some nooron_app_ontology. These KBs are equivalent to the records in a database (as opposed to the schema) or the objects in an object oriented system (as opposed to the class definitions themselves).
nooron_app_wardrobe A nooron_app_wardrobe associates a number of presentation resources such as templates with an ontology (specifically a nooron_app_ontology) so that all that is needed is some data to make a usable nooron app. An app skeleton is not itself a runnable app. It is a definition of the resources which when brought together with suitable data would be a runnable app. A wardrobe must know about the nooron_app_ontology (but not about any particular nooron_app_data). It must know about which presentation templates to use for the various classes specified in the nooron_app_ontology. It must know about whatever programming resources are required to make the app work.
nooron_app_instance A nooron_app_instance is an actual runnable app. It is the combination of two things: a nooron_app_wardrobe and some nooron_app_data. In fact, multiple nooron_app_wardrobe KBs and multiple nooron_app_data KBs can be the direct_parents of a nooron_app_instance KB. In this fashion, diverse (possibly distributed) ontologies and (possibly distributed) data can be brought together into a single Nooron application.
nooron_app_class Classes defined in nooron_app_ontology knowledge bases should be marked as instances of nooron_app_class. They then inherit facitilies for automatic display such as, initially, slot_display_order.
:THING  
:INDIVIDUAL  
:CLASS  
:KB  
:WORD :WORD is a :STRING which has no spaces.
:PHRASE :PHRASE is a :STRING which can be confined to an INPUT of type TEXT.
:PARAGRAPH :PARAGRAPH is a :STRING which could benefit from a TEXTAREA.
:HREF :HREF is a :WORD which may be a local, relative or absolute url.
:DOCUMENTATION  
Criterion A Criterion is a dimension along which opinions may be expressed. Those opinions are called Evaluations and may be supplied by either people or software agents.
CriterionRange A CriterionRange is a class whose instances are the values an evaluation might have.
Evaluation An evaluation is some Evaluator's answer to a question about some thing in some context. Where ActualEvaluation is the answer. WRTCriterion is the question. SubjectOfEValuation is the thing being evaluated. Evaluator is the agent who answered the question. EvaluationContext is the context of the evaluation. EvaluationVisibility indicates who can see it. EvaluationTimestamp is when the evaluation happened.
AggregationProcedure AggregationProcedures are OKBC Procedures which summarize the evaluations which are being heeded.
:PROCEDURE  
CriterionApplication A CriterionApplication specifies all that a WorldView needs to know about each Criterion it considers.
WorldView A WorldView is a list of CriterionApplication instances. In other words, it is a list of which criteria to consider in which order and whose evaluations to heed with respect to each.
StopWaitGo  
YesNoMaybe  
YesNo  
get_kb_slots
frame :DOMAIN :DOCUMENTATION
BookKeepingSlot [] Bookkeeping slots are those which are used for internal operations of the system and are not generally of interest to casual users. In particular they are not to be edited by other than extreme power users.
merges_in ['nooron_app_component'] Which nooron_app_components does this kind of nooron_app_component have as direct_parents?
npt_for_instances [':CLASS'] Nooron_app_wardrobes should have template_slots of this type on all classes which have specific nooron_page_templates for their instances. each class whose instances are supposed to be surfed. The associated resourceRef should contain the url of a Nooron Page Template (NPT) which is appropriate for displaying instances of the class on which ntp_for_instances is an occurrence.
actions_for_instances [':CLASS'] Nooron_app_wardrobes should have template_slots of this type on all classes which have specific nooron_page_templates for their instances.
actions_for_self [':CLASS'] Nooron_app_wardrobes should have template_slots of this type on all classes which have specific nooron_page_templates for their instances.