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,
communities_ontology,
project_ontology,
pert_ontology,
web_log_ontology,
computing_systems_ontology,
faq_ontology,
spangler_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. |
| 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. |
| PromptForDataEntry |
[':SLOT'] |
This is a slot on slots which contains
a text prompt which can be presented to users to help
them to understand the kind of value they should enter
into the slot.
|
| CriterionAnswersAre |
['Criterion'] |
This is the slot on criterion which specifies the range
of evaluations with respect to the criterion. The values on this
slot may be of the following forms: 1) a :CLASS which specifies
the possible values e.g. :INTEGER or :STRING
2) the CriterionRange which specifies the possible values.
A CriterionAnswersAre of :STRING means that the Criterion is
in effect a fill-in-the-blank question. A CriterionAnswersAre
of, for example, :INTEGER means that the Criterion is asking
for an integer to be supplied. A CriterionAnswersAre of
|
| DomainOfCriterion |
['Criterion'] |
This is the slot on criterion which specifies the domain
of the criterion, in other words the classes of things which
the criterion may be applied to. If the value of this slot is
empty, then the criterion may be applied to anything. Further
analysis is required to determine how the distinction
could/should be recorded between
criteria-used-to-evaluate-candidates versus
criteria-used-to-evaluate-versions. Another issue is this
whole matter of whether the DomainOfCriterion should be
recorded at all, or whether this is a matter which can be left
to self-organize by noting how criteria are used.
|
| PertinentCriteria |
[':THING'] |
The PertinentCriteria for a class are those which
have that class as a value on their DomainOfCriterion slot. |
| QuestionCriterionAsks |
['Criterion'] |
This is the slot on criterion which has as its value
the question which is asked of people when evaluating something
with respect to the criterion. |
| WRTCriterion |
['Evaluation'] |
This slot on Evaluation contains the criterion
which the evaluation was performed with respect to. |
| SubjectOfEvaluation |
['Evaluation'] |
This slot on Evaluation contains the thing being
evaluated. Notice that a simple frame name is just a
degenerate form of a URL. |
| ActualEvaluation |
['Evaluation'] |
This slot on Evaluation contains the specific
value which is the Evaluator's response to the question
contained in the criterion. |
| EvaluationContext |
['Evaluation'] |
This slot on Evaluation indicates the context
in which the evaluation was performed, for example,
in relation to other members of the same class in
some KB, or in relation to other versions of the same
thing. Maybe there should really be two slots, one for
the URL which defines the context and the other a value
which is either CANDIDATE or VERSION. |
| Evaluator |
['Evaluation'] |
This slot on Evaluation indicates the person
or software agent who performed the evaluation. |
| HasVisibility |
['Evaluation'] |
This slot on Evaluation indicates who can
see the evaluation: only the Agent, or some broader
set of Agents. EvaluationVisibility is hence a class
of such visibility specifications. |
| WhoToHeed |
['CriterionApplication'] |
This slot on CriterionApplication indicates whose
evaluations to consider. Hence its list of values
contains either individual evaluators or classes of same.
The :SLOT-COLLECTION-TYPE is list because some
AggregationFunctions may consider the order to confer
precedence. |
| ConsiderCriterion |
['CriterionApplication'] |
This slot on CriterionApplication indicates
which criterion is being considered. |
| AggregateUsing |
['CriterionApplication'] |
This slot on CriterionApplication indicates
which OKBC procedure to use to summarize the evaluations
being heeded. |
$Id: kb.html,v 1.4 2003/07/09 16:35:13 smurp Exp $
Show Source
|
available garments:
:KB
entity_relationship:
dot ps jpg svg gif pdf
classes_in_kb:
dot ps jpg svg gif pdf
class_hierarchy:
dot ps jpg svg gif pdf
kb_ancestry:
dot ps jpg svg gif pdf
kb:
html
:THING
frame:
html
frame_details:
html
available actions:
put_frame_details.html
|
