Property talk:P2307

Active discussions

Documentation

namespace
qualifier to define a property constraint in combination with P2302 (Wikidata property constraint)
RepresentsMediaWiki namespace (Q6535237)
Data typeString
Domainqualifier for property constraint (P2302) (note: this should be moved to the property statements)
Allowed values(File|Category|Creator|Institution|Data)
Examplenamespace ==> File (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.
Lists
Proposal discussionProposal discussion
Current uses
Total78
Main statement11.3% of uses
Qualifier7494.9% of uses
Reference33.8% of uses
Search for values
[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)
List of this constraint violations: Database reports/Constraint violations/P2307#scope, hourly updated report, SPARQL, SPARQL (new)
  Format “(File|Category|Creator|Institution|Data): value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2307#Format, SPARQL, 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-

Add Gallery as a possible value?Edit

Commons gallery (P935) could use namespace specification. How should it be added? --Jarekt (talk) 20:14, 9 March 2018 (UTC)

The "format" for values is a regexp specific to each wikiEdit

The problem is that the listed values in the regexp are only valid for Commons, but this format should be specified wiki by wiki, using qualifiers. Setting a generic contraint of format such as "(File|Category|Creator|Institution|Data)" will not work to specify valid namespaces for other wikis (including Wikidata itself !)

So most probably this "format constraint property" cannot be set as a constraint directly here in P2307 (and P2307 cannot be used as a valid contraint for Commons or any wiki), but by creating set derived constraints (based on P2307) one constraint for each wiki, so that we can indicate their correct namespaces they accept ("File", "Category", "User", or even the associated Talk namespaces OK on all wikis, but not "Data", "Creator", "Institution" which are Commons-specific, or "Author" which is specific to Wikibooks) in a required "format constraint property" to define in the derived constraint.

Note also that the regexp used here should not be case sensitive (namespaces in wikis are not case-sensitive) so that "data" if also valid; there are also accepted aliases (e.g. "Image" is a valid alias of "File". Do we want only the "canonical namespace names" (with the leading capital as displayed on the wiki), and not any alias (which is valid also for links) ? Can we infer such canonicalization from the regexp or should be declare each namespace for each wiki as separate Wikidata elements listing their known canonical names and all their known aliases, instead of specifying a regexp here ?

Verdy p (talk) 23:17, 15 March 2018 (UTC)

Return to "P2307" page.