- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 19:29:43 +0000
- To: public-hydra-logs@w3.org
> It might be not as easy as it sounds. There can be multiple API documentation links, what if every part provides different value? I think that for the most part it actually is simple. If you consume multiple APIs (for example via multiple link headers), the client will have to understand all profiles used by all those APIs. No way around it. Good point about HTTP headers, but IMO same principle applies. The client will have to support the sum of all profiles. > We also need something for in-lined hypermedia controls Inlined controls will use the same descriptions, no? If API uses profiles `A` and `B` then you might expect those profiles applied to inline hypermedia. Am I missing something? > >Move the "Standard Profile" to a separate spec document. Would probably keep > I don't like it - I'd prefer to keep it as it is now. No strong opinion on my part. I can definitely live with that 😉 -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-634892333 using your GitHub account
Received on Wednesday, 27 May 2020 19:29:45 UTC