Property talk:P2056
Latest comment: 2 years ago by Toni 001 in topic Rename to avoid ambiguity?
Documentation
specific heat capacity
specific heat capacity of a substance, with phase of matter and temperature as qualifiers
specific heat capacity of a substance, with phase of matter and temperature as qualifiers
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “joule per kilogram kelvin difference (Q69423273), kilojoule per kilogram kelvin difference (Q108834064)”: value unit must be one of listed. (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/P2056#Units
Required qualifier “phase of matter (P515)”: this property should be used with the listed qualifier. (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/P2056#mandatory qualifier, SPARQL
Required qualifier “temperature (P2076)”: this property should be used with the listed qualifier. (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/P2056#mandatory qualifier, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2056#Scope, hourly updated report, SPARQLRange from “0” to “1000000”: values should be in the range from “0” to “1000000”. (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/P2056#Range
Citation needed: the property must have at least one reference (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/P2056#citation needed
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/P2056#Item P31, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2056#Item P31, SPARQL
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/P2056#Entity types
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Rename to avoid ambiguity? edit
There are several other measures of heat capacity, e.g. (extensive) heat capacity (Q179388), molar heat capacity (Q65122153). This should be renamed to remove ambiguity. I suggest "specific heat", which is unambiguous and the same number of words. 73.202.12.249 16:29, 15 September 2019 (UTC)
- I restricted the property to specific heat capacity (Q487756), with unit joule per kilogram kelvin difference (Q69423273). If we want to store other heat capacities, like molar or absolute, then we should propose additional properties.
- PS: The overall goal should be to have properties whose allowed units measure quantities of the same physical dimension (indicated by ISQ dimension (P4020)). This property (P2056) was one of the 25 or so which till now violated that principle.
- Toni 001 (talk) 09:23, 8 October 2021 (UTC)