Rob Sanderson
Rob Sanderson
Also, mea culpa! (blush)
I get this error also: ``` PREFIX crm: PREFIX lux: SELECT DISTINCT ?what ?txt ?atxt WHERE { ?what a crm:E22_Human-Made_Object ; lux:primaryName ?txt ; lux:agentOfProduction ?artist . ?artist lux:primaryName ?atxt...
Pinging this issue. Words with 3 or fewer characters still cause the query to fail as of 2025-06-29 Could this be related to #1534 ?
Can the camera move and/or change focal length to ensure that the looked at thing is visible? Especially if the looked at thing is animated or otherwise dynamically transformed?
Thanks for discussing it! I think we can close this particular issue -- the pre-flight does indeed solve the issue, and implementation notes in various specs in future versions could...
Or that the `DATE_FORMATS` setting have the timezone-less options by default (having re-found that particular setting)
Related to #2280 & #2271
Eg. move to end of cretaceous period and let the user fly around. Then hit play to start time up again.
Thanks Tim :) My 2015 understanding of good practice and the 2024 understanding are definitely different on that particular topic, and the differences (I think) come from the renewed emphasis...
I think the specification is somewhere between misleading and flat out wrong here. We need a registry of additional rights URIs with an explanation of what a client should do...