Consolidate Resource and ResourceTemplate definitions

[tzolov]

Problem
The current MCP specification has unnecessary overlap between Resource and ResourceTemplate definitions.
This creates duplicated code in SDK implementations and convoluted handling logic.

Proposed Solution
Expand the Resource's uri definition to support both static and dynamic (templated) URIs, then deprecate ResourceTemplate.

This would simplify the specification and reduce implementation complexity/overlaps for SDKs.

[pja-ant]

I'm not sure on this. While I agree there is a lot of overlap, there are differences (e.g. size doesn't make sense for ResourceTemplate) and they fundamentally are different things which can lead to more divergence in the future. In the current draft, Resource also has icons whereas ResourceTemplate does not (though, tbh, I'm not sure if that's an oversight or not...).

I do agree that it does cause a little bit of extra handling to deal with this, but I don't feel it should be a major nuisance. On the other hand, combing these together in the type system could lead to awkward things in the future if e.g. we want to add fields that are more specific to one or the other.

[jonathanhefner]

This would simplify the specification and reduce implementation complexity/overlaps for SDKs.

Could you elaborate on this?

I also tend to see Resource and ResourceTemplate as two different things. An analogy would be strings vs regular expressions. Or, more directly, URL vs URLPattern. 😄