W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > October 2019

Follow-up to Conneg Poll

From: Nicholas Car <nicholas.car@surroundaustralia.com>
Date: Tue, 15 Oct 2019 21:53:21 +0000
To: "riccardo.albertoni@ge.imati.cnr.it" <riccardo.albertoni@ge.imati.cnr.it>
CC: "public-dxwg-wg@w3.org" <public-dxwg-wg@w3.org>
Message-ID: <KU1PR01MB21025A4B082FA2A6E9D2B843A2930@KU1PR01MB2102.apcprd01.prod.exchangelabs.com>
Hi Riccardo,

Iíd like to follow-up on your comments on the poll for moving Conneg to CR.

You said:

> I think there is a valuable amount of work in the current CONNEG document, and my concerns are mostly on the readability of the document.
Can you please review the ED now at https://w3c.github.io/dxwg/conneg-by-ap/ as a fair bit of copy editingís gone on so perhaps itís now easier to read?

>  I am assuming that all the open issues marked as red notes will be deleted or replaced with green notes.
Yes, this has happened.

> I list some suggestions for improvements
> -The section about "Status of this document" should be updated. It still mentions Github issues and says the document is a working draft.
I have moved the document to CR.

> - Section 2.1: "this specification includes several functional profiles of it". I am not sure what 'it' stands for here.
The Ďití was the specification itself. The descriptions of Functional Profiles that were in 2.1 have been moved to 7.1 and more introductory wording has been added. Now that the sectionís next to the full Functional Profiles description, hopefully it makes more sense.

> - In Figure 1: shouldn't cp:rrd be cnpr:rrd ? Cnpr is the only namespace defined.
Yes, thanks, corrected!

- Section 6.1 .. "the the roles of client" --> "the roles of client"

- Section, 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.
Section 7.2.11 you refer to is now Section The work there is quite separate from Section 8. Link attributes.ís all about the HTTP Functional Profileís implementation of the Alternate Representations model using Link headers. Section 8ís also about Link headers but for communicating profile URI / token mappings which is now introduced in I think that a further tie-in between Sections  & Section 8 is needed so I will raise this with my co-editors this week.

So, I think that all your points except perhaps the last one are resolved, please could you confirm that?

Thanks for listing the points to address,

Received on Tuesday, 15 October 2019 21:53:28 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:33 UTC