Property talk:P2575

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

measures
physical quantity that this device measures

Represents	physical quantity (Q107715), measurement (Q12453), measurand (Q1924249)
Data type	Item
Domain	measurement tool (Q1047213)
Example	voltmeter (Q179741) → voltage (Q25428) Kibble balance (Q27203) → mass (Q11423)
Tracking: usage	Category:Pages using Wikidata property P2575 (Q107212542)
See also	measured physical quantity (P111), key performance indicator (P6563)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P2575 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 328 Main statement 325 99.1% of uses Qualifier 2 0.6% of uses Reference 1 0.3% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “measurement tool (Q1047213)”: item must contain property “instance of (P31), subclass of (P279)” with classes “measurement tool (Q1047213)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2575#Type Q1047213, SPARQL

Value type “individual quantity (Q71550118)”: This property should use items as value that contain property “subclass of (P279)”. On these, the value for subclass of (P279) should be an item that uses subclass of (P279) with value individual quantity (Q71550118) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2575#Value type Q71550118, SPARQL

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2575#Scope, SPARQL

Property “ISQ dimension (P4020)” declared by target items of “measures (P2575)”: If [item A] has this property with value [item B], [item B] is required to have property “ISQ dimension (P4020)”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2575#Target required claim P4020, SPARQL, SPARQL (by value)

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2575#Entity types

This property is being used by: ca:Plantilla:Infotaula eina Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Extend property to measurements in tests, questionnaires and the like?

Instead of creating a new property, this one seems good enough to link tests (such as visual acuity test (Q17141574)) to what they measure. Anyone is against this? The other solution would be to add a new property to Wikidata.TiagoLubiana (talk) 14:27, 12 September 2021 (UTC)

Right now we restrict the values to physical quantities. What other kinds of results are you considering? Toni 001 (talk) 09:20, 13 September 2021 (UTC)

Easy: everthing that is an analytical technique (Q4751159) as they produce measurands. Any measurand has a physical dimension or is a dimensionless constant. So I added analytical technique (Q4751159) to the object type constraint. --SCIdude (talk) 15:53, 5 February 2022 (UTC)

@TiagoLubiana, SCIdude, Toni 001 - I'm also intersted in this from the point of view of psychological tests (example: Yale–Brown Obsessive Compulsive Scale (Q4330010)). These currently use "main subject" but "measures" seems more intuitive to interpret (current list in WD). What are people's thoughts? Such uses would also completely violate the ISQ value-requires-statement constraint! T.Shafee(evo&evo) (talk) 01:56, 14 March 2023 (UTC)

This should be a different property: A physical quantity and an analytical technique are different kinds of things. Toni 001 (talk) 04:58, 14 March 2023 (UTC)

@Toni 001 Do you have a feel for how the two properties should be named for clarity? E.g. This property (P2575) -> "measures physical quantity" and a new property for "measures"? Current examples mostly from current property usage:

• computer benchmarking (Q104537917) measures computer performance (Q1197550)
• oxygen sensor (Q286588) measures concentration (Q3686031)
• Yale–Brown Obsessive Compulsive Scale (Q4330010) measures Yale–Brown Obsessive Compulsive Scale (Q4330010)
• eye chart (Q1094496) measures visual acuity (Q555066)
• hardness test (Q25456031) measures hardness (Q3236003)
• Shore durometer (Q55714258) measures Shore durometery (Q2035690)

E.g. Hardness is a physical quantity, whereas Shore durometery is a specific hardness metric as measured by a particular analytical technique. T.Shafee(evo&evo) (talk) 05:51, 20 March 2023 (UTC)

To answer this question one would need some better examples for the proposed other property: Take for instance your third example, Q4330010, which is a scale. One does not "measure" a scale. Rather, a scale can be used to define a quantity to be measured.

The last example, Q2035690, is currently labeled "Shore durometery" in English. "Durometry" is the practice of measuring hardness. One does not "measure" durometry, but rather the hardness defined by some hardness scale.

In the end, it seems that for each of those items there could be some corresponding "physical quantity" item which is acceptable for this property (P2575). (See for instance the nicely distinguished concepts of Celsius temperature scale (Q110748751), Celsius temperature (Q74758530) and degree Celsius (Q25267) - the second of which is acceptable for this property.) Toni 001 (talk) 07:41, 21 March 2023 (UTC)

subclass of measurement should not need to repeat dimension

At the moment the statement Q110820747#P2575 is flagged because the measurand misses a dimension. But see Q110820735#P279 that it is a subclass of a measurand that has a dimension. The resp. constraint should be replaced by a suitable complex constraint. SCIdude (talk) 16:04, 5 February 2022 (UTC)

So far I've been adding ISQ dimension (P4020) to quantity items even if that value is implied by a subclass of (P279) relation, though I don't recall whether there's ever been a formal agreement whether we should a) fill out all such implied values or b) keep the graph lean or c) something in the middle (say, no rules).

I'd be fine to simply add the ISQ dimension (P4020) to all quantities. Toni 001 (talk) 14:59, 6 February 2022 (UTC)