Master-detail view in Json-LD

Note: part of Hydra's answers I'm not sure about is JSON-LD and REST I guess.

You can use @base

relative IRIs from JSON-LD as well, or you can define namespaces in @context

, so after that you can use relative IRIs like ns:relativeIRI

. Each one is better than returning a full IRI. (It is easier to parse the results with a generic client-side JSON-LD parser rather than a simple JSON parser.)

You can define your own @vocab

using the Diva guide, or you can add definitions for "actions" in @context

. If you want to "add actions" you must use subcategories hydra:Operation

in your vocab. Something like this (but I'm not a Hydra expert):

{
    "@id": "vocab:ProductList",
    //...
    "hydra:supportedOperations": [
        {
            "@type": "hydra:CreateResourceOperation",
            "method": "POST",
            "expects": "vocab:Product"
        }
        //...
    ]
}

      

        
        
        
      

    

Generally, the REST, if you need the same resource with fewer features, you need to add a new IRI for this resource, for example: /myresource?fewer=1

. For example, in your case: /api/products/?fields="id, price, name"

ok.

By Hydra you have 2 options if you want multiple links; you can add a new one hydra:Link

as a property, or you can add a new one hydra:Operation

as a supportedOperation

with method: GET

. I assume the operations are done for something like a search that has user input, but if you don't want to add a new property for each link, I think you have no other choice.

In fact, Hydra has link and operation support. It may be confusing, but JSON-LD is an RDF format, you can define three times in RDF. So the IRIs you used for example "customers":"www.myshop.com/api/customers"

are just resource IDs, not links. The link must have an IRI, title, method (GET), language, content-type, iana: relation, etc., so it is not possible to describe a link that you can follow with only one IRI (resource identifier). When processing a REST resource, the client should never check the IRI structure to know how to display what it received from you. You have to check other properties of the links, especially iana: relations or Hydra, perhaps the type of operation to do this. So, for example, in your casewww.myshop.com/api/dav8ufg723udvbquacvd723fudvg

is a perfectly valid IRI for a client list. We only use good IRIs because they are easier to configure by generating them on the server side and setting up a router for them.

Check Hydra vocab before additional questions . As you can see, Class

can have supportedOperations

and supportedProperties

, which are both collections. A Link

is a subclass Property

that can have one Operation

. For collections, I think you should use a class Collection

that member

contains the elements of the collection ... Please be aware that JSON-LD makes no difference defining one element or multiple elements with the same type. In context, you only need to define the type, and the property value can contain either a single element or an array of elements ... If you want to constrain this, I think you need to add some OWL styles and a validator that validates the values ​​using them.