HydraCG / Specifications

Specifications created by the Hydra W3C Community Group
Other
139 stars 26 forks source link

Enumerate supported/used operation types and properties in ApiDocumentation #59

Open lanthaler opened 10 years ago

lanthaler commented 10 years ago

_This was raised by Tomasz Pluskiewicz:_

Coming back to ApiDocumentation, I think it what the developer would use to discover the links/operation that need special care on the client. Hence my previous assumption that ApiDocumentation always contains all operations (not taking sth like Premium access into account).

lanthaler commented 10 years ago

The spec should also mention that the ApiDocumentation can be dynamic, i.e., different users might get different ApiDocumentations based on their permissions etc.