- From: Markus Lanthaler via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jan 2018 20:36:36 +0000
- To: public-hydra-logs@w3.org
Both are totally valid. The advantage of the approach used in the use case document is that you won’t have to invent your own properties such as “events”, “issues” etc. that no one else will understand. Instead you can leverage the existing types. You would retrieve the entry point and then look for a collection that manages objects of the desired type, e.g., schema:Event. Collections are subclasses of hydra:Resource which means they are de-referenceable. In other words, yes, you should assume that such entities can be retrieved with a GET. -- GitHub Notification of comment by lanthaler Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/155#issuecomment-357053547 using your GitHub account
Received on Thursday, 11 January 2018 20:36:37 UTC