A common way of building services endpoints is about http://. Here the content is adressed by its location, because the next part after the schema is the network location e.g. localhost (IETF RFC 1808). Alternativelly content based adressing will always return the “same” content regardless whjere the content is retrieved from, who offers the content or when the content is added content based adresses can be seen as permalinks. Why is this important for automotive related Software Defined Architecture (SDA)? It allows to keep the (virtual) interfaces for the northbound consumers as stable and semantically rich as possible. Consider e.g. the GENIVI/W3C Common Vehilce Interface (CVI) with a Vehicle Signal Specification (VSS) location: /vehicle/speed. Independed which source, in the SDA sothbound, provides the specific value instance e.g. a CAN signal or a AUTOSAR Adaptive service instance, it can be always found at this location as a persistent data structure (also compare https://en.wikipedia.org/wiki/Persistent_data_structure).
Content based adressing redically increases the durability, because multiple entities can take care about. Multiple consumer and producer sahre access on the content. As long as at least one is providing the content, all consumer could be served. If also the lst producer is unavailable it can come back at a later time, it is hard to attack but easy to recover – an emergent information flow, often descrived by the term “decoupling”.