Open oliverbarnes opened 3 years ago
Discussion on renaming (or not) proposals: https://github.com/liquidvotingio/api/discussions/246
Argument against using "scope": https://github.com/liquidvotingio/api/discussions/246#discussioncomment-630703
There's a flip side to that, though, and with Decidim this has already happened - everybody is confused about scopes there. Sometimes a concept is so flexible that it can mean anything, and people will always be asking for "what's a scope? give me an example" - and same goes for subject. And if people need to ask, chances are people will also be misusing it before even asking :/
Latest discussion seem to be between votables_collection_url
(and variations like votables_group_url
) and scope_url
Decidim participatory budgets integration brings up the scenario of voting on a selection of projects:
I'm thinking the API needs a proposal collection reference field for delegations that could account for different kinds of proposal buckets. This would still be external as the bucket will be platform-dependent. And the initial assumption, which we need to confirm, is that it'll have its own url.
Possible candidates:
There's also the issue of whether
proposal
itself is still a valid abstraction (say people are voting on answers rather than proposals), that perhaps precedes this. I'll open a discussion for it.