Property talk:P2315

Active discussions




The WD community has agreed to delete this property. PLEASE NO LONGER USE IT.

See the full discussion here.

Please rather use properties listed under field see also (P1659) on the main property page.




Documentation

comment (DEPRECATED)
to be deleted: replace with "syntax clarification" (P2916) or add the usage note in the items description.
Data typeMonolingual text
Domainproperties (note: this should be moved to the property statements)
Examplestring ==> [explanation of usage/meaning of this constraint] (note: this information should be moved to a property statement; use property Wikidata property example (P1855), Wikidata property example for properties (P2271), Wikidata property example for lexemes (P5192), Wikidata property example for forms (P5193) or Wikidata property example for senses (P5977))
Robot and gadget jobsMigrate constraints from property talk pages.
See alsoWikidata usage instructions (P2559), sourcing circumstances (P1480), statement disputed by (P1310), reason for deprecation (P2241), syntax clarification (P2916), criterion used (P1013), quotation (P1683), reference URL (P854), object has role (P3831), named as (P1810)
Lists
Proposal discussionProposal discussion
Current uses
Total192
Main statement136.8% of uses
Qualifier15480.2% of uses
Reference2513% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
  Scope is as qualifiers (Q54828449): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2315#scope, SPARQL, SPARQL (new)
  Allowed entity types are Wikibase property (Q29934218): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2315#allowed entity types, SPARQL (new)
Title ID Data type Description Examples Inverse
property constraintP2302Itemproperty constraint: constraint applicable to this Wikidata propertyIMDb ID <property constraint> distinct values constraint-
exception to constraintP2303Itemitem that is an exception to the constraint, qualifier to define a property constraint in combination with P2302traffic sign <exception to constraint> Shin-Tōmei Expressway-
group byP2304PropertyGROUP BY: qualifier to define a property constraint in combination with P2302 (Wikidata property constraint)Property talk:P2304-
item of property constraintP2305Itemqualifier to define a property constraint in combination with "property constraint" (P2302)Property talk:P2305-
propertyP2306PropertyWikidata property: qualifier to define a property constraint in combination with P2302 (property constraint), or to limit the scope of Q44292881 (wikidata statement)Property talk:P2306-
namespaceP2307StringMediaWiki namespace: qualifier to define a property constraint in combination with P2302 (Wikidata property constraint)Property talk:P2307-
classP2308Itemclass (set theory): qualifier to define a property constraint in combination with "property constraint" (P2302)Property talk:P2308-
relationP2309Itemrelation and relation: qualifier to define a property constraint in combination with P2302. Possibly values are: "instance of", "subclass of" or "instance or subclass of". The qualifier to use with the property "relative" is "type of kinship" (P1039), not this.Property talk:P2309-
minimum date (property constraint)P2310Point in timequalifier to define a property constraint in combination with P2302Property talk:P2310-
maximum date (property constraint)P2311Point in timequalifier to define a property constraint in combination with P2302. Use "unknown value" for current date.Property talk:P2311-
maximum valueP2312Quantitymaximum: qualifier to define a property constraint in combination with P2302. "no value" can be used to specify no upper boundrange constraint-
minimum valueP2313Quantityminimum: qualifier to define a property constraint in combination with P2302range constraint-
format as a regular expressionP1793Stringregular expression: regex describing an identifier or a Wikidata property. When using on property constraints, ensure syntax is a PCREISO 639-3 <format as a regular expression> [a-z]{3} and IMDb ID <format as a regular expression> ev\d{7}\/\d{4}(-\d)?|(ch|co|ev|nm|tt)\d{7}-
constraint statusP2316Itemqualifier to define a property constraint in combination with P2302. Use values "mandatory constraint" or "suggestion constraint"property scope constraint <constraint status> mandatory constraint-
syntax clarificationP2916Monolingual textsyntax: qualifier for P1793 (regular expression): to provide a textual description of the regex syntax of a value. Should be displayable after the text "The value for the property should match" and be followed by the regex.Property talk:P2916-

Purpose of this propertyEdit

Could someone explain how this property is supposed to be used? The proposal does not explain it very well (it seems to be something to do with property constraints?). The label is very vague, "comment" could mean anything at all - what I'm writing now is a comment. The description sounds like it should be used as an instruction field like requested on phab:T97566 but that's nothing to do with property constraints. Then there are already uses which don't seem like anything to do with property constraints or usage instructions, e.g. the references on David Rockefeller (Q11239) and View of the wharf at Nyholm with the crane and some warships (Q22137795). @Ivan A. Krestinin, Jonas.keutel, Mbch331: - Nikki (talk) 14:13, 24 January 2016 (UTC)

It should not be used yet. It's meant to be used when we switch to statement based constraint, so comments can be added to constraint definitions (as now done with hidden text in the source code). Mbch331 (talk) 14:33, 24 January 2016 (UTC)
Do you have an example? - Nikki (talk) 14:17, 2 February 2016 (UTC)
I guess I should have pinged you to get an answer, so @Mbch331: :) I'm also curious what you think should be done about the mess here. I think it might make sense to propose two new properties for property usage notes and generic comments. Then, if the properties are approved, migrate the current uses, if they're rejected, delete the current uses. Then we could fix all the labels and descriptions, or even delete this property and recreate it (so that people can't continue using this one incorrectly). What do you think? - Nikki (talk) 15:50, 19 February 2016 (UTC)
An example of how I interpret what this property is meant for: Property talk:P2437, check the sourcecode and see the range constraints. And to solve the mess, I think new properties are the best solution. 1 for property usage noted, 1 for comments on constraint and 1 for general comments. And indeed delete this one. Mbch331 (talk) 16:01, 19 February 2016 (UTC)
Actually it should also be used for property usage notes, per Wikidata:Property_proposal/Archive/44#property_usage.
Personally, I don't see why it couldn't be used for usage notes in general, as at some point we should stop including them in descriptions.
--- Jura 14:42, 24 January 2016 (UTC)
To avoid that it gets used for anything, maybe the label should be changed to something more explicit. How about "Wikidata usage note"?
--- Jura 10:29, 1 February 2016 (UTC)
"Wikidata usage note" would work for property usage notes, but I don't think it would work for what property constraint comments. Looking at the proposal you linked, it seems it only says to use this property because you had changed this property's description to say it's for property usage notes, not because people felt that property usage notes should use the same property as property constraint comments. I don't think they should be the same property and I don't think the proposal should have been rejected, since it was rejected based on incorrect assumptions (that we had already created a property for it). - Nikki (talk) 14:17, 2 February 2016 (UTC)
What else property should I use to add a source as a free textual bibliographical citation? Like "McKenna, Bell: Classification of Mammal: Above the Species Level. — Columbia University Press, 2000" --Infovarius (talk) 09:55, 29 March 2018 (UTC)

Deletion discussionEdit

Clarify purpose in descriptionsEdit

@Mbch331, Nikki, Jura1: Now that property Wikidata usage instructions (P2559) exists to describe "how to use a property or item", could anyone familiar with earlier debates indicate what is the expected purpose, so that we can all fix its description translations? thanks -- LaddΩ chat ;) 23:06, 7 March 2016 (UTC)

Until this property has been integrated in the system, we can't fix any descriptions. When adding a property (or item) to an item (or other property), the comment (DEPRECATED) (P2315) should be shown, so people know how to use it. Mbch331 (talk) 06:49, 8 March 2016 (UTC)
I think they were asking what to do with this property's descriptions. The answer to that is, it depends on the outcome of the deletion request (linked from the section above). - Nikki (talk) 08:10, 8 March 2016 (UTC)
I gave it a try, at least to describe its relation to P2559 and most other properties (like sex or gender (P21)/country of citizenship (P27) etc).
--- Jura 09:05, 8 March 2016 (UTC)
Wikidata usage instructions (P2559) is too restrictive : it is useful to add note about why a property value is set, or not completed by another property, for example where one would expect a change after some date, but the reference listing new changes applicable to lists of items reuses the same value. It is also useful to detail why some properties are kept (e.g. with a given date longer than initially expected, or because there's been some legal decision to maintain a value whose change was contested and cancelled).
So we need more some general notes that are not just for Wikidata itself but for the actual data, to signal that this is not an error or omission. May be it will be read only in Wikidata by Wikidata contributors, but it allows also to temporarily submit data which is still not representable (e.g. missing property type, or the existing property type is not strictly inapplicable but further modelisation is needed). Wikidata usage instructions (P2559) is proably applicable only to the Wikidata ontology modelisation only, but not to actual data items that frequently need precisions not covered by the provided data (especially when it is exact and there's no error or omissions). Verdy p (talk) 13:39, 5 October 2018 (UTC)

P2315 was used instead of quote P1683 in referencesEdit

Other options are possible to describe Help:Sources. d1g (talk) 01:15, 11 August 2017 (UTC)

Can we undepriciate this property?Edit

We could use this property for adding clarification to copyright statements. See Help:Copyrights. Sometimes we have important piece of info that does not fit other properties, than a generic text "comment" is what is needed. --Jarekt (talk) 05:18, 2 February 2019 (UTC)

Return to "P2315" page.