Requirement resources are problematic

It is not clear that representing requirements (Application Component Requirement and Platform Component Requirement) as individual HTTP resources is necessary or desirable. The idea of matching Requirement resources against Capability resources presumes a lot of things. First off, it presumes some a priori knowledge of how the provider models their underlying capabilities. For example, a Platform Component Requirement on a specific version of the Java Runtime Environment pre-supposes that the target platform will model it's JRE(s) as either a Platform Component Template or a Platform Component Capability. Unless CAMP wants to go down the rathole of specifying how each language and framework combination should model their capabilities (which, IMO, is a bad idea) an App Dev/Admin can't make these assumptions and be portable across providers. Secondly, beyond just the model, you would need to specify canonical names and version string patterns (i.e. "Java Runtime Environment" and "1.6.0_*") if you wanted to support automatically matching Requirements against Capabilities. Again, I think that this is not an area that CAMP should get into.

This issue was raised by Gilbert Pilz and was drupal issue # 1093