The interface repository is simply a mapping between a symbolic name and a public interface associated with which is some well-defined behavior.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• Interface Repository reduces coupling between applications and between applications and framework.claim0.815
• Interface Repositoryconcept0.813
  Facility that maps symbolic names to public interfaces, enabling dynamic functionality extension without modifying the backplane.
• INTERFACE REPOSITORY (4)framework0.801
• The interface repository allows functionality to be added without directly altering the backplane.claim0.796
  Claim that the interface repository provides a non-invasive extension mechanism.
• Create an interface repository for the system and let the backplane serve as the central access point to this list of publicly accessible interfaces which is indexed by a unique name.claim0.780
  Prescriptive claim for the INTERFACE REPOSITORY pattern.
• Make the components with which the user interacts standard applications which provide standard facilities and interfaces. These applications have a standard interface by which the backplane can manage their lifecycle methods. These applications can be dynamically loaded to help reduce the overall footprint of the system. Avoid having applications communicate directly with one another – use the interface repository for this purpose.claim0.759
  Prescriptive claim for the STANDARD APPLICATIONS pattern.
• Create a backplane component in the system. This component should be primarily concerned with providing facilities which address the runtime architecture of the system. These include initialization and termination of applications and high level window management. The backplane is also an ideal place to put the interface repository. Avoid placing application or domain-specific functionality into the backplane and instead use an interface repository to support this activity.claim0.737
  Prescriptive claim for the BACKPLANE pattern's responsibilities and boundaries.
• Good interface design reveals the underlying computational architecture to the user.claim0.732
  Core interpretive claim about the relationship between transparency and usability.