Skip to main content
Knowledge mapDoes every path address the same kind of thing?ArcBlock

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS and interfaces

One question

Does every path address the same kind of thing?

Compare scope, resolution and available operations.

Two systems can both write /tasks/talk/title without giving that address the same contract.

In a UI data model, it might locate a title field in a JSON object. A2UI uses JSON Pointer paths for component data bindings. A2UI data binding

In AFS, understand an address together with its namespace, provider and supported operations. It can connect to files, service resources or interface structures; its meaning and writability depend on the environment and authorization. See paths and operations.

Ask four questions: where is the address interpreted, who resolves it, which operations exist, and who can execute them? Similar slashes do not settle those questions.

HTML element IDs, test selectors and AUP node IDs also aid location without automatically becoming equivalent business-resource addresses.

Check your understanding

After noticing that two systems have paths, what should you ask?

Ask about namespace, resolver, operations and authorization rather than inferring identical contracts from similar strings.

Continue along a learning path