Closed larsgsvensson closed 1 year 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.
@riccardoAlbertoni does the section, now at https://w3c.github.io/dxwg/connegp/#http-altp, have sufficient text to address your concern here?
@riccardoAlbertoni can I close this?
@riccardoAlbertoni This issue is now "due for closing". Do you have any final remarks?
No I do not have other remarks on this,Thanks
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
(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?