Re: [dxwg] QSA Profile Conneg realisation must support QSA discovery

@akuckartz a standardised function would return all the keys that an implementation uses for profiles, Media Types, etc. and this would be required to be implemented for all QSA implementations, even ones that use the "standard pattern" keys of `_profile` & `_mediatype`. I already have many API instances that use `_view` & `_format`. 

This function would really be the starting point function that any implementation accessor could use to work out how the implementation is configured.

In HTTP land, there is no need for this function as the `Accept-Profile` request and the `Content-Profile` header keys will have been registered, just as `Accpet` and `Content-Type` already are.

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

Received on Thursday, 8 November 2018 07:20:10 UTC