← Prev in month ← Prev in thread
Next in thread → Next in month →

Comments on Common Encodings for OBIX v1 PRD02

From
Toby Considine <>
Date
2014-02-17T01:39:50+00:00
ID
[email protected]
Thread
Comments on Common Encodings for OBIX v1 PRD02
Comments on Common Encodings for OBIX v1 PRD02

Toby Considine

 

Non-Standard Formatting.

The OASIS template defines inter-paragraph spacing. In several locations, additional paragraphs were added. This may be an artifact of format conversion. Examples are:

Line 34

Line 39

(Make sure all instances of OBIX are capitalized properly – see 109)

 

 

Document Consistency.

Compare intro to section 3 (Binary) and to section 4 (JSON). Also, if we are going to go into the history of JSON, it is more properly routed in the LISP family of exchanges from which the literals of _javascript_ are derived. We should avoid formulations that can even begin to suggest disputation of history to the reader. The intro to 5 (EXI) is the clearest and least argumentative example.

 

Accordance/Conformance

Line 464: suggest “according to” be changed to “in conformance with”

 

 

Conformance:

Suggest adding call-outs to the “mother specs”

XML must conform with a well formed document as described in RFC…

JSON must conform with RFC4627

Etc.

 

 

 

 

 

"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." 

- Brian W. Kernighan 

Toby Considine
TC9, Inc

OASIS TC Chair: oBIX & WS-Calendar

OASIS TC Editor: EMIX, Energy Interoperation

SGIP Smart Grid Architecture Committee

  

Email: 
Phone: (919)619-2104

http://www.tcnine.com
blog: http://www.NewDaedalus.com
← Prev in month ← Prev in thread
Next in thread → Next in month →