Re: [dxwg] List profiles for dynamic resources (#785)

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: <>; rel="self"; profile="urn:example:profile:1", 
<>; rel="alternate"; profile="urn:example:profile:2 <>; rel="self"; type="text/html",
<>; 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 using your GitHub account

Received on Thursday, 9 May 2019 22:59:07 UTC