Could someone give an example of how to use "profile" link with hal+json format? I would like to see how it appears in the resource representation and how the profile reprensetation might look like. Am I allowed to include anything i want in the profile? Like insertable, updateable, type, maxLength etc. Can the format of the profile be plain json?

B.1. How should a client know the meaning/structure/semantics/type of a resource? There are two main approaches to solving this problem. Both involve exposing additional documentation describing the resource which may be human and/or machine readable (i.e. an HTML page and/or a JSON Schema document). The difference between the two approaches is in where that URI is shared with the client, which is either: (1) The URI that was the preceding link relation type. (2) A 'profile' link from the resource itself.**

.txt