Hydra W3C Community Group Telecon
Minutes for 2019-11-12
- Agenda
- https://www.w3.org/community/hydra/wiki/Conference_Calls#2019-09-03
- Topics
- Action Items
- Chair
- Karol Szczepański
- Scribe
- Angelo Valtens
- Present
- Karol Szczepański, Tomasz Pluskiewicz
- Audio Log
Karol Szczepański: Meeting: Hydra W3C Community Group Conference Call
Topic: Get a grip on collection ordering issue #172
Karol Szczepański: https://github.com/HydraCG/Specifications/issues/172
Karol Szczepański: Ordering touches the querying topic. Not sure if this should be in hydra core, but should at least be extendible
Tomasz Pluskiewicz: https://prefix.zazuko.com/dtype:orderIndex
Karol Szczepański: 2 possible solutions: Rising hydra:Collection to some kind of SortedCollection, impliying that the members are RDF Lists
... or leave it as is and provide a description of the ordering
... would be cautious with adding something to members
... like indices
Karol Szczepański: aveltens: I'm not sure what kind of use case Pieter has on his mind
Tomasz Pluskiewicz: i.e. for UI building, client would need to be sure on how the members are sorted [scribe assist by Karol Szczepański]
Karol Szczepański: The client could define an order in the query and expect the API to serve in that order
... same es an SQL or SPARQL queries
Tomasz Pluskiewicz: The server should be able to indicate the order to the client, even if the client did not ask for a specific order
... if the response is ordered, the server should return an RDF list
Karol Szczepański: Pieters proposol is quite complex, introducing many new predicates / classes
... I prefer having quering for order as a stanard
Tomasz Pluskiewicz: The client nontheless needs to understand what it got. Perhaps it followed only a parameterized link and does not understand what order it requested
Karol Szczepański: Even if a link is follows / refresh is done, the client will request a specific order based on it's state and knows about the order
Tomasz Pluskiewicz: There are several issues here. What if the server implemention changed meanwhile?
Angelo Valtens: The client would look up the API doc to know how to construct the query?
Karol Szczepański: We have to very different concepts. Querying the data vs shaping the data. Which path should we use? What are the benefits of each?
Tomasz Pluskiewicz: What about a resource /people, and the server orders them implicitly by name
... its not about what the server has to do, but what the server did
Karol Szczepański: If client knows what it needs, let it ask for it, unless it should not care
Karol Szczepański: let us craft some imaginatory situations in the cookbook
... lets link those examples / use cases to the issue
ACTION: Karol will provide example for the querying approach
Tomasz Pluskiewicz: Still, Pieter is asking for the complete opposite, Indicate a partial collection view is ordered