Property talk:P2859

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

X-SAMPA code
Extended Speech Assessment Methods Phonetic Alphabet (X-SAMPA) code for phoneme

Represents	X-SAMPA (Q614484)
Data type	String
Domain	phone (Q202064)
Allowed values	[ -~]+(([a-zA-Z1-9@{}&?<>]\\?`?|[=|<>:!-]\\)(_([ac-ehjl-rtv-xABF-HL-ORTX0^<>\\/}\"+-]|\?\\|_?[=~]))*(:\\?)?|[%'"|^.-]|\|\||-\\)+
Example	near-open front unrounded vowel (Q740768) → { voiceless palato-alveolar affricate (Q518603) → tS
Tracking: usage	Category:Pages using Wikidata property P2859 (Q120092357)
See also	IPA transcription (P898), Kirshenbaum code (P3625)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P2859 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 476 Main statement 474 99.6% of uses Qualifier 2 0.4% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

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/P2859#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/P2859#Unique value, SPARQL (every item), SPARQL (by value)

Type “phone (Q202064)”: item must contain property “subclass of (P279)” with classes “phone (Q202064)” 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/P2859#Type Q202064, SPARQL

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P2859#Scope, hourly updated report, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase form (Q54285143): 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/P2859#Entity types

Item “IPA transcription (P898)”: Items with this property should also have “IPA transcription (P898)”. (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/P2859#Item P898, search, SPARQL

Item “Kirshenbaum code (P3625)”: Items with this property should also have “Kirshenbaum code (P3625)”. (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/P2859#Item P3625, search, SPARQL

Format “[ -~]+”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P2859#Format, hourly updated report, SPARQL

Format “(([a-zA-Z1-9@{}&?<>]\\?`?|[=|<>:!-]\\)(_([ac-ehjl-rtv-xABF-HL-ORTX0^<>\\/}\"+-]|\?\\|_?[=~]))*(:\\?)?|[%'"|^.-]|\|\||-\\)+”: 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/P2859#Format, SPARQL

This property is being used by: ru:Шаблон:Карточка звука be:Шаблон:Картка:Гук vec:Modeło:Infobox de Fonema es:Plantilla:Ficha de fonema oc:Modèl:Infobox AFI Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Use for forms in lexemes?

Can/should this property be used for the forms of lexemes? — Finn Årup Nielsen (fnielsen) (talk) 17:31, 27 March 2019 (UTC)

@ChristianKl, NMaia: Do you have an input on this issue? There is a CC0 database with SAMPA [1] which perhaps can be used, see, e.g., See [2]. — Finn Årup Nielsen (fnielsen) (talk) 13:47, 7 June 2019 (UTC)

I can't think of a reason why not! NMaia (talk) 15:06, 7 June 2019 (UTC)

It was set to item of property constraint (P2305) Wikibase lexeme (Q51885771). I have changed that to item of property constraint (P2305) Wikibase form (Q54285143). — Finn Årup Nielsen (fnielsen) (talk) 08:56, 19 December 2023 (UTC)

Problems with the constraints

Hi y'all,

We may need to revisit the constraints for this property, right now we have :

• "Single value" 66 violations = 18 %
• "Unique value" 21 violations = 6 %
• "Type phone (Q202064)" 145 violations = 41 %
• "Scope" 0 violation = 0 %
• "Entity types" 0 violation = 0 %
• "Item transcription API (P898)" 139 violations = 39 %
• "Item Kirshenbaum (P3625)" 226 violations = 64 %
• "Format" 0 violations = 0 %
• "Format" 109 violations = 31 %

Some of these numbers are pretty high. @Fnielsen, ChristianKl, Tinker Bell, LitigiousOx, Roman Kerimov: I don't know much about X-SAMPA, could you take a look?

Cheers, VIGNERON (talk) 09:22, 28 January 2023 (UTC)

When the property was created there were no lexemes, single value, unique value and the type phone constraint all don't apply to uses on lexemes. IPA transcriptions and kirshenbaum transcription could both be automatically generated, so that constraint is good. I don't know enough about whether the last format constraint should be changed. ChristianKl ❪✉❫ 14:04, 28 January 2023 (UTC)

• I have use the property for lexemes, see above "Use for forms in lexemes?". There might be multiple pronounciations for a form. Two different forms may be pronounced the same. So if the property is ok for use in lexemes some of the constraints should be changed. — Finn Årup Nielsen (fnielsen) (talk) 20:46, 31 January 2023 (UTC)