Initial checkin to resolve issue 373.

[pvretano]

Closes #373

[fmigneault]

The "Cardinality" chapter seems very appropriate to explain the current 1.0 behavior, but it contradicts with the updated examples that use the planned deprecation of maxOccurs.

[m-mohr]

Is there a way to translate minOccurs/maxOccurs into a JSON Schema equivalent without them? If there is, it might help to have a note how to translate between them somewhere in the spec.

[jerstlouis]

@m-mohr There is no equivalent for the use of minOccurs / maxOccurs as a JSON Schema, because individual process inputs which occur can be substituted by an href reference (or collection or process with Part 3).

The JSON Schema is for the actual value of an input, regardless of where it comes from (inline, as an href reference, or from a nested process). That's what I pointed out in #373 (comment) .

To clarify, in Processes-1, "by reference" inputs are NOT defined as one particular JSON schema possibility with an "href" property. Rather (like Part 3 process and collection), href is an alternative way to provide an input that corresponds to a JSON schema which describe what you will find inline or at that reference (or generated by that process / collection).