Talk:Knowledge Interchange Format

It should be merged. Tim 05:16, 8 April 2007 (UTC) Yes, I thing It should be merged, becouse both describe the same thing. Eduardo Moraes(Ufpe)

Possible Plagarism Issue
I just started looking at this article and did a Google search and one of the first sites that came up was this: http://www-ksl.stanford.edu/knowledge-sharing/kif/  Normally I would wonder who was stealing from whom but given the source at Stanford and what I already know about KIF I think it's a virtual certainty that the Stanford site is the source not vice versa. I'm probably going to rewrite this article anyway but in case I get distracted wanted to document this. --MadScientistX11 (talk) 22:55, 6 August 2014 (UTC)
 * ✅ I've fixed this. Removed the plagarized text and rewrote the article to include better linking and to make sure everything was appropriately referenced. Essentially the KIF manual by Genesereth and friends backs up all the significant claims except the last paragraph which has two additional refs. --MadScientistX11 (talk) 19:53, 7 August 2014 (UTC)

Undid edit about Knowledge Acquisition
I just reverted an edit that added this to the beginning: " which is basically in perspective of Intelligent Knowledge Acquisition ." First, I thought this was clumsy English and also saying "intelligent" knowledge acquisition is redundant. But more importantly KIF is not primarily about Knowledge Acquisition. Knowledge acquisition refers to getting domain knowledge encoded as rules and ontologies. I.e., going from the informal knowledge stored in the heads of experts to formal representations of that knowledge that a computer can use. KIF is about sharing formal representations of knowledge. Its essentially a tool for technical people not domain experts. To some extent you can say it facilitates Knowledge Acquisition but you could essentially say that about any tool that is involved in a knowledge based system. The kinds of technologies that are specifically relevant to knowledge acquisition are things like explanation engines (that explain the reasoning of a system in text or graphics that is intuitive to users), tools to automatically capture rules and ontologies from existing documents, graphical ontology editors such as Protege, etc. --MadScientistX11 (talk) 15:57, 23 November 2015 (UTC)