Re: [Specifications] Relative Template URIs (#208)

> This seems it doesn't fit to the intermediate parent

Yes, I know you're right and I admit taking a little liberty in interpreting the nature of this "embedding". Unfortunately, the HTTP spec is rather closely related to HTML hence the spec is not as universal as it could.
I do find the notion of graph subject/object relation a close enough approximation. Especially easy to accept when you look at the graph as a JSON-LD tree

> It is somehow unfortunate to have implementation of the feature in discussion without resolving it

Chicken and egg? How can you standardise anything without implementing first but at the same time hold off any implementation before you standardise? 🤔 

Treat it as a proof of concept. And I have only implemented the "Encapsulating Entity" way for now

```
<collection/> hydra:search [
  hydra:template "{?name,tag}
] .
```

Which results in `<collection/?name=john&tag=friend>`

> I feel like we may need something extra added to the vocabulary/spec that servers will need to use explicitly in order to amend client's behavior in that matter.

Very on point, only that I'm a little tired of only trying to following "feelings". Only by actually implementing something, even if not yet agreed as "standard", will we be able to decide whet works and what doesn't. 

And granted, this is not the first and not the last code in Alcaeus which fills in gaps in the specification to get a useful result of Hydra

-- 
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/208#issuecomment-617607719 using your GitHub account

Received on Wednesday, 22 April 2020 07:39:11 UTC