@@ -64,7 +64,7 @@ Data models (go structs) for the MEC service will need to be updated based on th
1. Handler functions for the HTTP methods of respective endpoints will need to be updated if there are any changes in the MEC specification documents for those endpoints.
2. In case new endpoints or HTTP methods or both are added in the desired specification version, handler functions will need to be written for them in the backend code.
3. Emulation logic and functional implementation will need to be added in backend for the newly added endpoints and HTTP methods respectively.
3. Emulation logic and functional implementation will need to be added in backend for the newly added endpoints and HTTP methods respectively. Respective docs can be consulted for existing MEC service APIs and their features that are supported in the Sandbox. These features are documented in the "Macro-Network-Scenario" folder in this same repository. For example, see [MEC011](../Macro-Network-Scenario/MEC011.md), [MEC012](../Macro-Network-Scenario/MEC012.md), [MEC013](../Macro-Network-Scenario/MEC013.md), [MEC030](../Macro-Network-Scenario/MEC030.md) etc.
4.**Data model related changes in NBI code:**
- Validation checks for mandatory attributes in the incoming request
- Population of (mandatory) attributes while generating the response for a particular HTTP method
