tripu
tripu
> _“As you suggested I think we should change those anchors and use the user id (an info we are already exposing in the API), the issue is that it...
Ditto about the participations of the special group that is the Advisory Board: seems the only group for which retrieving participations errors: [`https://api.w3.org/groups/7756/participations?embed=true`](https://api.w3.org/groups/7756/participations?embed=true).
It's happening with other groups (not only with the AB); see participations of the Web Security IG: [`https://api.w3.org/groups/49310/participations?embed=true`](https://api.w3.org/groups/49310/participations?embed=true).
(I think @vivienlacourba told me that yes, it's reasonable, but not a trivial feature to add.)
Any idea if/when this could be tackled…?
https://api-platform.com/ to the rescue…?
[`https://api.w3.org/functions`](https://api.w3.org/functions) seems ordered by IDs; not numerically but lexicographically. I suggest order by title instead.
[`https://api.w3.org/groups/55181/participations?embed=true`](https://api.w3.org/groups/55181/participations?embed=true) seems also sorted by numeric ID, but lexicographically (eg, `10` < `9`), which is of little use.
I have a vested interest in having human-friendly sorting implemented server-side (for my API clients). But, to be honest, pagination doesn't need friendly sorting — it just needs to be deterministic, predictable....
@jean-gui: OK, understood. I'll wait for you guys to evaluate this feature request, then.