Re: [Specifications] Simplify discovery of collections that contain resources of a certain type

I think we could make something like `hydra:memberType` a special case (shortcut). Later when we have something more generic like
``` json
        "hydra:constraint": {
            "rdf:type": "schema:Event",
            "foo:country": "bar:Italy"
        
```
we could add for reasoning purposes
```ttl
hydra:memberType owl:propertyChainAxiom (hydra:constraint rdf:type) .
```

Once again, more generic solution like proposed `hydra:constraint` should IMO get considered together with `hydra:manages`. For example I don't see how `hydra:constraint` can support use of predicate in `@reverse` direction, while `hydra:manages` wouldn't allow `owl:propertyChainAxiom` 'shortcuts' like the one above.

If we work in small increments, introducing `hydra:memberType` in use case seems like an improvement over current `examplevocab:events`. We can always update it to something more generic once we agree on it.

```json


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

-- 
GitHub Notification of comment by elf-pavlik
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/126#issuecomment-316241795 using your GitHub account

Received on Wednesday, 19 July 2017 01:01:40 UTC