Property talk:P537

Documentation

DescriptionDescribes the usual way that crystals show twinning.
Representscrystal twinning (Q109856)
Data typeItem
Template parameter
Domain
According to this template: Minerals, Variants of minerals
According to statements in the property:
mineral (Q7946), mineral species (Q12089225) or mineral variety (Q429795)
When possible, data should only be stored as statements
Allowed valuesSome are specific for certain minerals: Bavenoer, Karlsbader, Manebacher, Periklin, Dauphinée, .... (note: this should be moved to the property statements)
Example
According to this template: orthoklase = Bavenoer, Karlsbader, Manebacher (Qualifiers for frequency?)
According to statements in the property:
pyrite (Q50769)penetration twin (Q13366330)
sunstone (Q2729026)polysynthetic twinning (Q1238520)
When possible, data should only be stored as statements
Sourcemindat-, rruff-, mineral databases (note: this information should be moved to a property statement; use property source website for the property (P1896))
Lists
Proposal discussionProposal discussion
Current uses
Total14
Main statement1178.6% of uses
Qualifier214.3% of uses
Reference17.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “crystal twinning (Q109856): This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value crystal twinning (Q109856) (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/P537#Value type Q109856, SPARQL
 

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Return to "P537" page.