Releasenotes 653, mdsl doc page update

_docs/generators/mdsl.md

@@ -15,7 +15,7 @@ how we would derive (micro-)services from models based on strategic DDD. The gen
 |----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Upstream Bounded Contexts from upstream-downstream [relationships](/docs/context-map/#relationships)                             | Service Specification (API description)            | We create one service specification for each upstream Bounded Context of your Context Map.                                                                                                                                                                              |
 | [Exposed Aggregates](/docs/context-map/#exposed-aggregates)                                                                      | Endpoint                                           | Every exposed Aggregate of your upstream Bounded Context results in one endpoint.                                                                                                                                                                                       |
-| [Application layer](/docs/application-and-process-layer)                                                                         | Endpoint                                           | In case you model an application layer, we generate an additional endpoint for it. The endpoint contains the operations of the application services and/or commands.                                                                                                    |
+| [Application layer](/docs/application-and-process-layer)                                                                         | Endpoint, Flow                                           | In case you model an application layer, we generate an additional endpoint for it. The endpoint contains the operations of the application services and/or commands. *Update:* CML flows are mapped to MDSL flows as well; they must not contain any operations.                                                                                                   |
 | Public methods/operations of the [aggregate root entity](/docs/tactic-ddd/#entity) or of [Services](/docs/tactic-ddd/#services). | Operation                                          | Your exposed Aggregates should contain methods/operations, either on the [aggregate root entity](/docs/tactic-ddd/#entity) or in [Services](/docs/tactic-ddd/#services). For every method/operation in those objects we generate an operation in MDSL.                  |
 | Parameters & return values of methods/operations                                                                                 | Base types or data type specifications if possible | If you use primitive data types in CML, they are mapped to the base types of MDSL. If you refer to objects (such as entities) in CML, we produce a corresponding parameter tree. Types which are not further declared are mapped to abstract, unspecified elements (P). |
 | Upstream Bounded Contexts from upstream-downstream [relationships](/docs/context-map/#relationships)                             | API provider                                       | For the upstream Bounded Context we also generate an API provider.                                                                                                                                                                                                      |
@@ -158,8 +158,8 @@ As illustrated above, the patterns on the endpoint/resource level are added with
  * [OPERATIONAL_DATA_HOLDER](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpoints/OperationalDataHolder)
  * [MASTER_DATA_HOLDER](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpoints/MasterDataHolder)
  * [REFERENCE_DATA_HOLDER](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpoints/ReferenceDataHolder)
- * [TRANSFER_RESOURCE](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpoints/TransferResource)
- * [LOOKUP_RESOURCE](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpoints/LookupResource)
+ * [DATA_TRANSFER_RESOURCE](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/DataTransferResource)
+ * [LINK_LOOKUP_RESOURCE](https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/LinkLookupResource)
 
 #### Operation Responsibility Patterns
  * [COMPUTATION_FUNCTION](https://microservice-api-patterns.org/patterns/responsibility/operationResponsibilities/ComputationFunction)
@@ -258,4 +258,4 @@ For example, you can move a set of _data types_ into the corresponding protected
 </pre></div>
 
 ## MDSL Support
-The current version of our MDSL generator is compatible with the MDSL version _5.0_. For further questions regarding [MDSL](https://microservice-api-patterns.github.io/MDSL-Specification/), please visit its website [https://microservice-api-patterns.github.io/MDSL-Specification/](https://microservice-api-patterns.github.io/MDSL-Specification/). You can also find the update site to install the MDSL plugin in Eclipse there.
+The current version of our MDSL generator is compatible with the MDSL Version 5. For further questions regarding [MDSL](https://microservice-api-patterns.github.io/MDSL-Specification/), please visit its website [https://microservice-api-patterns.github.io/MDSL-Specification/](https://microservice-api-patterns.github.io/MDSL-Specification/). This is the [update site](https://microservice-api-patterns.github.io/MDSL-Specification/updates/) to install the MDSL tools plugin.

_news/2021-10-06-v6.6.0-released.md

@@ -0,0 +1,14 @@
+---
+layout: news
+title: "v6.6.0 Release Notes"
+author: Olaf Zimmermann
+image: /img/mdsl-generator-1.png
+---
+
+Version 6.6.0 of Context Mapper is available now.  
+
+This minor release extends the [MDSL generator](https://contextmapper.org/docs/mdsl/) to convert [application layer flows](https://contextmapper.org/docs/application-and-process-layer/) in CML into API [orchestration flows](https://microservice-api-patterns.github.io/MDSL-Specification/flows) in [MDSL](https://microservice-api-patterns.github.io/MDSL-Specification/index). Note that only commands are supported; operations cannot be mapped. 
+
+The previous two releases 6.5.1 and 6.5.2 fixed bugs, see the [Relase Notes](https://github.com/ContextMapper/context-mapper-dsl/releases).
+
+As always, if you have any issues or other feedback, please [let us know](/getting-involved/).