Meeting minutes
<YoucTagh> https://
roba: I have tried to fix broken meeting minutes
roba: broken links now fixed
topic+ Approve Minutes
<roba> +1
+1
<YoucTagh> +1
topic+ Previous Action Items
roba: Have not heard back from IETF
roba: Have not heard back from IETF
roba: YoucTagh promied to create PRs and has done so
This is PR 67
A discussion now followed regarding Issue 39 and the use of various HTTP status codes to communicate what a ConnegP server is doing. The suggestion from roba is that Link header requirements could be alstered to only be required to provide a link to the Alternates Profile, not all profiles.
YoucTagh: I am happy with this proposal - no need to send all profile/format possibilities to the client
NicholasCar: I too am happy with the proposal
roba: we don't have a strong requirement for use of other status codes, so that's future work, but 406 seems to be the most likely
roba: which Issues would a PR for this close? 5, 11, 19, 39 perhaps
Further discussion by all about several Issues and Pull Requests. NicholasCar will create a couple of PRs for address several Issues such as 26 & 27
Several Issues, such as #13, were closed where the requested edits are clearly visible in the document - should have been closed previously.
<YoucTagh> YoucTagh/
The link above is to an implementation of ConnegP that includes the ID of the resource as a QSA.
A discussion about Issue 57 and a templating profile of ConnegP is suggested to solve it and to replace the Alt Keywords profile
end the meeting
<roba> publish the minutes
<roba> rssagent, publish the minutes
rrsagent: publish the minutes