6 ms·
HolyShit! > The goal of Abstract Wikipedia is to let more people share in more knowledge in more languages. Abstract Wikipedia is an extension of Wikidata. In
by sitkack 6y ago
HolyShit!
> The goal of Abstract Wikipedia is to let more people share in more knowledge in more languages. Abstract Wikipedia is an extension of Wikidata. In Abstract Wikipedia, people can create and maintain Wikipedia articles in a language-independent way. A Wikipedia in a language can translate this language-independent article into its language. Code does the translation.
from https://meta.wikimedia.org/wiki/Abstract_Wikipedia https://meta.wikimedia.org/wiki/Abstract_Wikipedia
Will this mean that knowledge is encoded in machine readable format and that we can start to write programs over this knowledge graph? This is huge.
- afandian 6y agoThe Abstract Wikipedia idea is a great advance. > knowledge is encoded in machine readable format and that we can start to write programs over this knowledge graph But surely that abilty has been the goal of wikidata from the start?
- coolreader18 6y agoPerhaps, but this seems to be moving towards a more holistic machine-readable article graph. If you look at a page from wikidata[0], it seems to be basically a key-value database (e.g. earth.highest point = [ mount everest { from sea level, 8000m } ], while the "full article" terminology used in the announcement seems like it may be even more connected/informative/structured than that. [0]: https://www.wikidata.org/wiki/Q2 https://www.wikidata.org/wiki/Q2
- afandian 6y agoAgreed, but my point was that the aim has always been to encode these facts and then mix them into wikipedia for any assertion / attribute, so that any fact is backed by an assertion.
- Vinnl 6y agoExactly. The main difference is that they would now not be used to generate the infoboxes, but actual prose.
- baddox 6y agoI don't see any indication that Abstract Wikipedia articles are anything more than a sequence of "constructors" and those "constructors" are essentially just triples (with qualifiers) that a "renderer" turns into a specific human language. The example they give is the constructor: rank(SanFrancisco, city, 4, population, California) And the English renderer will output: "San Francisco is the fourth largest city by population in California."
- Tarean 6y agoThe data is stored as a bunch of triples but it encodes a graph. You can use tools like sparql to query that graph. https://www.stardog.com/tutorials/sparql/ https://www.stardog.com/tutorials/sparql/
- incompatible 6y agoI'm curious whether this new project has been driven in any way by the difficulty of integrating data from Wikidata into Wikipedia. It various a lot by language, but the user communities are quite hostile to Wikidata in some cases. I think it's generally on the grounds that since Wikidata is a wiki, it can be easily vandalized and its data can't be trusted.
- bawolff 6y agoI dont really think so - the goal is to fill in the gaps of knowledge, not to replace existing wikipedias and whatever policies they may have.
- amrrs 6y agoI'm sorry if I didn't understand. Wouldn't a json or xml type data structure (where some Wikipedia stuff is already stored) would support this?
- Nican 6y agoWhile the implications are huge, it is hard to think about what is actually being done. XML and JSON are just languages, and the type of information could be stored in any number of ways. In my point of view, the problem here is that you could say something like "'water' and 'heat' produces 'steam'", but knowledge is never that simple, and understanding of that information is even more complicated. I would think that Abstract Wikipedia is not the first people trying to solve such a problem, and I am very curious to see what they come up with. EDIT: Looks like they have an example: https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Examples https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Examples
- remolacha 6y agoVery cool. I’m fascinated by the Wolfram Language paradigm of Knowledge Base+Programming language=Computable everything (demo: https://youtu.be/3yrVuM2SYZ8 https://youtu.be/3yrVuM2SYZ8). But I could never get into the Wolfram ecosystem because it’s totally proprietary. This makes me think, does Wikidata’s model (ontologies?) provide a way to recreate the Wolfram computable everything concept as an open community project?
- 20after4 6y agoYes, essentially. Wikidata models assertions of facts about things and it has a very powerful system for writing queries to get at the facts and relationships you are interested in. Here are some examples of what you can do with Wikidata: https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/queries/examples https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/...
- msla 6y agoIt assumes articles will say the same thing in every language, which to me means that edit wars can now proceed on a more global basis. You're no longer fighting only the people who feel comfortable enough with your language to edit in it, you're fighting anyone who can edit the article at all around the world. Do the Hebrew Wikipedia and the Arabic Wikipedia agree on the status of Israel?
- zeroimpl 6y ago> Do the Hebrew Wikipedia and the Arabic Wikipedia agree on the status of Israel? If they don’t agree, perhaps they can agree to disagree and we can encode that fact instead.
- kijin 6y agoA lot of serious social problems would be non-issues if only people could agree to disagree.
- atoav 6y agoUnless they agree to disagree about the facts in a case where one side is factually right while the other has the consistency of a lie your 3-year-old would make up to stop you from discovering they ate all the cookies. Agree to disagree is like saying there is no right side in this matter which is okay for topics where there isn't. Many topics however are not a matter of perspective, they are a matter of who is factually right. IMO in such a case agreeing to disagree can often be destructive, because it legitimises a position which is factually wrong and constructs an illusion of balance where there is none. If one side says it rains and the other says it doesn't, agreeing to disagree is wrong. If there is disagreement about what the facts mean, then sometimes both perspective can be true at the same time. This is however not as often the case as I wish it would be..
- hutzlibu 6y ago"If one side says it rains and the other says it doesn't, agreeing to disagree is wrong" No. Agreeing to disagree is accepting, that a subject is disputed with different, even contradicting opinions. An AI could in theory extract both versions and present them as disputed. Meaning, there are different definitions of a word and the correctness of facts. And "raining or not" is also not as simple as you think. A person from spain will consider a certain state as raining, which a british person might see as some humidity in the air ..
- yters 6y agoIsn't this the same as expert systems that led to the first AI winter?
- 082349872349872 6y agoWeren't expert systems the second AI winter? In any case, I see the end of the cold war as being the driving factor behind that winter, whatever its ordinal.
- harperlee 6y agoMaybe, but that doesnt mean this cant be pulled off. Neural networks were dismissed as non viable and look at them now!
- zelphirkalt 6y agoThe semantic structure is the structure of the language (or the independent thing between languages). This does not automatically facilitate machine Understandable knowledge. You would need to write the code to understand it first, which is probably almost as difficult as understanding English for example. Only when relations are defined in a kind of Prolog style in those examples it will be usable as knowledge about things other than language. A computer might spit out texts which it guessed are connected to some question you ask it though. Does not mean it understands the relations of things. But when can we ever really say "a machine understands" something? So perhaps there is not much of a difference?