[dxwg] Resource URLs prohibit the use of QSA in data aggregators and/or single page web applications (#1301)

ssstolk has just created a new issue for https://github.com/w3c/dxwg:

== Resource URLs prohibit the use of QSA in data aggregators and/or single page web applications ==
Paragraph "7.3.2.3 Resource URL" in https://www.w3.org/TR/2019/WD-dx-prof-conneg-20191126/ mentions the following:

```
For the representation of Resource X, according to Profile Y, in Media Type Z:

Rather than:
GET /single/endpoint \
            ?resource=http://example.org/resource/X \
            &_profile=Y \
            &_mediatype=Z HTTP/1.1

Use:
GET /resource/X?_profile=Y&_mediatype=Z HTTP/1.1
```

To me this seems like a missed opportunity. Is it not the case that in a decentralized Web, it is also desirable to be able to select services from data aggregators. These may not be the original content holder, but are still able to present information on a certain resource, including alternate profiles. I believe I recall a presentation by Ruben Verborgh a few years back in which he advocated the choice for consumers to select a service for their data, which may indeed be a data aggregator. Indeed, I have seen a number of applications which use such a method (mainly: single page applications) and would still benefit from being able to use QSA for profile negotiation.

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1301 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 February 2021 11:09:18 UTC