Property talk:P7007

Documentation

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

Wolfram Language unit code
input form for a unit of measurement in the Wolfram Language

Description	input form for a unit of measurement in the Wolfram Language
Applicable "stated in" value	Wolfram Language (Q15241057)
Data type	External identifier
Domain	unit of measurement (Q47574), individual quantity (Q71550118) or unit prefix (Q15132612)
Allowed values	According to this template: string, product, division, power, HoldForm[...] According to statements in the property: [A-Za-z0-9"()*/\[\]^-]+ When possible, data should only be stored as statements
Example	metre (Q11573) → "Meters" metre per second (Q182429) → "Meters" / "Seconds" joule per cubic metre kelvin (Q3186734) → "Joules" / ("Meters"^3 * "KelvinsDifference")
See also	Wolfram Language entity code (P4839), Wolfram Language quantity ID (P7431), Wolfram Language entity type (P7497), UCUM code (P7825), QUDT unit ID (P2968)
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 Items with no other external identifier 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/P7007 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 2,446 Main statement 2,443 99.9% of uses Qualifier 3 0.1% of uses
Search for values

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

Single value: this property generally contains a single value. (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/P7007#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (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/P7007#Unique value, SPARQL (every item), SPARQL (by value)

Type “unit of measurement (Q47574), individual quantity (Q71550118), unit prefix (Q15132612)”: item must contain property “instance of (P31)” with classes “unit of measurement (Q47574), individual quantity (Q71550118), unit prefix (Q15132612)” 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/P7007#Type Q47574, Q71550118, Q15132612, SPARQL

Item “measured physical quantity (P111)”: Items with this property should also have “measured physical quantity (P111)”. (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/P7007#Item P111, search, SPARQL

Conflicts with “Wolfram Language quantity ID (P7431)”: this property must not be used with the listed properties and values. (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/P7007#Conflicts with P7431, search, 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/P7007#Scope, 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/P7007#Entity types

Format “[A-Za-z0-9"()*/\[\]^-]+”: value must be formatted using this pattern (PCRE syntax). (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/P7007#Format, SPARQL

datatype

Shouldn't this have external-id datetype? It appears to uniquely identify units in that system. --- Jura 10:40, 27 July 2019 (UTC)

I've been wondering that, too. If this were always just a string then I would tend to agree, but in general this can be an algebraic expression of strings with many valid ways to write them down. One could argue that once one agrees on a standard code formatting (I have used so far the InputForm[...] with a space inserted around "*" and "/") then those values should be unique identifiers. But then one could view this property - as its name suggests - as part of a family of "code" or "program" properties, just like Wolfram Language entity code (P4839) and some hypothetical "SPARQL code" (see also Wikidata SPARQL query equivalent (P3921)), "javascript code", ... which I would not consider identifiers because there are usually many ways to write any given "program". Toni 001 (talk) 12:58, 13 August 2019 (UTC)

• Wikidata SPARQL query equivalent (P3921) uses string as they dont need to be unique.

Values for Wolfram Language unit code (P7007) should be normalized in one way or the other. --- Jura 08:51, 22 August 2019 (UTC)

I just gave some more explanation about "code" on the Wolfram Language entity code (P4839) talk page, which applies here, too. Toni 001 (talk) 11:30, 2 October 2019 (UTC)

 Support Given that Wolfram Language entity code (P4839) will be changed to external ID I now think that the same can be done for this property. While identifying a unit, the expressions are still code, so I think the current name is good even if the type is changed to external ID. Toni 001 (talk) 17:47, 18 October 2019 (UTC)