Person. This name immediately follows the keyword
I[Person], is the interface term of this service.
Person. In the screenshot, it applies to
<"J. Lovell", x>from the field term, the field displays the right atom
x. A field term always works on one specific atom on the left, which is
"J. Lovell"in this example.
"J. Lovell"has one personName (which is
"J. Lovell"), it has no personStatus, one personEmail and three persons to work with in
BOXwith a list of subservices. Without it, it is just a field term. 2. When a field term is followed by a
BOX, every atom in the codomain of the field term is displayed in a box of its own on the screen. That box behaves like a service with the field term serving as interface term of that subservice. 3. By this mechanism, the hierarchical structure of the entire service translates directly to the hierarchical structure of the web-page in which it is displayed. 4. The source concept of a field term must match with the target concept of the field term outside the box. 5. The target concept of a field term that has a box, must match with the source concepts of each field inside that box.
TABS, as in the following code fragment. Note that these annotation have no meaning other than to change what the user interface looks like.
BOX <TABS>turns the box into a layout with tabs. 2. The keyword
BOX <TABLE>turns the layout 90 degrees into columns. 3. The keyword
BOX <FORM>is default for any box. It does not change the effect of
ROWSdo to your display.