Lydia_Pintscher added a comment.
Geoshape properties can be added from Monday on.TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lydia_PintscherCc: Yurik, aude, Micru, Rschen7754, daniel, Esc3300, Mbch331,
Rschen7754 added a comment.
I lost track of whether it was possible to create the property yet or not.TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lydia_Pintscher, Rschen7754Cc: Yurik, aude, Micru,
Yurik added a comment.
Seems like the new property hasn't been created yet, or has it?TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lydia_Pintscher, YurikCc: Yurik, aude, Micru, Rschen7754, daniel,
Micru added a comment.
Where is the geoshape/dataset datatype being tracked? In WD it is still not available for property creation.TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lydia_Pintscher, MicruCc:
Esc3300 added a comment.
Sounds good. Here we go: https://www.wikidata.org/wiki/Wikidata:Property_proposal/geoshapeTASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lydia_Pintscher, Esc3300Cc: Yurik, aude,
Esc3300 added a comment.
Interesting point. I hadn't thought of it that way. Obviously, it's sounds somewhat optimistic that such consistency is achieved without any constraints. In theory, infoboxes could have had that too.
I think we were already hammered by the monthly (not quarterly) ratings,
daniel added a comment.
@Esc3300 Managing time-series data in Items this way is rather limited. You can't easily have multiple columns, you have to repeat the source references, and the whole thing does not scale well. I would not recommend to put more that 20 statements into a time series on a
Esc3300 added a comment.
Currently we already have tabular data at Wikidata, e.g. for population numbers and quarterly ELO ratings.
These are fairly straight-forward:
date
value
some qualifier about the type of value (optional or omitted)
This for each item.
Obviously, the same could be
daniel added a comment.
@Esc3300 The problem with infoboxes is a) that they exist once per language version and b) they are hard to parse to get the data. Neither of those problems exists with the new tabular data sets on commons.
Also note that we have said from the beginning that we explicitly
Esc3300 added a comment.
Maybe I should clarify that I don't really mind geoshapes to be stored at Commons, I'm worried about tables of other data. The risk is that we start the Wikipedia Infobox problem once more.TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL
Yurik added a comment.
I think the description needs to be updated - it IS possible to store data :)TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: YurikCc: Yurik, aude, Micru, Rschen7754, daniel, Esc3300,
Esc3300 added a comment.
Nothing is easy, but if we don't try, it's unlikely it will ever happen ..TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Esc3300Cc: aude, Micru, Rschen7754, daniel, Esc3300,
Micru added a comment.
@Esc3300 There is data that cannot be modeled easily in WD, like geodata and climate data, and this is the ideal complement.TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: MicruCc:
Esc3300 added a comment.
I hope this doesn't lead to tons of unstructured data (read: data not structured Wikidata form)TASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Esc3300Cc: aude, Micru, Rschen7754,
Micru added a comment.
Structured datasets are officially available on Commons:
https://lists.wikimedia.org/pipermail/wikitech-l/2016-December/087313.htmlTASK DETAILhttps://phabricator.wikimedia.org/T151334EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
aude added a comment.
I think the data types should be separate. As a consumer of the data (e.g. json dump), I might want to find all the shapes or search/query on them in a different way (or also render them differently) I think such would be easier with the separate data types.TASK
daniel added a comment.
I vote for separate data types for maps, tabular data (and media files). The purpose of data types is to defined the semantics of a value, and thereby determine how a value is displayed and edited. I'd like to have the option to show shapes and tables in different ways,
17 matches
Mail list logo
