Dave Wedwick

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dave Wedwick

  • Rank
  1. Section 7.3 for Sag Charts Rather than have Lines be an array of strings, why not do like: "Lines": [ { "Base": 6, "Add": 1, "Radius": 15, "Angle": 0, "Sag": 3.17 }, { "Base": 6.00, "Add": 1.00, "Radius": 15.00, "Angle": 15, "Sag": 3.56 }, ... ] No need to multiply by 100 and naming the values gives more clarity.
  2. Fixes for the example in section 4: Use the standard double-quote char everywhere - some non-standard ones are in the example (e.g. “Product IDs” versus "Product IDs") "Blank Collections" section - remove the last comma after BLK-YYY-010 since this is the last element in the array I attached a working file after the fixes above. Suggestions for consistency: Consider renaming UsableDiameter to have a space - same for RightOPC, LeftOPC, RightID, etc. as the convention seems to be space separated names like: Capitalize words in the names - change "Owner name" to "Owner Name" and "contact" to "Contact" Clarity on JSON Arrays In section 7.3 RFC 7159 says "An array is an ordered sequence of zero or more values." So, something like [1, 2, 3, 4, 5] must always be in that order. If a JSON parser does not maintain that order, then the parser is faulty. lpds-example.json