- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Sep 2020 18:37:05 +0000
- To: public-hydra-logs@w3.org
Alternative solution proposed by @alien-mcl would be to keep the `IriTemplateMapping` and simply link the template to a shape which is an alternative description of the same graph.
```json
{
"@context": "http://www.w3.org/ns/hydra/context.jsonld",
"@type": "IriTemplate",
"template": "http://api.example.com/issues{?q}",
"variableRepresentation": "BasicRepresentation",
"hashi:shape": "ex:IssueSearchShape",
"mapping": { /* ... */ }
}
```
A client which understands SHACL extensions would find the `hashi:shape` link and use that as the description of user input.
By keeping the Hydra Core `mapping` property other clients could use that as a fallback and still produce a conforming template
--
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/215#issuecomment-692899234 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 September 2020 18:37:06 UTC