[1] Not the same as a 'knol', which as defined by Google was not a unit. A real knol would be a single atomic fact.
[1] Not the same as a 'knol', which as defined by Google was not a unit. A real knol would be a single atomic fact.
Wittgenstein and Russell tried to build philosophical atomism and it fell apart.
http://plato.stanford.edu/entries/wittgenstein-atomism/#DisL...
You're making a common mistake, which is to think of Wikipedia as a collection of facts. It's a collection of verifiable statements from reliable sources, or reasonable summaries thereof. "Reliable" is a collective judgment call, and even "verifiable" can be tricky sometimes if it's not an online resource or if we're summarizing.
So what you really want is a kind of source tracing. You want to know that when one statement is put into question, everything that followed from that statement is also questionable.
With encyclopedic content, the consensus 'fact' is useful, plus the level and strength of general agreement over time is useful, plus the alternative 'facts' are useful.
Wikipedia is too much a collection of the most obstinate authors' latest opinions. It's saving grace is the 'History' tab, which adds a lot of value, at least for me.
"37 minutes ago hilyan was hoping that the next generation of wikis (especially as used by wikipedia) would introduce an underlying 'fact unit' [1] layer on which articles are built, effectively separating edit wars from verification wars.
[1] Not the same as a 'knol', which as defined by Google was not a unit. A real knol would be a single atomic fact."
I will interpret a lack of responses as evidence for failure. ;)
(declare hilyan-hope)
(declare footnote-constraint)
(let [t universal-timestamp]
(said AndrewOMartin t
(status hoping hilyan
(- t (minutes 37))
hilyan-hope))
(said google (undefined-past)
(let [knol (gensym)]
(not (unit knol))))
(let [knol (gensym)]
(single-atomic-fact knol)))
(def hilyan-hope
(let [next-wiki-generation (gensym)
fact-unit (gensym)
article (gensyn)]
(introduces next-wiki-generation fact-unit)
(underlies next-wiki-generation fact-unit)
(footnote-constraint fact-unit)
(underlies fact-unit article)
(cause fact-unit (separate verification-wars edit-wars))))
(def footnote-constraint [fact-unit]
(let [knol (gensym)]
(!= knol fact-unit)))
The DSL could be improved :)Edit: So a couple of things about this exercise: yes, it took me more time (and space) than your phrase. On the other hand, I specified some extra information. Some ambiguities about your phrase needed to be explicit, so that's a win for a more formal language. Also, there's some more effort involved, so I could have the time to think more about what I say. It would be great to have an interactive tool to think and write in a more formal language, even if it is not meant to be compiled to assembler.
I have a side project that touches this tangentially (the code is made up, though!), but I can't find a lot of time for it :(
Does anybody know if something like this exist? Somethig like a wiki/REPL/mindmap sandbox for concepts.
Cracking this problem could bring about an entirely new era of debate & communication.
Sites like Larry Sanger's infobitt.com attempt to break down news stories into their facts, by letting contributors asses the factuality of each piece of information. However, I believe that fact checking current news stories is over-rated. Why do we need to fact-check the old story, when a more accurate news story will come along anyway? Again this stems from the wiki, formatting the page as an article, rather than, say, a stream of information.
There are other solutions that can mitigate problems that arise from using wikis, such as assigning anonymous editors to check content, and paying editors to contribute. I have implemented many of these on my site, Newslines (http://newslines.org) which crowdsources news, but uses each news event as the primary data type.