mkroetzsch added a comment. @thiemowmde One could have documentation as a text that is added as a description of the property used for precision. However, most users would more likely read a web page than look up the description stored in an OWL file. In the end, when you type in a SPARQL query, there is not much documentation directly available to you, even if it is stored in the RDF database somewhere.
Since our main use of RDF is query answering, I would not see readability as its main requirement, but of course it would be nice to retain this too. One could replace the numbers by strings of the form "08=decade" and "11=day" that would sort as expected while still having some readability. It should be checked if this has a negative impact on the store performance, but in general this should be workable. On the other hand, maybe we are worrying too much about readability here. All of our RDF uses opaque IDs like "https://phabricator.wikimedia.org/P345"; and "Q123456" in combination with several URI prefixes that have specific (not self-explaining) meanings. SPARQL queries based on this vocabulary in general are not readable to uninitiated users. Making the rarely used precision constants readable among all the other unreadable IDs might not add much to usability overall. Maybe it would be more promising to focus on suitable query building interfaces that show human readable labels instead of ids. This would also be much more useful internationally, because English labels hardcoded in URIs would not always be helpful. TASK DETAIL https://phabricator.wikimedia.org/T99907 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: mkroetzsch Cc: mkroetzsch, Smalyshev, daniel, thiemowmde, Aklapper, Wikidata-bugs, aude _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
