Section 3 - Simple editorial comments

155: replace with The oBIX design philosophy recognizes a commonality of functionality of the components of all control systems while hiding the underlying mechanisms and protocols. To that end, OBIX relies on the principles in Table [n].

156-161. Replace bullet points with a named table.

Should REST be replaced with CRUD? We can then add a sentence that suggests "For this document, we use REST operations as examples of CRUD operations in oBIX."

158: A better definition of URI, including translation of acronym. Reference to RFC 3986 would be good.

164: Remove "cleverly"

208-209L "Since OBIX is used to interact with control systems over the web, we use the URL to identify each resource. Just as we assume an XML encoding and a REST binding for all examples in this document, so to we assume a URL using the hypertext transfer protocol (URLs beginning with http beginning with HTTP. This is not meant to forbid the use of secure transfer (https or of other protocols (ws. Neither are the examples are meant to forbid the use of alternate ports. The URLs in examples in this document are for illustration only.
Or, see detailed comment on URLs. Below.

240-242: Consider replacing first 3 sentences with:
In oBIX, these patterns are modeled as a template object named the Contract.

244: Remove words "In Geek Speak". Replace with "Formally" if desired.