- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 May 2019 22:59:05 +0000
- To: public-dxwg-wg@w3.org
Mulling this over - my concern is about the cartesian product of all possible negotiation dimensions (including language, version, spatial resolution, etc. I dont know enough about link headers and support in client libraries - but it strikes me this would be informationally complete: Link: <http://example.org/a/resource>; rel="self"; profile="urn:example:profile:1", <http://example.org/a/resource>; rel="alternate"; profile="urn:example:profile:2 <http://example.org/a/resource>; rel="self"; type="text/html", <http://example.org/a/resource>; rel="self"; type="application/xml" this is order D x N where D is number of dimensions and N is number of options for a given dimension (the cartesian product is N exp(D) this puts the responsibility on the client to match the resource URI and calculate the intersection - buts thats pretty trivial and can be implemented in reusable libraries. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/785#issuecomment-491096802 using your GitHub account
Received on Thursday, 9 May 2019 22:59:07 UTC