Conformance structure

I'm reading OSLC Delegated Dialogs 3.0 (04 March 2016) and was struck by the majority of the document being non-normative, until I hit 6. Implementation Conformance.

I appreciate the separate of examples and the notation of non-normative sections but except for "selection" and "creation," 6.1.1 and 6.1.2 are identical. Yes?

That's a sure sign that the material could be broken into general normative requirements stated in prose and then we vary only the part that differs. yes?

Note also that you are mixing client and server conformance requirements, which will make it more difficult for implementers to easily check to see if they have met all the requirements.

For example, lets say that we define all the requirements stated in 6.1.1, 6.1.2 and 6.1.3 as follows: (partial)

– A response to a successful HTTP request for an LDP container includes a link header [RFC5988] where:

The context URI is the effective request URI,
The target URI is the URI of the dialog descriptor.

and,

The link relation is http://open-services.net/ns/core#selectionDialog, or

The link relation is http://open-services.net/ns/core#creationDialog.

(you may also define #selectionDialog and #creationDialog elsewhere and use section references)

That enable you to move the MUST language into the conformance clauses because you will have cases where a server produces and a client consumes the same required content.

Generally those are gathered together in the conformance clause when enables you to define conformance targets.

A conformance target means that if I am writing a client, I don't have to search all of the text to discover every MUST for my client, I need only follow the conformance section for my app.