[O01.01.01.05] Specify the RFC 10008 QUERY communication binding

[dotnetcadet]

Summary

Write the Communication section: the RFC 10008 QUERY binding per design decision D2. Covers media-type naming and the registration path, the 400/415/422 status taxonomy, Accept-Query (RFC 8941) semantics, caching/conditionals/no-transform, Location/Content-Location, the CORS-preflight note, and the optional GET fallback profile.

Acceptance Criteria

• The QUERY primary read binding and media types (application/vnd.ograph.query, application/vnd.ograph+json) are specified.
• The 400/415/422 status taxonomy and Accept-Query semantics are specified.
• Caching/conditionals, Location/Content-Location re-fetch, and the GET fallback profile are specified.
• A media-type registration path (vendor-tree vs standards-tree) is chosen per RFC 6838.

Standards and Compliance

• Implements the RFC 10008 QUERY binding and RFC 9110 status semantics; references RFC 8941 (Accept-Query) and RFC 6838. Governs V-01/V-02/V-04/V-08.