[Specifications] collections with manages block & Triple Pattern Fragments

elf-pavlik has just created a new issue for https://github.com/HydraCG/Specifications:

== collections with manages block & Triple Pattern Fragments ==
Continuing from https://github.com/HydraCG/Specifications/issues/137#issuecomment-339353568

>> @elf-pavlik: do you have some insights to share on how you see Hydra and LDF working together to expose the same dataset?

> @RubenVerborgh: I guess this is more of a question of doing the same things different ways in Hydra. The TPF interface uses Hydra to explain "you can filter by triple pattern". If there are multiple ways to express this, we need to discuss this, and perhaps eliminate.


If we look at snippet in [UC#1EntryPoint](https://github.com/HydraCG/Specifications/blob/master/drafts/use-cases/1.entry-point.md#details)

```json
{
  "@context": "/api/context.jsonld",
  "@id": "/api",
  "@type": "hydra:EntryPoint",
  "collection": [
    {
      "@id": "/api/events",
      "title": "List of events",
      "@type": "hydra:Collection",
      "manages": {
        "property": "rdf:type",
        "object": "schema:Event"
      },
      "operation": {
        "@type": ["hydra:Operation", "schema:CreateAction"],
        "title": "Create new event",
        "method": "POST",
        "expects": "schema:Event"
      }
    }
  ]
}
```

This `manages` block works very similar to what I looked at doing with `void:classPartition` https://github.com/HydraCG/Specifications/issues/126#issue-237916600
At the same time single `manages` block seems to work very closely to Triple Pattern Fragments. Actually with HTTP/2, Etag etc. I consider in projects I work on not to use collections which return members inline but rely on TPF and just fetch new members or members that have changed.
I think we should take some time to clarify how collections with `manages` block and TPF supposed to work together, maybe even write side by side comparison with guidelines about strengths and weaknesses of each one.

Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/142 using your GitHub account

Received on Wednesday, 25 October 2017 17:40:04 UTC