Open main menu

Wikidata:Property proposal/environment


Originally proposed at Wikidata:Property proposal/Natural science

   Not done
Descriptiondescribe the surroundings of an item.
Representssurface roughness (Q114817)
Data typeItem
Template parameterThis proprety request is part of the project of creating an infobox for materials
DomainPhysics, Biology...
Allowed valuesAny item
Example 1Corrosion resistance (Pxxx) → 500H with ISO standard (P503) → 9227, environment (Pxxx)sodium chloride (Q2314), ...
Example 2Corrosion resistance (Pxxx) → 500H with ISO standard (P503) → 9227, environment (Pxxx)nitric acid (Q83320), ...
Example 3Coefficient of friction : 0,3 with ISO standard (P503) → 15113, environment (Pxxx) → Dry (Qxxx) and Clean (Qxxx), ...
Sourcew:Environment and w:Biophysical environment
Planned useCreating an infobox for materials


This proprety request is part of the project of creating an infobox for materials. To be used as a qualifier for properties such as coefficient of friction or corrosion resistance. In the material scope we are interested in the w:Biophysical environment. However since environnement has a variety of uses it could be more interesting to create one global property that can accept any item as a value. --Thibdx (talk) 21:46, 27 July 2018 (UTC)


  •   Comment this label seems a little too generic and could be confusing ("enviroment" has a variety of meanings). Is there another term commonly used for this? ArthurPSmith (talk) 13:02, 30 July 2018 (UTC)
It could be medium to narrow a little bit. It is possible to use more specific terms specifying the type of medium : reaction medium, lubrication medium... --Thibdx (talk) 13:17, 30 July 2018 (UTC)
  •   Support, this should be useful, even with very broad name 'environment' (in this case we would have to add proper descriptions and instructions that this qualifier is only for chemical environment of measurement/reaction/etc, place some constraints here like value type constraint (Q21510865) = chemical substance (Q79529) etc. and keep an eye on the constraint violations pages). Wostr (talk) 18:55, 10 August 2018 (UTC)
  •   Comment My original goal was to propose a very open property to avoid the creation of several specialized ones in the futur. However I feel like you prefer to have something with a precise meaning. In this case I would better use a title that says precisely what the property is intended for in order to avoid violations. I would then propose reaction medium and lubrication medium that are the most immediate needs for materials. What do you think about it ? --Thibdx (talk) 21:19, 10 August 2018 (UTC)
    • IMHO such qualifiers are too specific and won't be needed if there's 'environment' qualifier. The only thing is that the constraints have to be applied correctly to this qualifier and someone have to watch for any attempts to use this qualifier in a non-intended way. Wostr (talk) 13:23, 11 August 2018 (UTC)
      • I'm OK with that too. It is just a matter of deciding. If we use environnement with constraints it could be precised by some other items like climates and items specifying that there is no chemicals like dry. However we may not have to list evrything now. This could be improved later. --Thibdx (talk) 19:43, 11 August 2018 (UTC)
The good point of having a wide qualifier could be on some cases where you specify a résistance to special environments. Most rescue knives are made to resist in corrosion in rivers. Wich is not the same as resting to corrosion in sea. Also deep sea is not the same as surface sea since there is not the same amount of oxygen. This is very specific but some steels, like hyper duplex, have been developed for very specific uses. Hyper Duplex is the only steel that resist when searching for deep oil. -- Thibdx (talk) 20:17, 12 August 2018 (UTC)
  • I will cautiously mark this as   Not done given that there seems to remain some uncertainty about the scope of this, and the discussion has stalled. Feel free to reopen and converge towards a consensus if this is still needed. − Pintoch (talk) 20:47, 6 March 2019 (UTC)