Re: [dxwg] Query string implementation of profile selection (#544)

From what @nicholascar says, it sounds like there is a fair amount of extra work needed, that one would need to write up a detailed specification of the general approach, as we are supplying for QSA. That would be work in addition to documenting the API calls themselves. Where I work, we have developers using React and GraphQL, others using REST (often with clean URLs, or avoiding query strings except for media types), others using RPC, maybe even some still using SOAP. And there will be others I haven't thought of, or that haven't yet been invented. My point is that there are going to be many ways to do conneg by profile. Some people may want to implement it only slightly differently, and the approach we have right now permits that. What happens, then, when you want to write a program to harvest data according to multiple profiles automatically? Asking the programmer to test for and handle all the possibilities doesn't strike me as feasible. But if there were some standard way of indicating what options are available, something closer to documentation for the API than a generalized spec, then we could have something workable. Maybe it would be an extension to OAI-PMH.

GitHub Notification of comment by agreiner
Please view or discuss this issue at using your GitHub account

Received on Thursday, 24 October 2019 06:20:07 UTC