Darrel

Thanks for reporting this. I suspect this is an error in the OpenAPI.Net library. I'm going transfer the issue to that repo.

I don't think the constraint about not declaring Accept headers existed when the runtime expression was created so I didn't think about that contradiction. However, I believe it still is...

Discovery of API Versions is something that the TSC (meeting 2017-12-15) feels is out of scope for the OAS, but part of the bigger topic of API discovery. There is...

@idosal I noticed in the proposal the use of the media type `text/html+mcp`. I would like to suggest an alternative, but before I do I want to explain why the...

@glen-84 I don't have much visibility into what the range of values could be for the profile. I think mcp-app is fine too.

@antonpk1 I am contractually bound to say you should not use a media type that is not registered and is structurally invalid. :-) However, I do understand your concern over...

> it stretches the spec's intent, which assumes a one-to-one mapping between request and response I would argue that this design does more than stretches the JSON RPC spec, I...

@matoushavlena I largely agree. JSON-RPC provides an envelope format for transports that don't have them. HTTP already has URIs, headers, status codes, so JSON-RPC syntax becomes redundant waste. Putting the...

@mikekistler Yeah, you are correct. The fact that MCP attempts to be a bidirectional protocol that interleaves S->C requests within C->S requests, makes the approach I suggested problematic. If we...

I don't believe it is possible to use $select and $expand on the results of actions, as per OData. You can designate a function as composable and then it should...