Sven,
To complement your thought, and for an historical perspective influencing this discussion, UNIX has many plusses and minuses informed by the computer science of the 1950s and 1960s, and it would be great to anticipate as many 'plusses' as possible, and as sophisticatedly as possible, in the development of Wikidata et al. in the 2010s, especially in terms of values such as geolocation, - for example, with both virtual worlds and brainwave headsets (so, neural interfaces ... e.g. see Tan Le's TED Talk), but in many other ways, as I see it - which is why Denny is asking.
Scott
On Tue, Dec 18, 2012 at 9:24 AM, Sven Manguard svenmanguard@gmail.comwrote:
The great thing about MediaWiki is that we don't have to anticipate new features, we can build them in later when we discover that they're possible and that they're wanted. In fact, there's no requirement that the Wikidata developers are even the ones that do develop said hypothetical future modules. If you could code, you could build them and offer them up for integration.
All that being said, there are already websites that map out astronomical features in a geolocation-like way. It's worthwhile to consider supporting that type of geolocation data on Wikidata.
Sven
On Tue, Dec 18, 2012 at 12:14 PM, Scott MacLeod < worlduniversityandschool@gmail.com> wrote:
Denny,
Thanks for this.
Are there ways to structure this geolocation data now to anticipate more 'fluid' uses of it, say 5 or 10 years from now, or beyond, in representing water, or astronomical processes, in something like interactive, realistic models of the earth or the universe, which would also be useful to Wikipedia's developing goals / mission?
Scott
On Tue, Dec 18, 2012 at 8:57 AM, Gregor Hagedorn g.m.hagedorn@gmail.comwrote:
Now, I don't think we need or want ranges as a data type at all
(better have
separate properties for the beginning and end).
I am afraid this will then put a heavy burden on users to enter, proofread, and output values. Data input becomes dispersed, because the value "18-25 cm length " has to be split and entered separately. You have to write a custom output for each property then, and do all the query logic (> lower, < upper) for each property in each Wikipedia client.
I believe this is something that is healthy to do centrally. I believe the concept of intervals exists because of that.
Gregor
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
--
Scott MacLeod Founder & President
-- World University and School (like Wikipedia with MIT Open Course Ware)
http://worlduniversityandschool.blogspot.com/
http://worlduniversity.wikia.com/wiki/World_University
P.O. Box 442, (86 Ridgecrest Road), Canyon, CA 94516
415 480 4577 worlduniversityandschool@gmail.com Skype: scottm100
Google + main, WUaS pages: https://plus.google.com/u/0/115890623333932577910/posts
https://plus.google.com/u/0/b/108179352492243955816/108179352492243955816/po...
Please contribute, and invite friends to contribute, tax deductibly, via PayPal and credit card:
http://scottmacleod.com/worlduniversityandschool.htm
World University and School is a 501 (c) (3) tax-exempt educational organization.
World University and School is sending you this because of your interest in free, online, higher education. If you don't want to receive these, please reply with 'remove' in the subject line. Thank you.
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l