Property talk:P1261

From Wikidata
Jump to navigation Jump to search

Documentation

Rundata
database about runestones, mainly in Sweden, but stones in all of Europe, Greenland and U.S. can be found here
DescriptionRundata (Q492230) is a database about runestones, mainly in Sweden, but stones in all of Europe, Greenland and U.S. can be found here.
RepresentsRundata (Q492230)
Data typeExternal identifier
Template parametersignum in sv:Mall:Runinskriftsfakta
Domain
According to this template: Runestones
According to statements in the property:
runestone (Q815241), group of Norse runestones (Q24570142), Runic inscriptions (Q7379880) and mask stone (Q1766565)
When possible, data should only be stored as statements
Allowed values((Öl|Ög|Sö|Sm|Vg|U|Vs|Nä|Vr|Gs|Hs|M|Ån|D|Hr|J|Lp|Ds|Bo|G|By|DR|DE|E|F|FI|FR|GR|IM|IR|IS|IT|LV|N|NL|Or|PL|RU|Sc|Sh|UA) .+|)
ExampleRök Runestone (Q472975) → Ög 136
Uppland Runic Inscription 932 (Q7899135) → U 932
no label (Q10727999) → Ög ATA4905/48
Sourcehttp://www.nordiska.uu.se/forskn/samnord.htm
Lists
Proposal discussionProperty proposal/Archive/21#P1261
Current uses1,243
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Type “runestone (Q815241), group of Norse runestones (Q24570142), Runic inscriptions (Q7379880), mask stone (Q1766565): element must contain property “instance of (P31)” with classes “runestone (Q815241), group of Norse runestones (Q24570142), Runic inscriptions (Q7379880), mask stone (Q1766565)” or their subclasses (defined using subclass of (P279)). (Help)
List of this constraint violations: Database reports/Constraint violations/P1261#Type Q815241, Q24570142, Q7379880, Q1766565, hourly updated report, SPARQL, SPARQL (new)
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of this constraint violations: Database reports/Constraint violations/P1261#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value), SPARQL (new)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Known exceptions: no label (Q10727944)
List of this constraint violations: Database reports/Constraint violations/P1261#Single value, SPARQL, SPARQL (new)
Format “((Öl|Ög|Sö|Sm|Vg|U|Vs|Nä|Vr|Gs|Hs|M|Ån|D|Hr|J|Lp|Ds|Bo|G|By|DR|DE|E|F|FI|FR|GR|IM|IR|IS|IT|LV|N|NL|Or|PL|RU|Sc|Sh|UA) .+|)”: value must be formatted using this pattern (PCRE syntax). (Help)
List of this constraint violations: Database reports/Constraint violations/P1261#Format, hourly updated report, SPARQL, SPARQL (new)
Item “country (P17): Items with this property should also have “country (P17)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1261#Item P17, search, SPARQL, SPARQL (new)
Item “image (P18): Items with this property should also have “image (P18)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1261#Item P18, SPARQL, SPARQL (new)
Item “coordinate location (P625): Items with this property should also have “coordinate location (P625)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1261#Item P625, SPARQL, SPARQL (new)
Item “located in the administrative territorial entity (P131): Items with this property should also have “located in the administrative territorial entity (P131)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1261#Item P131, search, SPARQL, SPARQL (new)
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P1261#Conflicts with P31, hourly updated report, search, SPARQL, SPARQL (new)
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Q815241 constraint[edit]

Note that the {{Constraint:Item|property=P31|item=Q815241}} - constraint is most likely to restrictive. The database contains runic inscriptions, these can be on runestones but also on other surfaces (as "graffiti" on Bysantine ruins, on preserved wood etc.). /André Costa (WMSE) (talk) 14:38, 1 May 2015 (UTC)

Let's see what it does and adapt it depending on the output. --- Jura 14:39, 1 May 2015 (UTC)
"Should also have image (P18)" will also be difficult in some cases.
no label (P387) maybe can be added! The datatype is string, so it does not have the problems the monolingual datatype has. -- Innocent bystander (talk) 08:13, 2 May 2015 (UTC)
Well, there are "must have", "likely to have" and "nice to have" constraints. The first ones can be marked "mandatory", the last ones shouldn't be added if there are too many errors. --- Jura 08:18, 2 May 2015 (UTC)
For inscriptions, Uppland Runic Inscription 932 (Q7899135) uses no label (P438) which seems more appropriate (although that property is apparently being replaced with inscription (P1684), which is unfortunate as it requires you to define a language which doesn't seem entirely appropriate for ancient texts where language determination is largely based on interpretation).
We could use image (P18): no value for inscriptions that haven't been documented and are now considered lost (with sources and an "as of" qualifier in case the inscriptions turn up again). That would take care of many violations, although caution is warranted. Väsk (talk) 15:42, 2 May 2015 (UTC)
There is the possibility to create new language (and script) codes just for Wikidata. Maybe one or several should be requested. --- Jura 16:35, 2 May 2015 (UTC)
I wasn't aware of no label (P438). Some stones are written (at least partly) in a kind of code, for example the stone in Rök. Do we have any property for interpretations? Many of these were done in the 19th century, so they are not always copyrighted. -- Innocent bystander (talk) 05:03, 3 May 2015 (UTC)