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
This guideline calls for metadata to be a part of the resource tree (a path element). In practice, we are associating metadata with resources though an association. Most notable, the service-meta and data-meta association types. This is a more flexible, and arguably more intuitive approach than that prescribed in Guideline 13.
The text was updated successfully, but these errors were encountered:
The current guideline #13 is too strict, there are cases where explicitly putting meta-data in the resource path is confusing to the user/programmer. The guideline should be relaxed to state that you should provide meta-data. It should be there to help the client/user/programmer understand the API and its content. The metadata should be associated with the resource it describes. The service-meta and data-meta association types can be referenced as an example on how to do this.
This guideline calls for metadata to be a part of the resource tree (a path element). In practice, we are associating metadata with resources though an association. Most notable, the
service-meta
anddata-meta
association types. This is a more flexible, and arguably more intuitive approach than that prescribed in Guideline 13.The text was updated successfully, but these errors were encountered: