一句话：通过扩展 OpenAPI 在模型中嵌入实现细节，实现 Web 服务自顶向下、模型与实现保持一致的开发流程。
Web 服务常需被其他程序调用，因此良好的开发者文档与模型至关重要。OpenAPI 作为业界标准支持自顶向下的迭代式开发：先构建描述目标服务的模型，再实现服务及其消费程序。然而在快速原型场景中，开发者往往跳过设计阶段直接实现服务，或在产品发布后停止更新 OpenAPI 模型，导致无法享受模型与实现一致带来的好处。本文提出对 OpenAPI 进行扩展，将实现细节直接加入模型中，把服务与描述计算的组件装配体关联起来。由此形成一种自顶向下的开发过程，使模型与实现持续保持对齐，同时保留原有灵活性，并让开发者获得更多支持特性。
Web services engineering is a crucial subject, because web services are often built to be used by other programs; thus they should have a good documentation targeting developers. Furthermore, when building a digital product, engineers need to build several programs that interact with a central instance of web services. OpenAPI, a popular industry standard, makes possible to document web services in order to quickly make a prototype of the product. It allows a top-down process where developers iterate to build an OpenAPI model that describes the web services they want, and then implement both the web services and the programs that will consume them. However, when doing such rapid prototyping, developers tend to either skip this design phase and implement web services right away, or stop updating the OpenAPI model when the product is released; in both cases they cannot take advantage of having an OpenAPI model aligned with the implementation. We show how OpenAPI can be extended to add implementation details inside models. These extensions link services to assemblies of components that describe computations. Hence a top-down development process that keeps model and implementation aligned. Moreover, this makes possible for developers to benefit from more support features while keeping the same flexibility.