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,

get_instance_types:: :KB, :THING,

**get_kb_classes**
frame	:DOCUMENTATION
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 data structure declarations 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	docs for :THING
:CLASS	docs for :CLASS
:KB	docs for :KB

**get_kb_slots**
frame	:DOMAIN	:DOCUMENTATION
merges_in	['nooron_app_component']	Which nooron_app_components does this kind of nooron_app_component have as direct_parents?
npt_for_instances	[]	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.
npt_for_self	[]	Nooron_app_wardrobes should have npt_for_self template_slots on all classes which have specific nooron_page_templates for their instances.
slot_display_order	[]	A list of the slots to display, in the order they should be displayed. This is respected by the template frame_as_html but not required by it. In other words, slot_display_order is optional on any nooron_app_class.

$Id: kb_as_html,v 1.9 2002/11/22 21:37:03 smurp Exp $