-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use SHACL for IriTemplate
mappings
#215
Comments
Let's keep the discussion separate for SHACL for |
Alternative solution proposed by @alien-mcl would be to keep the {
"@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 By keeping the Hydra Core |
I think that's an elegant solution. 👌 |
Oh, what about
IriTemplate
mappings. Maybe they could also be described with a Shape?The entire mappings could easily be swapped with a Shape, provided that individual
PropertyShapes
have an additional variable name which use use currently.Here's an idea for changing EXAMPLE 19 from the spec
Little has to change conceptually.
hydra:IriTemplateMapping -> sh:PropertyShape
hydra:variable
used withsh:PropertyShape
hydra:property -> sh:path
hydra:required -> sh:minCount
Of course, some limitations could be imposed for practical reasons:
Originally posted by @tpluscode in Native SHACL support #214 (comment)
The text was updated successfully, but these errors were encountered: