Property talk:P1181
Documentation
numerical value of a number, a mathematical constant, or a physical constant
List of violations of this constraint: Database reports/Constraint violations/P1181#Type Q11563, Q173227, Q47574, Q1441762, Q62944360, Q309314, Q82990, Q202805, Q15132612, Q63116, Q123348893, Q140774, Q3556678, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1181#Entity types
List of violations of this constraint: Database reports/Constraint violations/P1181#Scope, SPARQL
|
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||||||||||||||||||||||
physical constant
[edit]This property is intended to be used with mathematical constants. What about physical constants? Can we extend the scope of this property so that it can be used on mathematical and physical cosntants? --Pasleim (talk) 11:46, 5 October 2015 (UTC)
Support --Tobias1984 (talk) 19:36, 2 November 2015 (UTC)
Notified participants of WikiProject Physics
Notified participants of WikiProject Chemistry
Notified participants of WikiProject Astronomy
- Support of course, no big deal. author TomT0m / talk page 19:42, 2 November 2015 (UTC)
- No opposition Snipre (talk) 20:28, 2 November 2015 (UTC)
- Support There is a real need for this - however, just to be fair it's possible these should be two distinct properties, as a constraint check for being dimensionless (no units) as it has now does seem useful. I know there's some overlap, but just to be fair I'm adding a ping: ArthurPSmith (talk) 22:16, 2 November 2015 (UTC)
Notified participants of WikiProject Mathematics
@Jura1: - also pinging Jura1 as user responsible for adding the dimension constraint... ArthurPSmith (talk) 00:23, 3 November 2015 (UTC)
- Support --Almondega (talk) 23:22, 2 November 2015 (UTC)
- Support--►Cekli829 18:20, 3 November 2015 (UTC)
- So it looks like we don't have any disagreement to make this change. I think I can do the edit - here's what I would do, if anybody wants to review this change before it is made:
- Change the description to read "numerical value of a number (e.g. 1), a mathematical constant (e.g. pi), or a physical constant (e.g. speed of light)"
- Also change the Data type to "Quantity" (this has replaced Number anyway)
- Change the Domain statement as with the description to add physical constant
- Remove the "Dimensionless quantity" constraint
- Modify the "Type" constraint to add physical constant (Q173227) as allowed class
- does this seem right? ArthurPSmith (talk) 21:17, 3 November 2015 (UTC)
- Ok - the above changes have been made - except data type can't be changed (it's embedded in the property definition?) Also I added unit of measurement also as an allowed type as this seems to be frequently used. ArthurPSmith (talk) 19:20, 4 November 2015 (UTC)
- Can you add an example that involves uncertainties like the Planck constant
- --Physikerwelt (talk) 11:32, 8 November 2015 (UTC)
- Ok, I added an example with uncertainty - however it's not showing up quite right on the template page above, it doesn't seem to be pulling in the uncertainty or units. Note that there's also a problem with display of small numbers right now in wikidata (for example the Planck constant example) - see this phabricator request. ArthurPSmith (talk) 19:11, 10 November 2015 (UTC)
physiological condition
[edit]Which property should be used for physiological condition (Q7189713)-like data? See, e.g., ventricular-brain ratio (Q17141282). Is this out of scope for numeric value (P1181)? — Finn Årup Nielsen (fnielsen) (talk) 02:59, 18 January 2016 (UTC)
Unique value constraint
[edit]I find it strange that we put down a "unique value constraint" on this property. As the constraint violation report shows, there are a lot of real numbers which are the values of different physical or mathematical constants in different contexts. Should we remove the constraint? Deryck Chan (talk) 17:26, 23 April 2018 (UTC)
- But we see all "violations" (actually, exceptions) and can fix any wrong non-uniqueness (there were such cases some time ago). Let it stay. --Infovarius (talk) 10:46, 22 August 2018 (UTC)
Maximum value
[edit]Apparently, there is a maximum value around 9E124, see Help:Statements#Quantitative_values.
For a way to indicate that the value is known, but exceeds it, see Q28753965#P1181 using value known, but too large for datatype (Q54767019).
--- Jura 19:28, 5 June 2018 (UTC)
also for unit prefixes
[edit]Looks like we're also using this for unit prefixes (Q15132612) like kilo (Q107428). Makes sense. Not sure if the description needs updating to reflect this, or if an example would be useful. I updated the constraint. —Scs (talk) 12:38, 9 May 2020 (UTC)
Numerical value of convergent series
[edit]An instance of convergent series (Q1211057) should be allowed to have a numeric value (P1181), which is the number to which it converges. Helder 13:06, 7 July 2020 (UTC)
Allow links of a specific (large) number
[edit]Maybe it should allow links of a specific (large) number like the Largest known prime number item. Thingofme (talk) 15:46, 18 February 2023 (UTC)