Open tpluscode opened 3 years ago
A property shape would often require selecting resources/values from existing resources. This is easy to implement in a closed setting of TopBraid Composer but requires additional plumbing so that clients have a way to fetch them from an API source
In the extension I would like to codify what I wrote down in my blog posts Hydra and SHACL - a Perfect Couple - Part 1 and Hydra and SHACL - Part 2 - IRI Templates.
On top of that I would include an additional support for hydra:freetextQuery so that an async autocomplete components can be declaratively described. For an example implementation, check https://forms.hypermedia.app/#/extensions/hydra?id=collection-filtered-with-text-input
hydra:freetextQuery
Just wondering - is it somehow related to PR 229 ?
I suppose it's the same approach but used with Property Shapes rather than Supported Properties.
And also adds the sh:path to create forms with dependant fields.
sh:path
A property shape would often require selecting resources/values from existing resources. This is easy to implement in a closed setting of TopBraid Composer but requires additional plumbing so that clients have a way to fetch them from an API source
In the extension I would like to codify what I wrote down in my blog posts Hydra and SHACL - a Perfect Couple - Part 1 and Hydra and SHACL - Part 2 - IRI Templates.
On top of that I would include an additional support for
hydra:freetextQuery
so that an async autocomplete components can be declaratively described. For an example implementation, check https://forms.hypermedia.app/#/extensions/hydra?id=collection-filtered-with-text-input