Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

Use-case : xxx:searchWidget #26

Open
tfrancart opened this issue Oct 4, 2023 · 2 comments
Open

Use-case : xxx:searchWidget #26

tfrancart opened this issue Oct 4, 2023 · 2 comments

Comments

@tfrancart
Copy link
Contributor

See #16 for the complete story.
See #24 for naming question.

  • I need to be able to associate a xxxx:searchWidget (or xxx:filter) to property shapes to indicate which value selection widget should be used to assert a criteria on this property
  • and I need to be able to specify SearchWidgets / Filters
@bergos
Copy link
Member

bergos commented Oct 16, 2023

@tfrancart can you please provide an example given as Turtle? Maybe you can also give more context based on that example. I think that would be useful for further discussions.

@tfrancart
Copy link
Contributor Author

This has been discussed already, with more detailled issues like #24, and is in the scope of work of this group ("It covers viewing, editing and filtering RDF data"). This is about the "filtering" part.

What I mean by "I need to be able to specify SearchWidgets / Filters" is the following: I am assuming some widgets can be parameterized. For example a map selection widget could be parameterized by the lat/long/zoom of its initial display area. In some other situations parameters can be read from the model, like minimum values and maximum values of a slider widget (so, in that case probably no need for additional parameters.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants