Re: [dxwg] Query string implementation of profile selection

The relevance and requirement to deal with QSA implementations has been discussed at length and rules in scope for the conneg doc with both a motivating Use Case (https://github.com/w3c/dxwg/issues/239) and derivative Requirements.

What we are doing in the doc is explaining the conceptual logic of what "content negotiation by profile" is and then showing how it may be done. HTTP conneg is the first/primary way but there are other ways, such as RESTful APIs that are already in use (Epimorphic's Linked Data Registry, CSIRO's SISSVoc, pyLDAPI etc...) and we want to ensure functional equivalence between methods.

> I would expect that [requests for datasets that implement specific profiles] to appear in the profiles guidance document.

Well, we should and will refer to the conneg doc from the Guidance doc, but we just have to be sure not to duplicate work. We have a duty to at least describe the IETF doc's information in the conneg doc since the IETF doc isn't a recognised W3C doc and that's why that info's there.

> conneg document, however, currently specifies a method of implementing negotiation (not just selection), which I see little reason to demonstrate

Well, as a tool maker (APIs) I need, or would like, to be told how to implement. The test API I've implemented (https://github.com/CSIRO-enviro-informatics/profile-conneg-qsa-realisation) actually demos QSA & conneg methods for dummy resources. The real production toolkit I use (https://github.com/RDFLib/pyLDAPI) will, when the spec is settled, implement both. As per the Use Case at the top, we benefit from multiple ways of getting at things.

> A related nit is that the document draws a distinction between 'HTTP' and 'QSA', 

This redundancy has been removed in the FPWD candidate now at https://w3c.github.io/dxwg/conneg-by-ap/.

I'm pretty sure I've not touched on each of your concerns in the text above. Could you perhaps itemise the issues again so we can deal with them one-by-one? I just find the discursive paragraph a little hard to follow.

-- 
GitHub Notification of comment by nicholascar
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/544#issuecomment-437232383 using your GitHub account

Received on Friday, 9 November 2018 02:51:01 UTC