Meta property on resources about swapi HOT 3 OPEN

Maybe for created and edited, but the url attribute it vital for HATEOAS and I personally think it should be a direct attribute on the resource and not nested.

from swapi.

I'd agree with the view that the "self" URL is special.

I've done both things... adding it as the first property on a resource, and also adding it as a "self" URL on a list of links about the resource (taking the view that philosophically the URL doesn't really describe the resource but is a property of the system storing the resource)

Example of a "meta" object on a large and complex API:

"meta":{
   "created": "2013-04-11T05:52:46.362755Z",
   "createdBy": {
      ...
   },
   "flags": {
      "sticky": false,
      "open": true,
      "deleted": false,
      "moderated": false,
      "unread": true
   },
   "links":[
      {"rel":"self", "href":"/api/foos/1"},
   ],
   "permissions":{
      "create":false,
      "read":true,
      "update":false,
      "delete":false
   }
}

from swapi.

I think Meta is okay for the created and updated values. Accepted this into version 2 (whenever I find spare time to roll that out)

We don't need anything like permissions as we can just call the HTTP HEAD method on the resource and determine the CRUD actions based on the allowed HTTP methods. Also, swapi only supports GET anyway.

from swapi.