Property talk:P3858
Documentation
Wikimedia template with route diagram
List of violations of this constraint: Database reports/Constraint violations/P3858#Value type Q17146139, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3858#Item P17, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3858#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P3858#Item P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3858#Type Q1067164, Q728937, Q55488, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3858#Entity types
|
Constraints[edit]
Discussion[edit]
There should be an inverse property to this[edit]
I've now added this property to most railways in Norway, but I find it a bit odd to only have a one-way connection, so we need an inverse property. I see that it was mentioned in the property proposal back then, but nothing seems to have happened since then. But I'm not sure if we actually need to have a new property only for that purpose. Since route diagram template (P3858) is set as a subproperty of topic's main template (P1424), then can't we just use template has topic (P1423)? I tried this at one item, and it now has a inverse constraints issue, but wouldn't just fixing the constraints fix this? Or could there be some logical problem related to use P1423 for this purpose?
Also, I could probably go through the same RDTs and add this property if it is okay to use P1423, but could this be done by a bot? It seems to me like a relatively small botjob that can't go very much wrong. (But I could be wrong too!) Anyhow, I have no knowledge of bots (and don't intend to learn it either), so if this should be done by a bot, someone else has to do it. Bergenga (talk) 08:58, 3 October 2018 (UTC)