[NOTE: This is from #15. The above link has more than one issues. In order to make it easier to track, I decide to split them into individual issues]
**More points about Section 4.1
1) Defining system/application-specific vocabulary, the version update problem is faced, deploying the changes for use in existing deployments would be difficult.
2) This interpretation of specific vocabulary outside HTTP / CoAP methods could also add some burden to the most resource-constrained devices, something that could be avoided with defining the scope in the URL, without app-specific filters.
3) The key issue here is interoperability, which is not guaranteed if not any HTTP client/server/browser can not understand the scope of URL because it includes some app-specific vocabulary. Perhaps with different versions. However, every HTTP-compliant software knows what to do with basic HTTP methods.
[NOTE: This is from #15. The above link has more than one issues. In order to make it easier to track, I decide to split them into individual issues]
**More points about Section 4.1 1) Defining system/application-specific vocabulary, the version update problem is faced, deploying the changes for use in existing deployments would be difficult.
2) This interpretation of specific vocabulary outside HTTP / CoAP methods could also add some burden to the most resource-constrained devices, something that could be avoided with defining the scope in the URL, without app-specific filters.
3) The key issue here is interoperability, which is not guaranteed if not any HTTP client/server/browser can not understand the scope of URL because it includes some app-specific vocabulary. Perhaps with different versions. However, every HTTP-compliant software knows what to do with basic HTTP methods.