[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 Bug 59680 depends on bug 49554, which changed state. Bug 49554 Summary: allow statements on properties https://bugzilla.wikimedia.org/show_bug.cgi?id=49554 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 --- Comment #7 from Emw --- I think it would help to have this request reviewed by someone with detailed knowledge of the RDFS and OWL W3C specifications. Markus Krötzsch might be willing. I am concerned about Example C from the original request. It sets making subproperties of P31 (instance of) a motivation for this property. P31 has the semantics of rdf:type per community consensus. It is also in the RDF export as such: see wikidata-instances.nt.gz in http://tools.wmflabs.org/wikidata-exports/rdf/exports/20140526/. That export uses OWL. Of the OWL varieties, OWL 2 DL tends to be preferred. However, according to the OWL 2 Structural Specification, section 5.3, "IRIs from the reserved vocabulary other than owl:topObjectProperty and owl:bottomObjectProperty MUST NOT be used to identify object properties in an OWL 2 DL ontology." [1] The specification goes on to explain that IRIs prefixed with rdf and rdfs, e.g. rdf:type and rdfs:subClassOf, are among the reserved vocabulary. A 2007 paper by Boris Motik, an editor of OWL 2, explains why making statements about the built-in vocabulary is such a problem. Simply put, statements like "x rdfs:subPropertyOf rdf:type" and "y rdfs:subPropertyOf rdfs:subClassOf" would not be valid in OWL 2 DL, the preferred W3C language for Semantic Web ontologies. Subproperties would be very useful, but enabling non-standard semantics would outweigh that benefit. 1. http://www.w3.org/TR/owl2-syntax/#Object_Properties 2. http://www.cs.ox.ac.uk/Boris.Motik/pubs/motik07metamodeling-journal.pdf -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 dacu...@gmail.com changed: What|Removed |Added Depends on||49554 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 John F. Lewis changed: What|Removed |Added Priority|Unprioritized |Low Status|UNCONFIRMED |NEW CC||johnflewi...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 Lydia Pintscher changed: What|Removed |Added CC||emw.w...@gmail.com --- Comment #6 from Lydia Pintscher --- *** Bug 50911 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 --- Comment #5 from dacu...@gmail.com --- @filceolaire: For that first you need to know what is the relationship of one property with the others. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 --- Comment #4 from filceolaire --- I am proposing that the query API should have a facility to search accross a property and it's subproperties in one action -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 dacu...@gmail.com changed: What|Removed |Added CC||dacu...@gmail.com --- Comment #3 from dacu...@gmail.com --- It should be enough by allowing statements for properties, that way we could specify which property is a subclass of another one https://bugzilla.wikimedia.org/show_bug.cgi?id=49554 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 Chris Maloney changed: What|Removed |Added CC||voldr...@gmail.com --- Comment #2 from Chris Maloney --- I would note that this was mentioned briefly here: https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2013/10#What_type_of_data_should_be_stored. I'm not sure if storing "subproperty" as a statement on a property would satisfy what filceolaire is asking for here, or if he is asking for something more integrated at a fundamental level. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 Ivan A. Krestinin changed: What|Removed |Added CC||crow...@rambler.ru --- Comment #1 from Ivan A. Krestinin --- Qualifiers, rankes, novalue, somevalue, value order, ... and now subvalue. Basic data model is too complex already. More complex data model increases complexity of every application (for example infoboxes). Not every programmer can create and support complex application. So complexity limits applications count. Another side: complexity creates ambiguity situations and conflicts. For example same data can be presented by multiple properties or one property + qualifier. This ambiguity creates many conflicts in Wikidata community. So, please do not increase complexity of basic data model. Sometimes a little decrease total volume of information is better then increasing data access complexity. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 59680] SubProperty mechanism
https://bugzilla.wikimedia.org/show_bug.cgi?id=59680 Andre Klapper changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
