There's a related essay on Wikimedia Commons:
http://commons.wikimedia.org/wiki/User:Multichill/Next_generation_categories
.
The Wikidata properties instance
ofhttps://www.wikidata.org/wiki/Property_talk:P31(formerly is a)
and subclass
of https://www.wikidata.org/wiki/Property_talk:P279 are
The relationship between Wikipedia categories and Wikidata pops up here and
there in discussions -- a recent one was
https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2013/06#Proposal_for_phase_4:_unify_and_centralize_categories
.
I think Wikidata
Max's comment is very related to Wikidata. The sex property [1] is a
model system to explore important questions for the project at large.
For example, how rigorous do we want to be with automatic classification?
Let's say a property can have one of three values: A, B or C. Roughly 90%
of the
What about monthly/dump-based aggregated property usage statistics?
Property usage statistics would be very valuable, Dimitris. It would help
inform community decisions about how to steer changes in property usage
with less disruption. It would have other significant benefits as well.
what's the usage of the Person class ?
'Person' [1] should generally be avoided. For background, see the
discussion about how to classify subjects like Coco Chanel in [2]. That's
the basis for the note not for use with P31, instead use Q5 human.
Pretty much all the items that link to
Hi Markus,
You asked who is creating all these [subclass of] statements and how is
this done?
The class hierarchy in
http://tools.wmflabs.org/wikidata-todo/tree.html?q=Q35120rp=279lang=enshows
a few relatively large subclass trees for specialist domains,
including molecular biology and
In case anyone is a bit lost, Tom is proposing an approach to
classification we've been calling explicit metamodeling. Simply put,
let's say you have a class hierarchy:
A subclass of B
B subclass of C
C subclass of D
The proposal, as I understand it, is to add instance of claims for almost
all
Markus,
Thank you very much for this. Translating Wikidata into the language of
the Semantic Web is important. Being able to explore the Wikidata taxonomy
[1] by doing SPARQL queries in Protege [2] (even primitive queries) is
really neat, e.g.
SELECT ?subject
WHERE
{
?subject
05:52, emw wrote:
Markus,
Thank you very much for this. Translating Wikidata into the language of
the Semantic Web is important. Being able to explore the Wikidata
taxonomy [1] by doing SPARQL queries in Protege [2] (even primitive
queries) is really neat, e.g.
SELECT ?subject
WHERE
For articles that are really about multiple different things that cannot
be reconciled in a single natural concept:
* State intance of:Wikipedia article with multiple topics (we already
have several other classes of Wikipedia articles).
* Use some property, say has topic, to link to items
Hi all,
Talk about causes is ubiquitous in everyday life and many other domains of
knowledge. Until recently, we've had a few properties to make statements
about cause in certain narrow areas, but lacked a way to structure data
about causes across a broad range of subjects. For example, you
Andra, Chinmay, Ben, Andrew,
Kudos! This is a significant milestone, and showcases Wikidata's potential
for structuring large sets of biological data. Thanks for your excellent
work!
Cheers,
Eric
https://www.wikidata.org/wiki/User:Emw
On Mon, Oct 6, 2014 at 4:21 PM, Benjamin Good
I have removed the statement *instance of* chemical compound from ethanol
(Q153) [1].
A few proposals have been made in this thread about how -- or whether -- to
use *instance of* (i.e. rdf:type, P31) to classify 'ethanol' and other
chemical compounds, but there seems to be consensus that
Hi all,
Wikimedia New York City will be hosting a Wikidata hackathon and beginners
workshop this coming Sunday. This will be a good event to meet Wikimedians
involved with cultural institutions, structure a bunch of data, and help
new users.
If you're in the area, come!
When:
Sunday, December
Hi all,
Could those knowledgeable about OWL or intending to use Wikidata's RDF /
OWL exports please weigh in at
https://www.wikidata.org/wiki/Wikidata:Property_proposal/Property_metadata#How_should_we_declare_that_a_property_is_transitive
? [1]
Being able to declare certain properties 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
Since it appears that the creation of *subproperty of* went unnoticed by
many, I'd like to describe an important aspect of its proper use, and how
that relates to classification.
Please note that *instance of* (P31) and *subclass of* (P279) are not valid
values for *subproperty of* (P1647)
Hi James,
My mistake, I should have linked to
https://www.wikidata.org/wiki/Property_talk:P1647, which includes the
following in the 'Examples' section of the documentation template:
Note: it is not valid to declare subproperties of instance of (P31)
(rdf:type), subclass of (P279)
Amir,
What is the false positive rate of your algorithm when dealing with
fictitious humans and (non-fictitious) non-human organisms? That is, how
often does your program classify such non-humans as humans?
Regarding the latter, note that items about individual dogs, elephants,
chimpanzees and
Yes. I could see a simple Statements vs. External identifiers
distinction being useful that's also reflected in the data model so
it's easier to treat these property groups in a distinct manner.
I support grouping statements about external identifiers together and
distinguishing them from
Sebastian, Benjamin, Elvira, Andra, Andrew,
Kudos on your progress with an OWL-centric approach to knowledge
representation. The community has been incorporating OWL concepts into
property definitions and ontology development on-wiki for some time, but
yours is the first Wikidata group I'm aware
21 matches
Mail list logo
