[00:49:20] Even if it's not in software, we could systematize where we put that info. Sometimes it's in a label "(#)", other times in the description, other times on the talk page. (re @Feeglgeef: Something that might be nice is having an "intentionally disconnected" state for implementations, to differentiate between imple...) [00:59:51] We should probably pick something in the name, then it can be done by userscript (re @u99of9: Even if it's not in software, we could systematize where we put that info. Sometimes it's in a label "(#)", other times in the d...) [01:00:24] The only problem with that is that *anyone* can change it, this would be just functioneers [01:47:46] I don't mind that, we can always reverse it if we disagree. We've had cases where users are writing their first implementation and they don't want it connected yet because they want to keep working on it. (re @Feeglgeef: The only problem with that is that *anyone* can change it, this would be just functioneers) [01:56:42] Thanks for raising the question and for sharing the relevant documentation. We are eager to start ingesting Wikidata date/time and quantity, and we are currently making plans to provide that support in the coming quarter. (re @Al: Only certain types of statement are supported [[Wikifunctions:Support for Wikidata content#Notes about Wikidata statements]]. Da...) [01:58:04] @vrandecic (re @Feeglgeef: @vrandecic or David can you create the RGBA color type?) [09:10:51] We saw the ping, right now the team is busy with work, I'll try to see if they can take care of it as soon as they can (re @Feeglgeef: @vrandecic) [21:24:15] K (re @Sannita: We saw the ping, right now the team is busy with work, I'll try to see if they can take care of it as soon as they can)