Page 2, Line 7 (and elsewhere):Â machine-to-machine should be hyphenated pretty much anywhere it appears in this document.
Page 8, Line 36:Â the example formatted property name (created_at) does not match the Google Doc original.
Page 9, Line 6: the final sentence of the first paragraph is oddly worded. Suggest:ÂÂThe OpenC2 Language Specification and Actuator Profile specifications focus on theÂlanguage content and meaningÂat the producer and consumer of the command and response while the transfer specifications focus on the protocols for their exchange.
Page 10, Line 1:Â References to the subcommittees will be inappropriate as this document progresses through standardization; remove.
Page 12, Line 23: insert comma between "duration' and "etc."
Page 12, Line 27: insert "corresponding" before "profile"
Page 12, Line 38:Â should "time" be "timing" in "...Âtime, periodicity, duration, ..."?
Page 12, Line 42:Â insert "meaningful, whether" before "mandatory to implement"
Page 16, Line 36:Â the phrase "... appending "." or "." to the type ..." doesn't make sense. Is something missing?
Page 23, Line 12:Â suggest adding "implementers" before "MUST NOT" for clarity.
Page 23, Line 24:Â suggest adding "implementers" before "MUST NOT" for clarity.
Page 40, Line 27:Â the run-on formatting of the example command message makes it hard to read and reduces its utility as an example.
Page 40, Line 39:Â the run-on formatting of the example response message makes it hard to read and reduces its utility as an example.ÂÂ