Re: [Wikidata-l] Data values

On 19.12.2012 16:57, Sven Manguard wrote: > There is a balance. The more flexible the parameters, the easier it is to put > data in, but the harder it is for computers to make useful connections with > it. > I'm not sure how to handle this, but I am sure that we can't just keep > pretending that a

Re: [Wikidata-l] Data values

On 20/12/12 11:26, Daniel Kinzler wrote: First off: our target use case is Wikipedia infoboxes. Do you have examples and numbers about the usage of such ancient units in infoboxes on wikipedia? If they are not in main stream use there, I don't see why Wikidata would have to support them. I don'

Re: [Wikidata-l] Data values

On 20 December 2012 02:20, wrote: > For me the question is how to name the precision information. Do not the XSD > facets "totalDigits" and "fractionDigits" work well enough? I mean Yes, that would be one way of modeling it. And I agree with you that, although the xsd attributes originally are d

Re: [Wikidata-l] Data values

On 19.12.2012 18:13, Gregor Hagedorn wrote: > On 19 December 2012 17:03, Daniel Kinzler wrote: >> Indeed we do: https://wikidata.org/wiki/Wikidata:Glossary >> >> I use "precision" exactly like that: significant digits when rendering >> output or >> parsing intput. It can be used to *guess* at the

Re: [Wikidata-l] Data values

On 19.12.2012 18:00, Gregor Hagedorn wrote: > Yes, Wikidata shall store a normalized version of the value, but it > also needs to store an original one. Whether it needs to store the > value twice I am not sure, I believe not. If it store the original > prefix, original unit and original significan

Re: [Wikidata-l] Data values

On 2012-12-20 12:46, Daniel Kinzler wrote: So, please suggest terms to use for at least these two things: 1) value certainty (ideally, not using "digits", but something that is independent of unit and rendering) We want to specify the "limits of (possible) variation" of a value, which woul

Re: [Wikidata-l] Data values

(Proposal 3, modified) * value (xsd:double or xsd:decimal) * unit (a wikidata item) * totalDigits (xsd:smallint) * fractionDigits (xsd:smallint) * originalUnit (a wikidata item) * originalUnitPrefix (a wikidata item) JMc: I rearranged the list a bit and suggested simpler naming JMc: Is not or

Re: [Wikidata-l] Data values

I am still trying to catch up with the whole discussion and to distill the results, both here and on the wiki. In the meanwhile, I have tried to create a prototype of how a complex model can still be entered in a simple fashion. A simple demo can be found here: Th

Re: [Wikidata-l] Data values

Thank you very much. I think this visualization will help. Just tried it and found out that entering 18 and selecting ft results in 18 ft ± 1 ft. Shouldn't it be 18 ± 0.5 ft? So it has do be divided by 2. Cheers Marco On 2012-12-20 17:10, Denny Vrandečić wrote: I am still trying to catch up

Re: [Wikidata-l] Data values

I really, really hope that this isn't the mindset of the development team as a whole. If so, my confidence in the viability of Wikidata would take a major hit. Yes, collecting the information that goes into infoboxes is going to be important, and yes, centralizing that information so that it can b

Re: [Wikidata-l] Data values

Hi, tried to enter the height of the eiffel tower. 324 meters. It suggested 324m +-100m. So i clicked on details and emptied the the +/- fields, because i do not know the upper or lower bounds. Would that have been the correct way to do it? Or should i set them to 0, even though i don't know at wh

Re: [Wikidata-l] Data values

> (Proposal 3, modified) > * value (xsd:double or xsd:decimal) > * unit (a wikidata item) > * totalDigits (xsd:smallint) > * fractionDigits (xsd:smallint) > * originalUnit (a wikidata item) > * originalUnitPrefix (a wikidata item) > JMc: I rearranged the list a bit and suggested simpler naming We

Re: [Wikidata-l] Data values

> So, please suggest terms to use for at least these two things: > > 1) value certainty (ideally, not using "digits", but something that is > independent of unit and rendering) Here we want to talk about something that the true value is with a certain probability within a given interval, something

Re: [Wikidata-l] Data values

I believe there are a lot of dangerous assumptions on http://simia.net/valueparser/ First: there is no indication in a number that it is _not_ endlessly precise. Apostles = 12 has no uncertainty, representing it as 12 ± 1 is wrong, but also 12 ± 0.5 is wrong. The same applies to a number like 1

Re: [Wikidata-l] Data values

Thanks, the prototype helps make some this more concrete. I am increasingly wondering if "uncertainty" will be overloaded here. People seem to want to use it for various types of measurement uncertainty (e.g. the standard error), ranges with no defined central value, and distributional summaries (

Re: [Wikidata-l] Data values

Not quite on topic but on the subject of uncertainty around dates I've worked with a couple of data sets where birth and death dates were unknown but activity periods [1] were known. These have either had a separate flag called is_flourished (or similar) used to modify born / died or separate fl

[Wikidata-l] next steps for the first Wikidata client - the Hungarian Wikipedia

Heya folks :) I wanted to give you a heads-up about the next steps for Wikidata deployment. In this particular case it is about the first Wikipedia actually using language links from here. A while ago we discussed this with the Hungarian Wikipedia community and they agreed to be the first to use W