Property talk:P2347

Documentation

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

YSO ID
identifier for a concept in the General Finnish Ontology YSO

Represents	General Finnish Ontology (Q27303896)
Applicable "stated in" value	General Finnish Ontology (Q27303896)
Data type	External identifier
Domain	any (but not people or purely geographical places, though there are some buildings, airports etc) (note: this should be moved to the property statements)
Allowed values	[1-9][0-9]{0,5}
Usage notes	Wikidata users using this property to establish links between Wikidata and YSO concepts are advised to first read the instructions on the Finto service customer wiki and use the property accordingly: https://www.kiwi.fi/x/IQC5FQ
Example	pulmonary fibrosis (Q32446) → 22287 (RDF) Finland (Q33) → 94426 (RDF)
Source	https://finto.fi/yso/
Formatter URL	https://www.yso.fi/onto/yso/p$1 (Please note! Links to the /yso-paikat/ graph are automatically forwarded, do not change this link!)
Robot and gadget jobs	Could be validated by dereferencing the URI and checking the resulting HTTP status code
Related to country	Finland (Q33) (See 61 others)
See also	YSA ID (P6293)
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 external identifier 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 Mix'n'match (Report) Mix'n'match (Report) Mix'n'match (Report) Database reports/Constraint violations/P2347 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 30,156 Main statement 29,931 out of 30,000 (100% complete) 99.3% of uses Qualifier 2 <0.1% of uses Reference 223 0.7% of uses
Search for values

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

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

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). Known exceptions: nutrient (Q181394), landrace (Q174030), confirmation class (Q110996192), social science (Q34749), rhumba (Q221438), spirituality (Q168796), music industry (Q746359), accessibility (Q555097), fishing lure (Q1197418), sewer network (Q156849), road pricing (Q2739432), stress (Q181767), video recording (Q34508), pope (Q19546), Russo-Ukrainian War (Q15860072), keyboard instrument (Q52954), make-up artist (Q935666), Säkylänharju-Virttaankangas (Q24305840), taiga (Q69564)
List of violations of this constraint: Database reports/Constraint violations/P2347#Single value, SPARQL

Format “[1-9][0-9]{0,5}”: value must be formatted using this pattern (PCRE syntax). (Help)

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

Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836), human (Q5), Wikimedia template (Q11266439)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P2347#Conflicts with P31, hourly updated report, 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/P2347#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (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/P2347#Scope, SPARQL

Qualifiers “subject named as (P1810), alternative name (P4970), point in time (P585), start time (P580), end time (P582), located in the administrative territorial entity (P131), applies to part, aspect, or form (P518), object of statement has role (P3831), reason for deprecated rank (P2241), object named as (P1932), mapping relation type (P4390), scope note (P9570), intended subject of deprecated statement (P8327), identifier shared with (P4070), reason for preferred rank (P7452), replaces (P1365), replaced by (P1366), last update (P5017), replacement value (P9729), constraint clarification (P6607), stability of property value (P2668)”: this property should be used only with the listed qualifiers. (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/P2347#allowed qualifiers, SPARQL

Label required in languages: fi, mul: Entities using this property should have labels in one of the following languages: fi, mul (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/P2347#Label in 'fi, mul' language, search, SPARQL

Label required in languages: sv, mul: Entities using this property should have labels in one of the following languages: sv, mul (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/P2347#Label in 'sv, mul' language, search, SPARQL

URI namespace is wrong (should be HTTP not HTTPS)

I noticed that the URI namespace (formatter URL) is wrong. It uses https, when YSO URIs are actually plain http. It is easy to verify this, for example go to http://finto.fi/yso/en/page/p22287 (the page for the concept "pulmonary fibrosis" which is presented as an example of using this property) and look at the URI box near the bottom of the page. I tried to change it, but wasn't allowed ("Disallow new editors from changing formatter URL"). Note that I am the original proposer of this property. Either I made an error in my proposal, or someone changed the URL pattern later. --Osma Suominen (talk) 12:32, 9 June 2017 (UTC)

The https URL https://finto.fi/yso/en/page/p22287 also works, and we generally prefer secure versions, where available. Is there any reason we should not do so in this case? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:24, 9 June 2017 (UTC)

I don't know what I was thinking when I wrote the above. Yes, of course it is fine to use https URIs for finto.fi. What is not OK is to use URIs starting with https://www.yso.fi/, since that doesn't match the actual URIs in the data (plus the server is not prepared for this and gives the wrong certificate, but that could/should be fixes). But that is not what is happening here. All is fine. Sorry for the confusion! Osma Suominen (talk) 13:56, 16 June 2017 (UTC)

Ah, now I see that Zache actually changed the formatter URI today, according to my request. But my example URLs were wrong in my message above. Osma Suominen (talk) 13:58, 16 June 2017 (UTC)

Removed the property constraint "conflicts with" Q1248784

The YSO ontology does contain values for several airports (http://www.yso.fi/onto/yso/p664) so this constraint was wrong and thus removed. Saarik (talk) 16:28, 16 August 2021 (UTC)

Removing single value and distinct value constraints from this property

There are multiple cases with differences in the data modeling between Wikidata and YSO where a single item points to two separate items in the other one and this applies in both directions. We may need to remove the limiting constraints single-value constraint (Q19474404) and distinct-values constraint (Q21502410) to be able to add two YSO-ID to a Wikidata item or the same YSO-ID to two separate wikidata items. Saarik (talk) 08:57, 17 November 2021 (UTC)

• If it's a more general issue, the datatype should be changed from external-id to string. --- Jura 09:18, 17 November 2021 (UTC)

  Absolutely not. We will need to have the YSO-IDs as links to the finto.fi service. The point is just to remove the unnecessary constraint warnings. Saarik (talk) 16:18, 17 November 2021 (UTC)

In which item are these constraints "unnecessary"? As far as I can see, these constraints are there with a reason, especially in case of entries about places that I commented on earlier (see Topic:Wjvkbmckojfr816x). Distinct-value constraint in this case helps us find external dataset entries where data about distinct concepts is mixed inadequately and that probably shouldn't be linked from Wikidata to avoid futher confusion. Simply omitting the constraint does not make the problem go away. Such entries should be fixed on YSO's side. If you are in contact with people behind YSO dataset then you might want to let them know about this issue. 2001:7D0:81DA:F780:EB:330A:DC60:A3F1 09:31, 26 November 2021 (UTC)

@Saarik: I added separator (P4155) = identifier shared with (P4070) to the distinct value constraint which means that the constraint will accept same values in different items if the values have qualifier P4070. Samoasambia ✎ 10:19, 25 August 2024 (UTC)

Most of the listed single value and distinct value constraint violations have been handled by marking the erroneous or violating statements as deprecated. Please, note that "WikibaseQualityConstraints only uses normal-rank and preferred-rank constraint statements and ignores deprecated-rank ones, so setting a constraint’s rank to deprecated can be used to “hide” it from WikibaseQualityConstraints. (KrBot uses all constraint statements regardless of rank.)" source: When constraints aren't checked Saarik (talk) 08:36, 10 January 2022 (UTC)

Well, but the actual problem (messy data and links to non-matching external database entries) is still there. 2001:7D0:81DA:F780:2401:7416:81A4:B676 12:44, 11 January 2022 (UTC)

Rajoitemuutoksia

@Saarik, @Tuomas Palonen: Poistin äsken erillisarvojen rajoitteesta kaikki poikkeukset, sillä lisäsin kaikkiin niihin identifier shared with (P4070) -tarkenteen, joka estää rajoitteen laukeamisen. Sivulta Wikidata:Database reports/Constraint violations/P2347 löytyy päivittyvä luettelo, jossa on listattu tätä rajoitetta rikkovat kohteet (noin 350 kpl tällä hetkellä), joihin täytyy käydä lisäilemässä P4070-tarkenne. Lisäksi lisäsin ominaisuuteen kaksi uutta label in language constraint (Q108139345) -rajoitetta, jotka huomauttavat siitä, että Wikidata-kohteelta puuttuu suomen/ruotsinkielinen nimi tai monikielinen oletusnimi.

TL;DR in English: I added P4070 as separator for distinct values constraint, removed the exceptions, and added label in language constraint (Q108139345) for fi/sv/mul labels. Samoasambia ✎ 13:05, 26 August 2024 (UTC)

nyt virheraportti ei näytä tuon muutoksen jälkeen mitään, joten korjaus on vaikeaa....

>> ERROR: Error while Q108139345 constraint parameters loading: Too many P424 values Saarik (talk) 13:59, 12 October 2024 (UTC)

@Saarik: Kävin elokuussa valittamassa tästä asiasta botin omistajan keskustelusivulle [1], koska tuon rajoite on ihan validi, mutta raporttia päivittävän botin koodissa on virhe. Hän ei ole kuitenkaan vielä korjannut asiaa... Jos joku muu myös käy häntä muistuttamassa tästä, niin ehkä hän korjaa bugin nopeammin. Samoasambia ✎ 15:53, 12 October 2024 (UTC)

Tässä pari SPARQL-kyselyä, joilla näkee reaaliaikaisesti YSO-tunnisteen erillisarvojen rajoitteen rikkomukset ja yhden arvon rajoitteen rikkomukset. Voin kirjoittaa lisää kyselyitä tarvittaessa. Samoasambia ✎ 16:09, 12 October 2024 (UTC)