- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 19:12:36 +0000
- To: public-hydra-logs@w3.org
>I'm not sure the "profiles" have anything to do with dereferencability of the API descriptions. Not everything can be expressed with raw RDF terms definition - that's why the spec exists. Either profiles or levels could allow to make parts of the spec interpreted differently. While default level could have a `hydra:Resource` interpretation left as it is now (resources can be called with GET), but at different levels this _assertion_ could be relaxed or removed. >Add an optional property on ApiDocumentation to assert which profiles a server uses It might be not as easy as it sounds. There can be multiple API documentation links, what if every part provides different value? We also need something for in-lined hypermedia controls and on HTTP header level for pure JSON with JSON-LD context provided on that level. We might need to define precedence or scope of such a profile assertion. >Move the "Standard Profile" to a separate spec document. Would probably keep I don't like it - I'd prefer to keep it as it is now. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-634881009 using your GitHub account
Received on Wednesday, 27 May 2020 19:12:38 UTC