|
| 1 | +## MDSL change log (and release notes) |
| 2 | + |
| 3 | +Also see GitHub [release notes](https://github.com/Microservice-API-Patterns/MDSL-Specification/releases). |
| 4 | + |
| 5 | +V4.0, August 2020 |
| 6 | + |
| 7 | +* Improved HTTP and Java bindings |
| 8 | +* Added API provider implementation concept (assuming Java use for now) |
| 9 | + |
| 10 | +V3.4, July 2020 |
| 11 | + |
| 12 | +* Cleanup |
| 13 | +* Additional generators: gRPC protocol buffers, Jolie (and, indirectly, WSDL/XML Schema) |
| 14 | + |
| 15 | +<!--V 3.2, V3.3? --> |
| 16 | + |
| 17 | +V3.1.1, June 2, 2020 |
| 18 | + |
| 19 | +* Added three EIPs as stereotypes on message level: `'Command_Message' | 'Document_Message' | 'Event_Message'` |
| 20 | + |
| 21 | +V3.1.0, May 26, 2020 |
| 22 | + |
| 23 | +* Resolved two more TODOs in grammar |
| 24 | +* MAP decorators now match current pattern naming (operation level, element level) |
| 25 | +* Removed experimental MAP decorators (endpoint level) |
| 26 | + |
| 27 | +V3.0.0, May 22, 2020 |
| 28 | + |
| 29 | +* Removed deprecated support for Value `V` as AP (`D` should be used instead) |
| 30 | +* Corrected MAP decorator rule `MapPattern`: now has `'Control_Metadata' | 'Aggregated_Metadata' | 'Provenance_Metadata'` |
| 31 | +* Semantic Versioning reverted to `String` (usage of semantic versioning to be validated, not forced by grammar) |
| 32 | +* Moved `default is "..."` value to data type definition (from cardinality); this is an experimental feature still! |
| 33 | +* Further TODO resolution |
| 34 | +* Documented optionality operations/messages in grammar and new example (`expecting`, `delivering`) |
| 35 | +* Misc documentation updates |
| 36 | +* The Eclipse plugin tool now supports a generic Freemarker generator and a few simple validators (demo) |
| 37 | + |
| 38 | +V2.1.0, May 15, 2020 |
| 39 | + |
| 40 | +* Cleanup of grammar (TODOs, working comments, older rules) |
| 41 | +* Semantic version identifier: optional name removed |
| 42 | + |
| 43 | +V2.0, May 5, 2020 |
| 44 | + |
| 45 | +* Experimental parts removed from v1.2.0 (e.g., composition support) |
| 46 | + |
| 47 | +V1.2.0, March 17, 2020 |
| 48 | + |
| 49 | +* Extended proposal for asynch. messaging support on binding level (provider, client, gateway -> sender, receiver, broker) |
| 50 | +* March 25: project [wiki](https://github.com/Microservice-API-Patterns/MDSL-Specification/wiki) updated (presentations, getting started page) |
| 51 | + |
| 52 | +V1.1.0, February 8, 2020 |
| 53 | + |
| 54 | +* Updated endpoint role names from MAP: `CONNECTOR_RESOURCE` -> `TRANSFER_RESOURCE`, `STATIC_DATA_HOLDER` -> `REFERENCE_DATA_HOLDER` (so incompatible change). `TRANSFER_RESOURCE` and `LINK_LOOKUP_RESOURCE` also available as aliases (experimental). |
| 55 | +* Updated operation responsibility names from MAP: `EVENT_PROCESSOR` -> `NOTIFICATION_OPERATION`, `BUSINESS_ACTIVITY_PROCESSOR` -> `STATE_TRANSITION_OPERATION` (*note:* kept old names as variants, so syntactically compatible) |
| 56 | +* Some grammar cleanup (comments, TODOs) |
| 57 | + |
| 58 | +V1.0.3, January 9, 2020 |
| 59 | + |
| 60 | +* Deprecated `V`, brought back `D` for Data Element/Entity Element from MAP. Rationale: user feedback |
| 61 | +* Brought back long forms for parameter (stereo-)types: `Data`, `Identifier`, `Link`, `Metadata` (short forms `D`, `ID`, `L`, `MD`still work). Rationale: user feedback |
| 62 | +* Fixed doc pages bug (`blob` -> `raw`) |
| 63 | + |
| 64 | +V1.0.2, October 18, 2019 |
| 65 | + |
| 66 | +* MAP decorators can now be "text" STRINGs (to ease/improve MDSL generation Context Mapper): |
| 67 | + * Example: `operation createAddress with responsibility "BUSINESS_ACTIVITY_PROCESSOR" in "REQUEST_REPLY" conversation` |
| 68 | + |
| 69 | +V1.0.1, August 31, 2019 |
| 70 | + |
| 71 | +* Demo/proposal how to model pub/sub and event sourcing |
| 72 | +* Demo/proposal for specifying authentication (inspired by OAS 3.0) |
| 73 | +* Other feedback from VSS19 captured as TODOs (e.g., oneOf/allOf,anyOf from OAS 3.0) |
| 74 | + |
| 75 | +V1.0, July 19, 2019 |
| 76 | + |
| 77 | +* Entire API description can now also be versioned semantically |
| 78 | +* Removed unnecessary () in treeNode rule (line 130) |
| 79 | +* Grammar rules edited for better antlr4 compatibility (no changes to language) |
| 80 | +* Endpoint parameters were experimental so far, and are now deprecated (but not featured in examples anyway) |
| 81 | +* Repository/examples cleanup (TODOs) |
| 82 | + |
| 83 | +V0.99, June 26, 2019 (backward compatible except for `blob` -> `raw` and typo fix: `AGGRESSIVE_OBSOLESCENCE`) |
| 84 | + |
| 85 | +* Housekeeping |
| 86 | +* Mappy demo support (examples) |
| 87 | +* Renamed byte array base type from `blob` to `raw` |
| 88 | +* Type in EvolutionStrategy rule fixed: from `AGGRESSIVE_OBSOLESCENSE` to `AGGRESSIVE_OBSOLESCENCE` |
| 89 | + |
| 90 | +V0.98, May 22, 2019 (backward compatible) |
| 91 | + |
| 92 | +* Data types and operations can now be versioned as well: |
| 93 | + * `data type VersionedDataType version 0.0.1 {ID, V}` |
| 94 | + * `operation sampleOperation version 0.0.1 with responsibility EVENT_PROCESSOR` |
| 95 | + |
| 96 | +V0.97, May 15, 2019 |
| 97 | + |
| 98 | +* Removed '|' from Cardinality rule, no longer needed and not featured in examples anyway |
| 99 | +* Some new comments and TODOs |
| 100 | + |
| 101 | +V0.95 and v.096, May 13, 2019 |
| 102 | + |
| 103 | +* `V<"SomeUnknownType">` is now illegal, same effect can be achieved with plain identifier or `data type SomeUnknownType P` |
| 104 | +* Refactored data type grammar to make it more precise and to make code completion more useful (to be tested) |
| 105 | +* External SLAs now supported |
| 106 | +* Many other tweaks in API provider part (e.g. SimpleMeasurement) |
| 107 | + |
| 108 | +V0.94, May 13, 2019 |
| 109 | + |
| 110 | +* Added `V<void>` due to user feedback and test results |
| 111 | +* Changed base types to include 'long' and 'double' (instead of 'float') |
| 112 | +* Enabled support for choice modeling on PT level data type ChoiceDemo `{"optionA":V|"optionB":V}` |
| 113 | +* Updated pattern stereotype enum to reflect latest MAP status |
| 114 | + |
| 115 | +V0.93a, May 10, 2019: |
| 116 | + |
| 117 | +* Removed "contract" from "endpoint contact type" for brevity |
| 118 | +* Removed "instance" from "endpoint instance location" for brevity |
| 119 | +* `<<Value>>` no longer available as pattern stereotype (undone later) |
| 120 | +* Entity and E no longer available as parameter roles (but D and Data) |
| 121 | + |
| 122 | +V0.93b, May 10, 2019 (experimental): |
| 123 | + |
| 124 | +* Only `V<int>` supported as parameter role/type pair, `Value<int>` removed to avoid confusion with `<<stereotypes>>` |
| 125 | +* `<<Identifier>>` and `<<Link>>` and `<<Metadata>>` now available as pattern stereotypes (`<<Entity>>` was supported already) |
0 commit comments