You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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: