- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Jul 2020 23:28:31 +0000
- To: public-dxwg-wg@w3.org
@riccardoAlbertoni - i think the problem is the assumption that a dataset has exactly one meaningful query - either its a very unusual case and perhaps not important for the wider community, or queries are very common in which case a single query is unlikely to work very well - too much interoperability loss by overloading the intention for related cases. I could imagine a generic templated query object that is a qualified association whereby you can define the model profile the query uses with dct:conformsTo - and examples for things in the Web architecture 'canon' - such as URL templating and Opensearch. I have seen the void:sparqlEndpoint but never found an interoperability based use for it except in conjunction with some query model, (outside "i want a Linked Data star" or experimental "play with SPARQL" motivations) . Its not that useful to have such a scalar property in practice AFAICT, but perhaps a canonical qualified relation is probably a good thing. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1230#issuecomment-659732473 using your GitHub account
Received on Thursday, 16 July 2020 23:28:33 UTC