Edit detail for KeyConcepts revision 1 of 1

changed:
-
<table>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Agent"></a>AgenT</td>
<td width=270>
 A program that performs information gathering or tasks in the background. Typically, an agent is given a very small and well-defined task.  In computer science, there is a school of thought that believes that the human mind essentially consists of thousands or millions of agents all working in parallel. To produce real artificial intelligence, this school holds, we should build computer systems that also contain many agents and systems for arbitrating among the agents' competing results.
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Allele"></a>Allele</td>
<td width=270>
 A gene is a string of alleles. In simpler terms an allele's position in gene represents a property or function of its carrier and the value of the allele modifies the property in question.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Attribute"></a>Attribute</td>
<td width=270>
properties manifest themselves through attributes and functions.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Avatar"></a>AvataR</td>
<td width=270>
 A visual representation of an agent. Agent's 'virtual clothing'. A collection of properties that make up the visual reprentation of an agent. 
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Bluetooth"></a>BlueTooth</td>
<td width=270>
 A wireless close range (10 m) network. A specific support station is needed.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="CrossOver"></a>CrossOver</td>
<td width=270>
Crossover happens when two strands of dna first align themselves and cross each other. The strands break at crossover point and finally reassemble to form a new pair of aligned dna strands. In this context, crossover is the act of rearranging agents' properties.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="DesktopClient"></a>DesktopClient</td>
<td width=270>
 The program module for accessing Kyperia from a desktop computer.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Gaming"></a>Gaming, Gameplaying</td>
<td width=270>
.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="GenomE"></a>GenomE</td>
<td width=270>
The collection of genes that represent an individual and his properties is called genome. Here we are naturally referring to agents and data structures representing their attributes and/or contents.  
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="InstallatioN"></a>InstallatioN</td>
<td width=270>
Installation is the general term for the collection of equipment, software etc. and their arrangement for a public set-up. Oftentimes is used to refer to a particular set-up.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="InstallationRenderer"></a>InstallationRenderer</td>
<td width=270>
 At the installation site, a computer with the best affordable graphics and audio cards feeds the display and sound devices. It can use the same client that remote participants, but has special camera controls/presets designed for the public display where several participants must see their avatars. A more advanced installation can be built using several displays. There may be several installation sites using the same server (or later perhaps the network of them).
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="InstallationServer"></a>InstallationServer</td>
<td width=270>
 ServeR, InstallationRenderer and InstallationNetwork are needed for a KyperiA installation
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Kyperia"></a>Kyperia</td>
<td width=270>
Our world of worlds. A virtual reality for multi-player gameplaying and immersive participation. The eternity project of Kyperjokki.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="MatinG"></a>MatinG</td>
<td width=270>
The reproduction of BeinG s, produces OffSpring that can become new AvataR s. 
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="MobileClient"></a>MobileClient</td>
<td width=270>
 First a simple RemoteControl, used in combination with PublicDisplay.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Mode"></a>Mode</td>
<td width=270>
 .
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="OffSpring"></a>OffSpring</td>
<td width=270>
 The children of the parents that agreed to mate. In case of Avatars, which participants use, gives new time.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="OpenSource"></a>Open Source</td>
<td width=270>
 .
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="P2P"></a>Peer-to-Peer, P2P</td>
<td width=270>
 .
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="PhenomE"></a>PhenomE</td>
<td width=270>
 .
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="PlacE"></a>PlacE</td>
<td width=270>
Agents exist only in some place. A place is a displayable unit of a world, not all places are displayed - however.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="ProP"></a>ProP</td>
<td width=270>
 The purpose of prop is to generate atmosphere and landmark a place.  Props are not directly handled by agents, although the system may move them and change their properties. Props have physical attributes such as size, texture, opacity, hardness, weight, density, reflectivity, etc.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="Property"></a>Property</td>
<td width=270>
 is a conceptualization of an attribute. Mating mixes portions of partners' properties.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="SeasoN"></a>SeasoN</td>
<td width=270>
Like the world itself worlds in Kyperia are enlivened by seasonal change.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="ServeR"></a>ServeR</td>
<td width=270>
 Runs the system, i.e. manages the WorlD s and provides all data to the clients that participants use.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="SitE"></a>SitE</td>
<td width=270>
 site, on-site refers to the actual installation location with all its limitations and possibilities.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="SoundScape"></a>SoundScape</td>
<td width=270>
Places are have related soundscapes to convey atmophere, to create dramatic effects and to enhance immersion.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="TooL"></a>TooL</td>
<td width=270>
Tools are passive elements like props that populate places. In addition to properties of props they have properties and functions but to function they need a user, an operating agent or the system.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="TransitionEffect"></a>TransitionEffect</td>
<td width=270>
When a world ends and another starts they are joined by a transition effect. Their purpose is to let viewers anticipate and adapt to the change. E.g. imagine a thunderstorm slowly rising and coming on from the horizon bringing about the new world.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="VieweR"></a>VieweR</td>
<td width=270>
 by viewer usually we refer to the installation audience members. Sometimes the desktop client user is referred to as the viewer. This should be obvious from the context.
</td>
</tr>

<tr>
<td width=30><br> </td>
<td valign=top width=150>
<a name="WorlD"></a>WorlD</td>
<td width=270>
Contains things, active and passive. In this case: AgenT s, PlacE s, TooL s and ProP s. Knows about it's StatE (e.g. SeasoN)
</td>
</tr>


</table>