Property talk:P2916
Jump to navigation
Jump to search
Documentation
syntax clarification
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.
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.
Represents | syntax (Q37437) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | Monolingual text | ||||||||||||
Domain | Properties with cryptic property values, in particular for property "format as regular expression", P1793. (note: this should be moved to the property statements) | ||||||||||||
Allowed values | According to this template:
Any descriptive text
According to statements in the property:
When possible, data should only be stored as statements.{2,2000} | ||||||||||||
Usage notes | brukast for å uttrykke ein tekstleg verdi for eigenskapen og skal følgjast av regulæuttrykket (regex) | ||||||||||||
Example | According to this template:
Yandex Music artist ID (P1553) : format as a regular expression (P1793) → "[1-9]\d{0,6}"
According to statements in the property:
When possible, data should only be stored as statementsYandex Music artist ID (P1553) → numerisk streng, 1 til 7 tall Norwegian historical register of persons ID (P4574) → p etterfølgd av ein bokstav | ||||||||||||
See also | format as a regular expression (P1793), Wikidata usage instructions (P2559), constraint clarification (P6607), media legend (P2096) | ||||||||||||
Lists | |||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
|
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as qualifier (Q54828449): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2916#Scope, hourly updated report, SPARQLItem “format as a regular expression (P1793)”: Items with this property should also have “format as a regular expression (P1793)”. (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/P2916#Item P1793, SPARQL
Conflicts with “instance of (P31): written work (Q47461344)”: this property must not be used with the listed properties and values. (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/P2916#Conflicts with P31, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2916#Format, hourly updated report, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase property (Q29934218): the property may only be used on a certain entity type (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/P2916#Entity types
Scope
[edit]Please see Wikidata:Property proposal/Property constraint comment.
--- Jura 12:37, 10 August 2016 (UTC)
- I updated the description per suggestion there.
--- Jura 12:35, 20 August 2016 (UTC)