Resource type profile


#1

What do you think about an idea for adding ‘profile’ link to links section as an optional link to the resource description ?

{
“links”: {
“self”: “http://example.com/articles”,
“next”: “http://example.com/articles?page[offset]=2”,
“last”: “http://example.com/articles?page[offset]=10”,
“profile”: “http://example.com/articles/profile”,
},
“data”: [{
“type”: “articles”,

Profile resource for particular resource type could have json:api structure which could be determinate. Profile resource description should have resource meta files, like all fields with verification rules and other relation links.

Why should we need it ? For example:

  • For getting list of all fields to use it to dynamically creating models
  • for getting full list of available “actions” (which I described in other post) for resource
  • for getting validation rules…

#2

Yup, we’ll almost certainly add something like this soon, or create a mechanism for users to add any RFC 5988–compliant link. The talk about extending the capabilities of links is occuring here and in the various issues that links to.


#3

Thanks for your answer, glad that my considerations were in the right direction. Sorry I didn’t read all git stuff first.


#4

hello,
do you have examples on how the reply of GET http://example.com/articles/profile should look like?

many thanks