[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2019-10-23 Thread Bugreporter
Bugreporter added a comment. If structured data are added to global user pages, we probably need to make a page possible to not have a main slot (as not everyone have a user page). It might also be possible to delete only some specific slots. TASK DETAIL

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2019-06-11 Thread dbarratt
dbarratt added a comment. I suppose now that we have MCR this could be rephrased as: "Adding structured data to //global// user pages" much like #structureddataoncommons adds structured data to global files. TASK DETAIL

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2018-07-11 Thread dbarratt
dbarratt added a comment. In T173145#4416819, @daniel wrote: Unless you want free form modeling of users. I think that's fine. I'm assuming the properties though, would be unique to U on meta.TASK DETAILhttps://phabricator.wikimedia.org/T173145EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2018-07-11 Thread daniel
daniel added a comment. Quiet a few things use JSON based content models to store structured data. Sadly, they tend to not have good UI. So that would need to be written. But that would also need to be written when basing this on Wikibase. Unless you want free form modeling of users.TASK

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2018-07-11 Thread dbarratt
dbarratt added a comment. I'm certainly open to alternative solutions. It just felt like, of content models that we currently have (unstructured pages, form fields tied to database fields, wikibase, something else?) it was the best option I could think of.TASK

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2018-07-11 Thread daniel
daniel added a comment. I don't quite get the rationale behind this. There seems to be an idea that Wikibase is the preferred mechanism for storing structured data in MediaWiki. That's a bit off. Wikibase is a knowledge modeling tool. It's a good choice if you want to enable users to freely make

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2017-08-23 Thread dbarratt
dbarratt added a comment. In T173145#3546575, @Lydia_Pintscher wrote: It'd still require decisions and work from the Wikidata team so please keep it on our board. Apologies!TASK DETAILhttps://phabricator.wikimedia.org/T173145EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2017-08-23 Thread dbarratt
dbarratt added a comment. In T173145#3546539, @MarcoAurelio wrote: Well, I don't get this. Why do we want to flood Wikidata with items about users? Does not make sense to me... We already decided this would be on Meta, not Wikidata.TASK DETAILhttps://phabricator.wikimedia.org/T173145EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2017-08-23 Thread MarcoAurelio
MarcoAurelio added a comment. Well, I don't get this. Why do we want to flood Wikidata with items about users? Does not make sense to me...TASK DETAILhttps://phabricator.wikimedia.org/T173145EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: MarcoAurelioCc:

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2017-08-19 Thread Lydia_Pintscher
Lydia_Pintscher added a comment. Folks, I think we can let this rest. It will require more product and development resources than I am willing to put into it anytime soon.TASK DETAILhttps://phabricator.wikimedia.org/T173145EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T173145: Global users should be Wikibase items on Meta

2017-08-18 Thread dbarratt
dbarratt added a comment. In T173145#3534245, @Legoktm wrote: Anyways, my two cents on this is that this seems like a solution in search of a problem. If you want to extract info out of {{user info}} or something, then consider adding some semantic markup that makes it easy to parse or have it