- From: Dietrich Schulten <ds@escalon.de>
- Date: Sun, 22 Feb 2015 17:33:59 +0100
- To: public-hydra@w3.org
Nope. It turns out we *do* need hydra:collection to point to orders.
Am 22.02.2015 um 09:41 schrieb Dietrich Schulten:
> {
> "@context": {
> "@vocab": "http://schema.org/",
> "hydra": "http://www.w3.org/ns/hydra/core#",
> "hydra:property": { "@type": "@vocab"},
> "orders": {"@reverse": "orderedItem"}
> },
> "@type": "CafeOrCoffeeShop",
> "@id": "http://example.com/store",
> "name": "Kaffeehaus Hagen",
> "makesOffer": [
> {
> "@type": "Offer",
> "@id": "http://example.com/offers/1234",
> "itemOffered":
> {
> "@type": "Product",
> "@id": "http://example.com/products/latte",
> "name": "Latte Macchiato",
> "orders": {
> "@id": "http://example.com/orders",
This is probably not going to work. The "orders" property as used here
means "orders containing Latte Macchiato". Reflected in a URL structure,
that would be /products/latte/orders.
But that is not the collection we want to POST to. So, back to the
original design using a collection without "manages block".
Best regards,
Dietrich
Received on Sunday, 22 February 2015 16:34:39 UTC