Change Details

**Feature summary** (what you would like to be able to do and where): I want to set a prefix in the dashboard that'll be used to generate and apply local standard WDQS prefixes. This would be pre-populated with a name-based suggestion for new instances, but could be modified afterwards. **Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution): When you want to write queries on Wikibase.cloud currently, [you have to specify your own prefixes](https://furry.wikibase.cloud/wiki/Project:SPARQL/examples), or else use a full URI. [Default Wikibase-specific prefixes are from Wikidata](https://furry.wikibase.cloud/query/sparql?query=SELECT%20*%20WHERE%20%7B%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%2Cen%22.%20%7D%20%7D%0ALIMIT%20100&explain); some of these are added when the "Add Standard Prefixes" option is selected in the Prefixes 📌 menu. Some users have taken to manually redefining standard prefixes such as wdt: or p:. The autosuggestion CTRL-SPACE after a prefix is entered also seems to assume that this will be done. However this is bound to lead to confusion when others are reading or writing queries, or when it comes to federated queries, and is not in line with how other well-known prefixes are treated. Instead, I suggest creating new prefixes based on a master prefix associated with the instance, to replace 'wd' where it was in a prefix already, or else add to it; e.g. if the site prefix is 'wfd' for WikiFur Data then 'wdt' becomes 'wfdt', while 'p' becomes 'wfdp'. These wouldn't necessarily be unique, though it may be worth considering this in order to facilitate future federated queries between Wikibase.cloud instances. (Perhaps just warn that it is shared by X wikis if naming then is a privacy concern.) Prefixes could be suggested based on capital letters in the name, as well as the first letter after a space or hyphen or the start of the name, in case they don't use capitals. This concept could be introduced through the onboarding workflow, and added or reconfigured later in the dashboard for existing Wikibase.cloud instances. **Benefits** (why should this be implemented?): By doing this, there would be no more confusion about what 'wdt:' means on Wikibase.cloud, or what prefixes are required to write a query. By placing it in onboarding, perhaps using an example with the prefix, users will be introduced to the concept of using local prefixes for queries rather than Wikidata ones. Existing prefixes would continue to work, while new ones can be remembered easily if you know the prefix, or if you add the standard prefixes to a query, since they'd be there in addition to the ones for Wikidata. (Ideally, related issues T296451, T317109 and [Cradle's wdt: dependency](https://github.com/wbstack/cradle/issues/2#issuecomment-818352157) would be addressed too.)

**Feature summary** (what you would like to be able to do and where): I want to set a prefix in the dashboard that'll be used to generate and apply local standard WDQS prefixes. This would be pre-populated with a name-based suggestion for new instances, but could be modified afterwards. **Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution): When you want to write queries on Wikibase.cloud currently, [you have to specify your own prefixes](https://furry.wikibase.cloud/wiki/Project:SPARQL/examples), or else use a full URI. [Default Wikibase-specific prefixes are from Wikidata](https://furry.wikibase.cloud/query/sparql?query=SELECT%20*%20WHERE%20%7B%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%2Cen%22.%20%7D%20%7D%0ALIMIT%20100&explain); some of these are added when the "Add Standard Prefixes" option is selected in the Prefixes 📌 menu. Some users have taken to manually redefining standard prefixes such as wdt: or p:. The autosuggestion CTRL-SPACE after a prefix is entered also seems to assume that this will be done. However this is bound to lead to confusion when others are reading or writing queries, or when it comes to federated queries, and is not in line with how other well-known prefixes are treated. Instead, I suggest creating new prefixes based on a master prefix associated with the instance, to replace 'wd' where it was in a prefix already, or else add to it; e.g. if the site prefix is 'wfd' for WikiFur Data then 'wdt' becomes 'wfdt', while 'p' becomes 'wfdp'. These wouldn't necessarily be unique, though it may be worth considering this in order to facilitate future federated queries between Wikibase.cloud instances. (Perhaps just warn that it is shared by X wikis if naming then is a privacy concern.) Prefixes could be suggested based on capital letters in the name, as well as the first letter after a space or hyphen or the start of the name, in case they don't use capitals. This concept could be introduced through the onboarding workflow, and added or reconfigured later in the dashboard for existing Wikibase.cloud instances. **Benefits** (why should this be implemented?): By doing this, there would be no more confusion about what 'wdt:' means on Wikibase.cloud, or what prefixes are required to write a query. By placing it in onboarding, perhaps using an example with the prefix, users will be introduced to the concept of using local prefixes for queries rather than Wikidata ones. Existing prefixes would continue to work, while new ones can be remembered easily if you know the prefix, or if you add the standard prefixes to a query, since they'd be there in addition to the ones for Wikidata. (Ideally, related issues T296451, T317109 and [Cradle's wdt: dependency](https://github.com/wbstack/cradle/issues/2#issuecomment-818352157) would be addressed too. See also T211799 for the more general case of prefixes in the WDQS front-end.)

**Feature summary** (what you would like to be able to do and where): I want to set a prefix in the dashboard that'll be used to generate and apply local standard WDQS prefixes. This would be pre-populated with a name-based suggestion for new instances, but could be modified afterwards. **Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution): When you want to write queries on Wikibase.cloud currently, [you have to specify your own prefixes](https://furry.wikibase.cloud/wiki/Project:SPARQL/examples), or else use a full URI. [Default Wikibase-specific prefixes are from Wikidata](https://furry.wikibase.cloud/query/sparql?query=SELECT%20*%20WHERE%20%7B%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%2Cen%22.%20%7D%20%7D%0ALIMIT%20100&explain); some of these are added when the "Add Standard Prefixes" option is selected in the Prefixes 📌 menu. Some users have taken to manually redefining standard prefixes such as wdt: or p:. The autosuggestion CTRL-SPACE after a prefix is entered also seems to assume that this will be done. However this is bound to lead to confusion when others are reading or writing queries, or when it comes to federated queries, and is not in line with how other well-known prefixes are treated. Instead, I suggest creating new prefixes based on a master prefix associated with the instance, to replace 'wd' where it was in a prefix already, or else add to it; e.g. if the site prefix is 'wfd' for WikiFur Data then 'wdt' becomes 'wfdt', while 'p' becomes 'wfdp'. These wouldn't necessarily be unique, though it may be worth considering this in order to facilitate future federated queries between Wikibase.cloud instances. (Perhaps just warn that it is shared by X wikis if naming then is a privacy concern.) Prefixes could be suggested based on capital letters in the name, as well as the first letter after a space or hyphen or the start of the name, in case they don't use capitals. This concept could be introduced through the onboarding workflow, and added or reconfigured later in the dashboard for existing Wikibase.cloud instances. **Benefits** (why should this be implemented?): By doing this, there would be no more confusion about what 'wdt:' means on Wikibase.cloud, or what prefixes are required to write a query. By placing it in onboarding, perhaps using an example with the prefix, users will be introduced to the concept of using local prefixes for queries rather than Wikidata ones. Existing prefixes would continue to work, while new ones can be remembered easily if you know the prefix, or if you add the standard prefixes to a query, since they'd be there in addition to the ones for Wikidata. (Ideally, related issues T296451, T317109 and [Cradle's wdt: dependency](https://github.com/wbstack/cradle/issues/2#issuecomment-818352157) would be addressed too. See also T211799 for the more general case of prefixes in the WDQS front-end.)