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
Does an address tell you what you can do?
Location, supported operations and caller authority are separate questions.
Seeing a report does not imply permission to edit it. Writing its title does not imply that every display receives spontaneous updates. An address identifies the operation target; a capability declaration describes supported operations and additional conditions.
Imagine two Providers behind a report entry:
| Implementation | Read | Modify | Push changes spontaneously |
|---|---|---|---|
| Static archive | Supported | Unsupported | Not promised |
| Editable report service | Supported | Subject to service rules | Check subscription and live capabilities |
This is a teaching example, not a product capability test.
Ask three separate questions: can the implementation perform the operation, does this mount allow it, and may this caller invoke it? A Provider that implements writes may be mounted read-only. A writable environment can still reject a participant under business rules.
AFS resource capabilities also differ from AUP device capabilities. The former concern operations such as reading, writing and subscribing. The latter concern a device’s ability to present and handle interface types. Rendering a chart does not make its results writable.
Go deeper
Check your understanding
Does Provider write support authorize everyone who sees the resource to edit it?
No. Mount restrictions, caller authority and business rules still apply.