I try to describe here what the user (= owner–operator) of
a personal computer needs to understand in order to gain the benefits provided
by a capability design via a particular hypothetical GUI.
I try to avoid jargon.
This reveals concepts that the user needs whether he gains them by reading,
or osmosis.
This addresses design issues similar to these architectural
notes.
Earlier thoughts on this subject.
When you click on a guest icon in a web page you are inviting an
agent to come to your computer and reside therein.
The guest will be at your mercy, however, for you set the terms for
his transactions with others.
You are the landlord and the guest is a tenant.
A guest has no lease unless you negotiate that by other means.
The menu item guests shows you the list of current guests.
Clicking on one brings up your control point for that guest.
Here are the elements of a control point (red
elements are directly adjustable here):
- Name that the guest prefers, which may not be unique among your guests
- URL via which the guest arrived
- Phoneticized hash of delivery package
- List of digitally signed recommendations
for this guest
- Resources:
- Space:
- How much space is he using just now?
- How much space do I authorize him to use?
- Time:
- How much time has he used in the last minute, hour, day, month, year?
- What fraction of my machine do I authorize him to use?
- Screen Space:
- Do I allow the guest to acquire screen space without invitation?
- Which screen space does guest now control?
(Click here and the space will blink.)
- Constituency: which other guests rely on this guest?
- Invite guest to open dialog window now.
xx