UNDER THE HOOD
Interoperability
Local models, morphing along a path, and an empty endpoint that can receive a program first.
The Semantic Web has a working habit: when you link to a source, you turn that source to fit your local model. When someone later links to you, they do the same. If every service keeps that habit, the whole remains livable.
MAD uses that habit on a live path, not only on stored documents.
Fit the local model
To link a source and morph it so it fits the local data model is called . The receiving service keeps its own shape. The source does not have to change.
If the service then offers to change the data after the local model has been updated, that is a . The change stays in local context. Other nodes do not see how it was done.
The on a link is the verb in that fit. The logic belongs to the service that defined it. Domain owners keep that logic intact even as others link in. End users keep control of whether the source is available at all.
An empty endpoint can start
For endpoints and their ghosts, the source describes a further step. lets the endpoint receive a self-contained message before the data stream. The application-layer owner can send a program first. The data-layer stream follows. The client can build its interface without a preinstalled application.
The endpoint can therefore be distributed as an empty container. Program and data arrive later. Ownership of the ghost decides which layer may be configured at runtime.
This is also how the architecture talks about objects that have almost no stack of their own. If they can keep a connection alive and be identified, they can receive intelligence from a service. The limit is still the body of the object.
Protocol independence
RTW is protocol independent. The service owner decides their own protocol. Information about how data is structured lives on each . An implementation may support more than one encoding and change format at runtime when a client with domain ownership requests it.
This site will not publish those encodings. If a service does not describe itself, others have no serious basis for linking to it.
What interoperability is not
It is not one global data model that everyone must adopt. It is not a central API. It is the rule that each service keeps its own shape, and that a live source is morphed into that shape along the path.