This can already be done by changing JsonConfig configuration. I propose
we add a "Data" namespace to the commons. Moreover, with the recent work on
Graph extension, I was thinking of storing graphing related data there as
well. JsonConfig currently supports php-code-based validation, but adding
json-schema validation should not be too difficult.
Data:* -- accepts any valid JSON, without additional validation
Data:SubNamespace:* -- Custom validated domain-specific data
For graphs, we might have shape data as well as statistics data. So we
could declare:
Data:Graph:* -- accepts JSON that represents entire graph -- vega
grammar,
and Data:SomethingElse:* for all snippets of graphs that will be pulled
in by the vega dynamically.
Also, I could fairly easily add support for CSV and TSV if we decide that
it is needed, so that Data:Tsv:* pages would be forced to have the same
number of columns on each line.
On Wed, Aug 13, 2014 at 11:48 AM, Dario Taraborelli
<dtaraborelli(a)wikimedia.org> wrote:
There's a proposal I posted a while ago to store generic datasets that
can be represented in a tabular or JSON format in a dedicated project
namespace with dedicated handlers:
http://meta.wikimedia.org/wiki/DataNamespace
There's some good discussion on the talk page on the differences between
this type of data and structure data hosted on Wikidata and where this thing
could live (it could live on any Wikimedia wiki, including Commons or Meta).
It looks like this could be a good fit for shapefiles and I'd love to hear
your thoughts if you have a moment to read this.
Dario
On Aug 5, 2014, at 8:43, Paul Houle <ontology2(a)gmail.com> wrote:
I'm intensely interested in links to shapefiles from databases such as
Wikidata, DBpedia and Freebase. In particular I'd like to get Natural
Earth hooked up
http://www.naturalearthdata.com/
It's definitely a weakness of current generic databases that they use
the 'point GIS' model that is so popular in the social media world.
On Tue, Aug 5, 2014 at 10:14 AM, Magnus Manske
<magnusmanske(a)googlemail.com> wrote:
>
> We don't have shapefiles yet, but a lot of property types such as
> geographic coordinates (as in, one per item, ideally...), external
> identifiers (e.g. VIAF), dates, etc.
>
> A (reasonably) simple way to mass-add statements to Wikidata is this
> tool:
>
http://tools.wmflabs.org/wikidata-todo/quick_statements.php
>
> A combination of spreadsheet apps, shell commands, and/or a good text
> editor should allow you to convert many CSVs into the tool's input format.
>
> Cheers,
> Magnus
>
>
> On Tue, Aug 5, 2014 at 3:01 PM, Brylie Christopher Oxley
> <brylie(a)gnumedia.org> wrote:
>>
>> I would like to contribute data to Wikidata that is in the form of CSV
>> files,
>> geospatial shapefiles, etc.
>>
>> Is there currently, or planned, functionality to store general
>> structured data
>> on Wikidata?
>> --
>> Brylie Christopher Oxley
>>
http://gnumedia.org
>>
>> _______________________________________________
>> Wikidata-l mailing list
>> Wikidata-l(a)lists.wikimedia.org
>>
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>
>
>
> _______________________________________________
> Wikidata-l mailing list
> Wikidata-l(a)lists.wikimedia.org
>
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>
--
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254 paul.houle on Skype ontology2(a)gmail.com
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org