mkroetzsch added a comment. On another note, it would be good if the view on all data that is in the system is somewhat uniform. We don't want special query syntax for badges etc. This could be avoided by viewing everything as statements, possibly using some "special" properties (and qualifiers). For example, a label can be structurally represented like a statement for a property of type monolingual text. A sitelink could be represented as a statement with main property pointing to the article title and a qualifier defining the site. Doing this does not change the data, but it would unify the query syntax.
Something that should *not* be represented in the query service is order. The order of statements relative to other statements (of the same property or not), the order of qualifiers, the order of reference snaks in a reference, the order of aliases -- none of this should play a role in query answering as such. Whan displaying data, it could still use the order as in Wikidata, but this is not related to indexing (e.g., it should not be possible to search for entities with third alias starting with "a" and the fifth statement from the top being about property https://phabricator.wikimedia.org/P31). TASK DETAIL https://phabricator.wikimedia.org/T86278 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Smalyshev, mkroetzsch Cc: Aklapper, Smalyshev, Lydia_Pintscher, Multichill, Magnus, daniel, JeroenDeDauw, JanZerebecki, aude, mkroetzsch, Denny, Sjoerddebruin, Tobi_WMDE_SW, jkroll, Wikidata-bugs, GWicke, Manybubbles _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
