Should returns and statusCodes be removed to avoid tight coupling?

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group

Other

138 stars 26 forks source link

Should returns and statusCodes be removed to avoid tight coupling? #175

Closed alien-mcl closed 5 years ago

alien-mcl commented 5 years ago

There was already a paragraph that mentioned a volatile character of ApiDocumentation, which I've extended with direct references to hydra:returns and hydra:statusCodes hoping it will make the #32 resolved.