Template talk:Constraint:Value type

Review 2013

Please review template name, property name, description and etc. My English is not well. — Ivan A. Krestinin (talk) 18:01, 9 June 2013 (UTC)

I'm trying to re-phrase it. Would you have to two sample items that are correct? --  Docu  at 18:14, 9 June 2013 (UTC)

Selenga (Q75745), Lena River (Q46841) — Ivan A. Krestinin (talk) 18:42, 9 June 2013 (UTC)

I tried to rephrase it .. not sure if it helps. --  Docu  at 18:57, 9 June 2013 (UTC)

P:P31 and P:P297 aren't easy to understand (and marginally useful IMHO): maybe using "instance of class" instead of "type" makes it more consistent with the terminology used there. --  Docu  at 19:05, 9 June 2013 (UTC)

My English level does not allow to see difference between "type" and "instance of class" :-) In Russian "тип" (type) is more trivial term then "экземпляр класса" (instance of class). "экземпляр класса" is used in scientific works in the main. "тип" is more widely used. You are feel free to rename the template. I synchronize bot`s code if needed. — Ivan A. Krestinin (talk) 19:30, 9 June 2013 (UTC)

The distinction more or less boils down to type-token distinction, where a class is a type and an instance is a token. Help:Basic membership properties explains things more fully. Emw (talk) 20:37, 30 June 2013 (UTC)

Creation of a Type Constraint for the same think for administrative area.

It's possible to create the same type of constraint for administrative area? It think it's possible by using P132 (P132) as remplacement of instance of (P31) and located in the administrative territorial entity (P131) as a subclass. It would be usefull to use make sure the administrative unit is located in the said area. --Fralambert (talk) 19:09, 4 August 2013 (UTC)

Description

In the description of this contraint {{P|31}} is hardcoded. But one can use this constraint with subclass instead of instance of. Therefore one should change the description. A property where subclass is used is for example P132 (P132). --Pasleim (talk) 09:13, 5 October 2013 (UTC)

• Currently P31 is hardcoded in bot`s code too. — Ivan A. Krestinin (talk) 13:18, 5 October 2013 (UTC)

No, I guess that was a question concerning the description of the template, which is at the moment translated from Russian to English and German. I updated the German description and included the "switch" form the Russian description. Is German okay? But I guess that the English description still needs a clean-up. --Zuphilip (talk) 22:51, 3 November 2013 (UTC)

Support custom relation

Hi Ivan, I would like to use this constraint on team captain (P634) to check for occupation (P106) = any subclass of athlete (Q2066131) (such as ice hockey player (Q11774891), basketball player (Q3665646), association football player (Q937857)...) Could you add support for this format :

 {{Constraint:Value type|class=Q2066131|relation=P106}}

Much appreciated tools. thanks LaddΩ chat ;) 15:16, 15 February 2014 (UTC)

• Hi, I add this to my TODO list. But priority is not very high. team captain (P634) is used in 10 items only. — Ivan A. Krestinin (talk) 17:21, 15 February 2014 (UTC)

Another case: property instrument (P1303) to check for occupation (P106) = any subclass of musician (Q639669) (such as drummer (Q386854), bassist (Q584301)...)

{{Constraint:Value type|class=Q639669|relation=P106}}

LaddΩ chat ;) 23:56, 27 May 2014 (UTC)

Support more than one class

It would be great if you could update this constraint to can be used with more than one class. It would great for properties like country of origin (P495) where the values can be at least of types country (Q6256) or state (Q7275). They have the property said to be the same as (P460) so it should be valid with any of them. -- Agabi10 (talk) 07:29, 2 June 2014 (UTC)

• You can add instance of (P31) = country (Q6256) to every instance of state (Q7275) or vice-versa if its have property said to be the same as (P460). — Ivan A. Krestinin (talk) 09:23, 2 June 2014 (UTC)

That only solves the problem in the cases that it is state (Q7275). It wouldn't take as valid if they are subclass of (P279) and I don't know if it is correct to add subclass of (P279) = country (Q6256) to every element with subclass of (P279) = state (Q7275) -- Agabi10 (talk) 06:44, 3 June 2014 (UTC)

Please update the documentation to clarify whether multiple classes are supported now. {{Constraint:Type}} supports them and this template renders them correctly as well. Petr Matas 19:50, 29 March 2015 (UTC)