John Dziurlaj

**Organization Name**: The Turnout **Organization Type**: 1 (CTR) **Comment (Include rationale for comment)**: JSON Schemas map `xsd:language` typed properties to the plain JSON Schema `String`. However, the [XML Schema Part...

**Organization Name**: The Turnout **Organization Type**: 1 (CTR) **Document**: Various A lot of properties in the CDF data models use `xs:integer`. However, this allows for negative numbers, which makes little...

**Organization Name**: The Turnout LLC **Organization Type**: 1 (CTR) We use the JSON Schema data types to further restrict the JSON number data type. However, this provides limited protections in...

**Organization Name**: The Turnout LLC **Organization Type**: 1 (CTR) **Document**: All CDF specifications **Comment (Include rationale for comment)**: PDF page numbers and printed page numbers (i.e. numbers at the bottom...

Right now the JSON schemas developed produce JSON that somewhat verbose. In large JSON files, it's clear this is coming from two areas: 1. `@type` key is always required, even...

**Organization Name**: The Turnout **Organization Type**: 1 (Contractor) **Suggested Change**: Primitive subtypes such as `ShortString`, `HtmlColorString`, `TimeWithZone`, etc. are not well documented. In many cases, the documentation tooling generates hyperlinks...

JSON Schema format: uri appears to be stricter than XML anyURI. For example `www.example.com` is valid for XML but not JSON.

**Organization Name**: The Turnout **Organization Type**: 1 (Contractor) **Suggested Change**: Existing JSON Schemas do not have documentation associated with data structures, while XML Schema (XSD 1.0) does. Add support for...

Currently all UML properties are private. This presents issues when performing certain operations on the models, such as simulations.

In the word docs, the Appendixes are at the wrong heading level (6) instead of (1). Checked 1500-100 and 1500-102.