w3c / dx-connegp

Content Negotiation by Profile
https://w3c.github.io/dx-connegp/connegp/
Other
6 stars 5 forks source link

Add motivating text to the HTTP Alternate Representation Data Model #9

Closed larsgsvensson closed 1 year ago

larsgsvensson commented 5 years ago

In his conneg-by-ap-to-CR vote, @riccardoAlbertoni suggests that we add some motivating text to §7.3.1.1 of conneg-by-ap

Section 7.2.1.1, an introduction about what is going to be described in this section and why you are presenting the definition of HTTP link would probably help to keep the reader on track.

(I assume it's section 7.3.1.1 since there is no §7.2.1.1 and we've shuffled things around a bit...)

@nicholascar, can you have a look at that?

nicholascar commented 4 years ago

The following text added for this issue is now present in the ED:

Functional profile implementations need to ensure that they, in addition to implementing the Abstract Model's functions, can deliver alternate representation information as per the Alternate Representations Data Model. In this HTTP functional profile, the chosen mechanics for doing this are Links headers (from [RFC8288]), as described below.

nicholascar commented 4 years ago

@riccardoAlbertoni does the section, now at https://w3c.github.io/dxwg/connegp/#http-altp, have sufficient text to address your concern here?

nicholascar commented 4 years ago

@riccardoAlbertoni can I close this?

larsgsvensson commented 1 year ago

@riccardoAlbertoni This issue is now "due for closing". Do you have any final remarks?

riccardoAlbertoni commented 1 year ago

No I do not have other remarks on this,Thanks