…ition of release.

To be checked: I've used \\n\\n to create new paragraphs in the schema. I'm not sure that'll work and I'm not sure whether this should be preceded / followed by spaces (I follow by a space but do not preceed, but I'm afraid that will lead to indentation on the first row of the new paragraph.)

Add "Contracting and planning processes" section to the Mapping the hard cases of the Guidance. Rename "unsuccessful procedures" and "pre-qualification". Minor updates in other parts of the documentation.

Also: change definition of contracting process from "aimed at concluding"to "aimed at implementing".

See #903 (comment)

…ning-process

…-planning-process"

…nstead of "[contracting process] identifier"

…pt of the ocid to avoid confusion between real-world processes and their data representation.

…describing unique identifiers and the ocid field

Signed-off-by: Yohanna Lisnichuk <[email protected]>

Signed-off-by: Yohanna Lisnichuk <[email protected]>

release:
- Change the first sentence to what OCDS is used for (not releases specifically, defined later).
- Remove sentence about what concepts releases cover, as this is done by the rest of the schema.
- Move "many releases" sentence before "previous releases" sentence, for better flow.
- Small copy-edit.

ocid:
- Restore two-sentence construction, to distinguish primary and secondary use cases.
- Clarify that the secondary use cases are alternative, not additional, semantics.
- Clarify the relationship between the release and process.
- Use "internal identifier" consistently.

…d concepts, not OCDS concepts.

…pen Contracting ID"

- schema/identifiers: Use "release" not "OCDS release"

…the description of a record. Adapt title and description for ocid from release schema.