Property talk:P4231

Latest comment: 1 year ago by C960657 in topic Removing property constraint

Documentation

United Nations Treaty Series registration number
registration number of a treaty within the United Nations Treaty Series
Data typeExternal identifier
Domaintreaty (Q131569)
Allowed values[1-9]\d*
ExampleTreaty on Certain Maritime Arrangements in the Timor Sea (Q1234338) → 44577
Agreement between the Republic of Latvia and the Kingdom of Spain on the mutual protection of classified information (Q39326380) → 46651
Agreement between the Government of the Republic of Poland and the Government of the United Kingdom of Great Britain and Northern Ireland concerning the mutual protection of classified information (Q39325825) → 44339
Sourcehttps://treaties.un.org/pages/AdvanceSearch.aspx?tab=UNTS&clang=_en
See alsoUnited Nations Treaty Series Volume Number (P4222), United Nations Treaty Collection object ID (P9966)
Lists
Proposal discussionProposal discussion
Current uses
Total254
Main statement24998% of uses
Qualifier41.6% of uses
Reference10.4% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “treaty (Q131569): item must contain property “instance of (P31)” with classes “treaty (Q131569)” or their subclasses (defined using subclass of (P279)). (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/P4231#Type Q131569, SPARQL
Format “[1-9]\d*: value must be formatted using this pattern (PCRE syntax). (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/P4231#Format, SPARQL
Single value: this property generally contains a single value. (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/P4231#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (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/P4231#Unique value, SPARQL (every item), SPARQL (by value)
Item “full work available at URL (P953): Items with this property should also have “full work available at URL (P953)”. (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/P4231#Item P953, SPARQL
Allowed entity types are Wikibase item (Q29934200): 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/P4231#Entity types

Contraint 'Unique Value' edit

There are some exceptions, and they are completely normal. For instance Q331504 (main treaty) has 3 supplementing protocols (only Q15991240 exists for now on Wikidata), and the four texts have the same Registration Number 39574. I don’t know how many such exceptions there are, and consequently if it’s worth keeping this contraint. Just mentioning it for now. ~ Seb35 [^_^] 19:44, 6 July 2018 (UTC)Reply

Removing property constraint edit

I'm removing property constraint (P2302)item-requires-statement constraint (Q21503247)property (P2306)depositary (P2058) for the same reasons as mentioned on Property_talk:P9966#Removing_property_constraint. --C960657 (talk) 18:31, 31 August 2022 (UTC)Reply

Return to "P4231" page.