Issue with Missing Mandatory contentType Field in ExpectedResponse

[RobWin]

Description:

When implementing and testing the Directory Discovery process with Webthings (https://plugfest.webthings.io/), I encountered an inconsistency related to the contentType field in the response.

Expected Behavior:

The spec mentions that the contentType field is mandatory in the response. The example response in the spec is:

"response": {
    "contentType": "application/json"
}

Actual Behavior:

However, there are cases where the contentType field is missing from the response. For example:

"response": {
    "htv:statusCodeValue": 201
}

This missing mandatory contentType field causes parsing to fail.

Steps to Reproduce:

1. Test using the Webthings platform (https://plugfest.webthings.io/).

Expected Outcome:

Ensure that the contentType field is always included in the response, as per the spec.

Additional Information:

• The spec should also clarify whether the description field is actually optional or not, as it is not mentioned explicitly in the spec.