Decide on a structure for main conneg doc content

[nicholascar]

This will give headings and structural outline for the main content of the Conneg doc.

Content drafted here will be placed into the Conneng doc when agreed to by the Conneg subgroup of the DXWG.

[larsgsvensson]

Looking at §6 Realisations in the current ED, I wonder if it wouldn't be better to group the descriptions by use case, e. g.

• Profile Listing (A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the representation most appropriate for their use. #285, There should be a way to look up additional information about a profile - this may be machine readable for run-time mediation or used to develop or configure a client [ID2] (5.2) #286, Profiles offered by a service must be discoverable through a machine-readable graph of metadata that describes what is offered and how to invoke the offered profiles. [ID5] (5.5) #288, Profiles listing [RPFL] #73)
  • Realisation through QSA
  • Realisation through Conneg
• Profile Negotiation (A server can indicate that a response conforms to multiple profiles. [ID3] (5.3) #287, When requesting a representation, a client must be able to specify which profile it prefers the representation to adhere to. This information about the requested profile is not a replacement for content type (e. g. application/xml), language (e. g. zh-Hant) or any other negotiated dimension of the representation. [ID5] (5.5) #289, There need to be an http-based mechanism to point to representations conforming to other profiles [ID30] (5.30) #266, Enable the ability to negotiate the data profile via http, similar to the negotiation of data formats today. [ID30] (5.30) #265, Define conneg interaction with media types that have a profile param #261, Profile negotiation [RPFN] #74, Profile Composition and Languages #162, Responses can conform to multiple, modular profiles (UC 5.3) #217)
  • Realisation through QSA
  • Realisation through Conneg

Then we could move all the relevant requirements from the end of the document to where they will be dealt with (once they are approved, that is...)

[larsgsvensson]

I think this can be closed since we have a structure for the main document

[larsgsvensson]

closed in conneg meeting 2019-03-13