There is currently no agreement to discuss resource attributes in the Blueprint API. Close planned Description of the attributes of the message body .
But I feel that it would be a real solution that the concept of the future Blueprint API - Resource Blueprint offers to define semantic data (from a resource). Refer to an example resource .
, , , , , :
+ ip (string) ... ipv4 or ipv6 address associated with the resource
+ some-other-attribute (number, optional, `42`) ... a number of something