Organization of OData Documents

I had agreed to take offline a discussion on how we would ideally organize the set of OData documents.

According to the OASIS categorization of documents, I believe we are best served by identifying three related Work Products as follows:

1. Multi-part OData Core

a. Part 0: Core protocol document (includes normative reference to ABNF text document)

b. Part 1: URL conventions document

c. Part 2: CSDL document (includes non-normative reference to textual XSD for CSDL)

2. Standalone OData Atom format

3. Standalone OData JSON format

Batch processing (which is small) should be incorporated into 1a).

This proposed organization seeks to:

1) Clearly identify the core information that a reader needs to read to understand the specification (1a)

2) Clearly identify the complete set of information that an implementer needs to implement the core specification (1)

3) Identify multiple formats that may be used with (1)

4) While minimizing the total number of documents

Thoughts?

odata message