You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
Which primitives does AUP define?
Eighteen core types provide an entry into the interface vocabulary.
A primitive is a basic interface type recognized by the protocol. Learn responsibilities first: containers organize content, text expresses words, inputs receive values and actions trigger operations.
The reviewed AUP_PRIMITIVES list has 18 entries. These teaching groups do not add source-level classifications.
| Learning purpose | Core types |
|---|---|
| Organization and expression | view, text, media |
| Input and action | input, action, overlay |
| Data and time | table, time, chart, map, calendar |
| Conversation and editing | chat, rtc, editor, canvas |
| Resources and embedding | explorer, surface, afs-list |
Each type has its own linked node. The registry still describes rtc as a reserved placeholder; inclusion is not evidence of working calls. Check chat against a concrete session target; a document is not a chat application.
This vocabulary describes what an interface expresses. Which browser library draws it, which site component composes it, and which display supports its interactions are implementation questions.
Continue to Web Device components for the article-header example that separates protocol types from site components.
Further reading
Technical documentation: read the full reference.
Check your understanding
Why study capabilities alongside primitives?
The vocabulary says which types can be expressed; capabilities say what a particular target supports.
Continue along a learning path
- From protocol to siteStep 7 of 9