You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the proper method for signifying inclusion of an extension in this repository within an API? Should the full URL to the extension markdown file be added as a profile link relation? In particular I am interested in taking advantage of the value-types extension and am wondering how best to signify that fact to third party clients of my API.
Thank you for your time.
The text was updated successfully, but these errors were encountered:
keep in mind that this MUST not create a REQUIREMENT for the parser, IOW, all extensions MUST be backward-compatible. existing parsers/clients/etc MUST NOT reject a representation just because it has an extension assertion at the top.
What is the proper method for signifying inclusion of an extension in this repository within an API? Should the full URL to the extension markdown file be added as a
profile
link relation? In particular I am interested in taking advantage of the value-types extension and am wondering how best to signify that fact to third party clients of my API.Thank you for your time.
The text was updated successfully, but these errors were encountered: