Embedding links in HAL+JSON

approach 1: hal with _embedded.json

{
    "queue_status": "running",
    "_embedded": {
        "jobs": [
            {
                "_links": {
                    "self": { "href": "/queue/job1" },
                }
                "status": "queued"
            },
            {
                "_links": {
                    "self": { "href": "/queue/job2" },
                }
                "status": "running"
            },
            {
                "_links": {
                    "self": { "href": "/queue/job2" },
                    "output": { "href": "/output2" }
                }
                "status": "complete"
            }
        ]
    }
}

approach 2: hal without _embedded.json

{
    "queue_status": "running",
    "jobs": [
        {
            "_links": {
                "self": { "href": "/queue/job1" },
            }
            "status": "queued"
        },
        {
            "_links": {
                "self": { "href": "/queue/job2" },
            }
            "status": "running"
        },
        {
            "_links": {
                "self": { "href": "/queue/job2" },
                "output": { "href": "/output2" }
            }
            "status": "complete"
        }
    ]
}

So the difference is:

document._embedded.jobs[0].status
// vs..
document.jobs[0].status

Although _embedded may seem like noise, it's valuable to have HAL defined this way because it allows generic libraries/browsers to be written that can efficiently distinguish embedded resources from standard JSON properties that belong to the resource.