Property talk:P2347
Documentation
identifier for a concept in the General Finnish Ontology YSO
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 57 others) | ||||||||||||
See also | YSA ID (P6293) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P2347#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P2347#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2347#Entity types
List of violations of this constraint: Database reports/Constraint violations/P2347#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2347#allowed qualifiers, SPARQL
URI namespace is wrong (should be HTTP not HTTPS) edit
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)
- 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
- 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 edit
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 edit
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)
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)