Presentation and localization
Presentation is the App-authoring projection of the full presentation and localization contract. Presentation metadata never changes the underlying typed wire value: the schema owns what the App accepts, sends, computes, protects or means, and the package's Display Template owns only how the same value is arranged and styled on a device. The rules are generated from that contract into four task cards; load the card for the task and read its linked owner before implementing.
| The task changes | Load |
|---|---|
A field's text, metadata, answer controls, Foldable, InlineChoices, SuppressLabel, UIIncludeDescription, media or Link rendering |
Presenting a field |
display.json: layouts, master-detail panes, labels and titles, page controls, promotion and flattening, conditions, hints and style |
Writing a Display Template, with its arrangement procedure and display presets |
Date and time types, Money, PhysicalUnit, Bitflags, Format, StringResources, FormattedText, translation |
Formatting values and text |
| Chart metadata and chart-producing requests | Declaring a chart, and Declaring a 3D chart for a 3D chart |
Complete applicable metadata proactively on every authored App — useful
initial task and server names, localized text defaults, value defaults, units,
bounds, inline help and grouping — and review those choices before delivery
without waiting for a separate user request. Each annotation must serve the
App's actual behavior; configuration-only examples need no invented protocol or
persistence. Check the annotation inventory before
adding source syntax, and follow the source documentation card
for the text every node carries. The schema-side placement and value rules
of these attributes (attr.*, format.*, numeric.*, bitflags.*) are on
the data model card.
How a chosen request is presented by its input, including the
hierarchical choice popup,
is on the actions card; the messages card
owns LMF1 templates and the FormattedText tuple. Rendering mechanics that only a client
implementer acts on are on the client runtime card.