Re: [Wikidata-l] subclass-of vs. instance-of
Hi, both instance and subclass is possible, see https://www.wikidata.org/wiki/Help:Item_classification This has been a subject of dispute though, but this is a powerful tool, allowed by standards like OWL2 through punning 2014-12-30 22:35 GMT+01:00 Federico Leva (Nemo) nemow...@gmail.com: ja...@j1w.xyz, 30/12/2014 22:04: Are there processes in place to manage the integrity of these structural components of Wikidata? Yes. https://www.wikidata.org/wiki/Wikidata:Database_reports/ Constraint_violations Nemo ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] subclass-of vs. instance-of
Automobile (Q1420) had the claims [1]: *subclass of* motor road vehicle *instance of* motor road vehicle That was incorrect. An instance of motor road vehicle is something like the Peekskill Meteorite Car (Q7756463) [2]. It is generally incorrect when an item has *instance of* and *subclass of* claims with the same value. I am not aware of a Wikidata constraint template which can encode that rule. (Off hand I'm not sure how it would be encoded in OWL, either. Ontology experts: how would we do that?) If we wanted use both *instance of* and *subclass of* in automobile, then we would need to do something like: *subclass of* motor road vehicle *instance of* motor road vehicle class In my opinion, *instance of* claims like that are not very useful, because they simply restate what is directly implied in the *subclass of* claim. Punning that is not a mere rephrasing can be useful, e.g. Chevrolet Malibu (Q287723) [3] *subclass of* mid-size car, *instance of* car model. See also Markus's comment from September about using *subclass of* and *instance of* in the same item, which conveniently also discusses automobiles [4]. Happy Q11269! Eric https://www.wikidata.org/wiki/User:Emw 1. https://www.wikidata.org/w/index.php?title=Q1420oldid=184512429#P279 2. https://www.wikidata.org/wiki/Q7756463 3. https://www.wikidata.org/wiki/Q287723 4. https://lists.wikimedia.org/pipermail/wikidata-l/2014-September/004649.html ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] subclass-of vs. instance-of
Not sure either it's writeable as punning imply to treat the class/individual as different things ... tried to dig if it is possible in SWRL (see http://dior.ics.muni.cz/~makub/owl/ for example), seems not so easy either, found this topic on semanticweb.com (google cache http://webcache.googleusercontent.com/search?q=cache:dAcXbpivQJoJ:answers.semanticweb.com/questions/26553/property-chains-or-swrl-rules-with-subclassof-and-type+cd=1hl=frct=clnkgl=frclient=iceweasel-a, the site seems down ATM, original URL : swrl rules with subclass of and type http://answers.semanticweb.com/questions/26553/property-chains-or-swrl-rules-with-subclassof-and-type) which is related to the problems I faced and seem to imply it needs to be done in SPARQL. Happy Q11269 either ;) 2014-12-31 14:59 GMT+01:00 Emw emw.w...@gmail.com: Automobile (Q1420) had the claims [1]: *subclass of* motor road vehicle *instance of* motor road vehicle That was incorrect. An instance of motor road vehicle is something like the Peekskill Meteorite Car (Q7756463) [2]. It is generally incorrect when an item has *instance of* and *subclass of* claims with the same value. I am not aware of a Wikidata constraint template which can encode that rule. (Off hand I'm not sure how it would be encoded in OWL, either. Ontology experts: how would we do that?) If we wanted use both *instance of* and *subclass of* in automobile, then we would need to do something like: *subclass of* motor road vehicle *instance of* motor road vehicle class In my opinion, *instance of* claims like that are not very useful, because they simply restate what is directly implied in the *subclass of* claim. Punning that is not a mere rephrasing can be useful, e.g. Chevrolet Malibu (Q287723) [3] *subclass of* mid-size car, *instance of* car model. See also Markus's comment from September about using *subclass of* and *instance of* in the same item, which conveniently also discusses automobiles [4]. Happy Q11269! Eric https://www.wikidata.org/wiki/User:Emw 1. https://www.wikidata.org/w/index.php?title=Q1420oldid=184512429#P279 2. https://www.wikidata.org/wiki/Q7756463 3. https://www.wikidata.org/wiki/Q287723 4. https://lists.wikimedia.org/pipermail/wikidata-l/2014-September/004649.html ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] WikiData for Research Project Idea: Structured History
There is very interesting and relevant work done by a group of scholars about modeling time for recording historical events as structured data. Please have a look at http://dh.stanford.edu/topotime/ and http://perio.do/narrative/. I am following the discussion related to the development of the http://www.openhistoricalmap.org/ at https://lists.openstreetmap.org/listinfo/historic. In my mind, it would be a good idea to keep in sync with and provide insight into the other open projects for historical data, in this case geodata. The question of standards is being discussed right now :) Best, Susanna 2014-12-30 19:45 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com: Hoi, The Wikipedia article on the subject has probably most if not all relevant details.. Thanks, GerardM On 30 December 2014 at 16:39, Gerard Meijssen gerard.meijs...@gmail.com wrote: Hoi, The most important people, as far as Wikidata is concerned, are the Wikidata developers. As long as they indicate that the software conforms to the standard we are good. There is no problem in them having the standard and publishing what is expected of the use of timestamps and time diffs/ Thanks, GerardM On 29 December 2014 at 18:00, Paul Houle ontolo...@gmail.com wrote: Gerard, tell me about it. It's hard to find anyone who has even seen ISO 8601 so there is not general compatibility between tools that accept ISO 8601 (date)?(times?); the xsd:datetime (defined mainly as a restriction of ISO 8601) is closer to an open standard, but people aren't so sure about extra digits in the date fields, but maybe we will need them to deal with the year 1 problem. IEEE 744 is a similar scandal since it hasn't been read by most developers, particularly systems developers, so it is unlikely that FP operations in your favorite language are completely conformant. Now IEEE does have the Get802 program which lets you get slightly aged documents for networking standards and ISO does release the occasional standard for free such as ISO 20222 but there is a big difference between those two and the other organizations like the OMG, W3C, IETF, and FIPS that publish standards for free and manage to somehow pay the bills. On Mon, Dec 29, 2014 at 6:31 AM, Gerard Meijssen gerard.meijs...@gmail.com wrote: Hoi. The fact that ISO has its standards behind a paywall is its shame. However, it does not necessarily imply anything about the use of the standard. Thanks, Gerard NB a paywall seriously hampers acceptance of standards On 29 December 2014 at 12:20, Jeff Thompson j...@thefirst.org wrote: The ISO standard for CIDOC CRM is behind a pay wall with a patent notice. Can it be used in an open knowledge system? On 2014-12-29 9:49, Dov Winer wrote: Hi Sam, CIDOC/CRM is the ontology of choice for Structured History as it is anchored on modelling events. An excellent project based on it is the ResearchSpace from the British Museum. See: http://www.researchspace.org/ http://www.researchspace.org/home/rsandcrm http://cidoc-crm.org/ Enjoy, Dov ___ Wikidata-l mailing listWikidata-l@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- Paul Houle Expert on Freebase, DBpedia, Hadoop and RDF (607) 539 6254paul.houle on Skype ontolo...@gmail.com http://legalentityidentifier.info/lei/lookup ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- *Susanna Ånäs *Käyttäjä:Susannaanas Wikimedia Suomi http://wikimedia.fi/ – Wikimaps http://wikimaps.wikimedia.fi/ – GLAM http://fi.wikipedia.org/wiki/Wikipedia:GLAM @ https://twitter.com/WMFinlandWMFinland https://twitter.com/WMFinland / Facebook https://www.facebook.com/WikimediaSuomi / Liity jäseneksi! http://fi.wikimedia.org/wiki/Liity_j%C3%A4seneksi ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] WikiData for Research Project Idea: Structured History
Thanks for sharing those links Susanna :) really fascinating to find out about the related projects and discussions. I'll join in to any discussions about this on Wikidata - it's very relevant to the long term goals of Histropedia http://www.histropedia.com/ (interactive timeline powered by Wikidata, which I'm a co-founder of) so I may be able to add a useful perspective. I'm not sure where it is on the roadmap, but hopefully we'll soon get access to the 'before' and 'after' times for dates on Wikidata. I imagine this will open up a vast range of different uses for digital humanities projects, that are often dealing with uncertain time ranges. For example, we plan on using this data in Histropedia to visualise uncertainty in date ranges of events displayed on the timeline interface. Regards, Navino On 31 December 2014 at 15:20, Susanna Ånäs susanna.a...@wikimedia.fi wrote: There is very interesting and relevant work done by a group of scholars about modeling time for recording historical events as structured data. Please have a look at http://dh.stanford.edu/topotime/ and http://perio.do/narrative/. I am following the discussion related to the development of the http://www.openhistoricalmap.org/ at https://lists.openstreetmap.org/listinfo/historic. In my mind, it would be a good idea to keep in sync with and provide insight into the other open projects for historical data, in this case geodata. The question of standards is being discussed right now :) Best, Susanna 2014-12-30 19:45 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com: Hoi, The Wikipedia article on the subject has probably most if not all relevant details.. Thanks, GerardM On 30 December 2014 at 16:39, Gerard Meijssen gerard.meijs...@gmail.com wrote: Hoi, The most important people, as far as Wikidata is concerned, are the Wikidata developers. As long as they indicate that the software conforms to the standard we are good. There is no problem in them having the standard and publishing what is expected of the use of timestamps and time diffs/ Thanks, GerardM On 29 December 2014 at 18:00, Paul Houle ontolo...@gmail.com wrote: Gerard, tell me about it. It's hard to find anyone who has even seen ISO 8601 so there is not general compatibility between tools that accept ISO 8601 (date)?(times?); the xsd:datetime (defined mainly as a restriction of ISO 8601) is closer to an open standard, but people aren't so sure about extra digits in the date fields, but maybe we will need them to deal with the year 1 problem. IEEE 744 is a similar scandal since it hasn't been read by most developers, particularly systems developers, so it is unlikely that FP operations in your favorite language are completely conformant. Now IEEE does have the Get802 program which lets you get slightly aged documents for networking standards and ISO does release the occasional standard for free such as ISO 20222 but there is a big difference between those two and the other organizations like the OMG, W3C, IETF, and FIPS that publish standards for free and manage to somehow pay the bills. On Mon, Dec 29, 2014 at 6:31 AM, Gerard Meijssen gerard.meijs...@gmail.com wrote: Hoi. The fact that ISO has its standards behind a paywall is its shame. However, it does not necessarily imply anything about the use of the standard. Thanks, Gerard NB a paywall seriously hampers acceptance of standards On 29 December 2014 at 12:20, Jeff Thompson j...@thefirst.org wrote: The ISO standard for CIDOC CRM is behind a pay wall with a patent notice. Can it be used in an open knowledge system? On 2014-12-29 9:49, Dov Winer wrote: Hi Sam, CIDOC/CRM is the ontology of choice for Structured History as it is anchored on modelling events. An excellent project based on it is the ResearchSpace from the British Museum. See: http://www.researchspace.org/ http://www.researchspace.org/home/rsandcrm http://cidoc-crm.org/ Enjoy, Dov ___ Wikidata-l mailing listWikidata-l@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l -- Paul Houle Expert on Freebase, DBpedia, Hadoop and RDF (607) 539 6254paul.houle on Skype ontolo...@gmail.com http://legalentityidentifier.info/lei/lookup ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org
