Minor IN the List resources, the Links are name/href pairs. This means that if you have a client widget such as a table which displays attributes (other than just the name) of, for example, assemblies it needs to retrieve the assemblies and then iterate through the LInks array retrieving the underlying entities. This is do-able, but it is very unconventional and makes the API very chatty. You would normally expect the Links entities to be actual json lists containing the attributes.
Clearly there has been a design decision to allow the implementation to be decoupled at these URIs, but this si the exception not the rule so we need to consider whether there is a way of making the general case less chatty.