- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 07:39:19 +0000
- To: public-hydra-logs@w3.org
I would definitely have 1️⃣ over 2️⃣ --- The third point however I find rather orthogonal. I'm not sure the "profiles" have anything to do with dereferencability of the API descriptions. More about the requirements from the client. I would see this as an open-ended set of "feature-packs" that a server may implement in addition to core. Here are some ideas: 1. Hydra Core * Only the base terms to put an API together 2. Standard Profile * hydra:Class 2. SHACL profile * Shapes for `expects`/`returns` * maybe also `supportedClass` 3. JSON Schema profile * like SHACL, uses a different vehicle to describe requests and responses 4. IANA Media types profile * Uses IANA-registered media types. for example the snippet below might denote an operation where PNG and JPG are allowed to be uploaded ``` <> hydra:expects <https://www.iana.org/assignments/media-types/image/png> , <https://www.iana.org/assignments/media-types/image/jpeg> , ``` 5. Multi-part profile * Something we discussed in #199 where an operation is described as expediting a `multipart/form-data` body. * Individual parts could then be individually describe using the other profiles. For example to have one part image (IANA profile) and the other a plain RDF resource (Standard profile) Each profile would be free to define its specific processing rules. The required changes would be to: 1. Add an optional property on `ApiDocumentation` to assert which profiles a server uses 2. Move the "Standard Profile" to a separate spec document. Would probably keep So as effect a server might announce itself as ```turtle <> a hydra:ApiDocumentation ; // SHACL might potential be maintained by Hydra CG hydra:profile <http://www.w3.org/ns/hydra/profile#SHACL> ; // a vendor-specific profile which somehow bridges Open API hydra:profile <http://example.com/hydra-profile#OpenAPI> ``` -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-634486520 using your GitHub account
Received on Wednesday, 27 May 2020 07:39:21 UTC