https://access.redhat.com/documentation/en-us/red_hat_decision_manager/7.11/html-single/getting_started_with_red_hat_decision_manager/index#dmn-execution-rest-proc_getting-started-decision-services

The section "7.1. Executing a DMN service using the KIE Server REST API" refers to some curl command examples and responses.

for example

curl -u wbadmin:wbadmin -H "accept: application/json" -H "content-type: application/json" -X POST "http://localhost:8080/kie-server/services/rest/server/containers/traffic-violation_1.0.0-SNAPSHOT/dmn" -d "{ \"model-namespace\" : \"https://github.com/kiegroup/drools/kie-dmn/_60B01F4D-E407-43F7-848E-258723B5FAC8\", \"model-name\" : \"Traffic Violation\", \"dmn-context\" : {\"Driver\" : {\"Points\" : 15}, \"Violation\" : {\"Type\" : \"speed\", \"Actual Speed\" : 135, \"Speed Limit\" : 100}}}"

Note that model-namespace URI now starts from "https://kiegroup.org/dmn/" when generated by DMN editor. (e.g. https://kiegroup.org/dmn/_B59E5A20-CAB1-4681-AB19-A5D0AE18C2C4) since RHDM 7.4.0. Imported sample DMN may have ""https://github.com/kiegroup/drools/kie-dmn/" model-namespace so I'm not saying which is right or wrong. But when users follow this getting started procedure, they would create a DMN with the DMN editor so it will have "https://kiegroup.org/dmn/" model-namespace.

The document tells that users have to replace the example model-namespace value with their own model-namespace value. So this is not a serious document bug. However, it might be error-prone... imagine that users copy&replace only the UUID part (B59E5A20-CAB1-4681-AB19-A5D0AE18C2C4) in the curl command.