Re: [dxwg] Clarify how to refer to alternates view methodology for profile neg

Rob & I think we can define an abstract API to emulate HTTP methods for multiple other implementations (QSA, REST API etc.) and then the current `_view`, `_format` Alternates View system can map its terminology to that thus avoiding having torename anything. But the AV system will have to be feature complete with the HTTP methods in order to be a full implementation, so the part about supporting `Accept-Encoding` etc. is still relevant.

We'll roll support for the other HTTP conneg headers into starting now (we need to the tookit updated anyway) but this won't affect alignment with any changes you and Ruben might make to the I-D.

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

Received on Monday, 24 September 2018 15:37:46 UTC