<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rdf:RDF [
 <!ENTITY rdf 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
 <!ENTITY rdfs 'http://www.w3.org/2000/01/rdf-schema#'>
 <!ENTITY owl 'http://www.w3.org/2002/07/owl#'>
 <!ENTITY swrc 'http://swrc.ontoware.org/ontology#'>
 <!ENTITY xsd 'http://www.w3.org/2001/XMLSchema#'>
]>



<rdf:RDF
xml:base="http://www.bibsonomy.org/author/Murray/acquisition"
 xmlns:rdf="&rdf;"
 xmlns:rdfs="&rdfs;"
 xmlns:owl="&owl;"
 xmlns:swrc="&swrc;"
 xmlns:xsd="&xsd;"
 >

 

<owl:Ontology rdf:about="">
  <rdfs:comment>BibSonomy publications for/author/Murray/acquisition</rdfs:comment>
  <owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/>
</owl:Ontology>
  <rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/252942f394b70f8132982ac0012b5d58e/neilernst">
    <rdf:type rdf:resource="&swrc;Article"/>
    <swrc:journal>International Journal of Man-Machine Studies</swrc:journal><swrc:pages>23--49</swrc:pages><swrc:title>Visualizing and representing knowledge for the end user - a review</swrc:title><swrc:volume>38</swrc:volume><swrc:year>1993</swrc:year><swrc:keywords>acquisition cognition information knowledge modeling software visualization </swrc:keywords><swrc:date>2006-03-24 16:34:33.0</swrc:date><swrc:hasExtraField>
    <swrc:Field swrc:key="id" swrc:value="121807"/>
  </swrc:hasExtraField>
<swrc:hasExtraField>
    <swrc:Field swrc:key="priority" swrc:value="0"/>
  </swrc:hasExtraField>
<swrc:hasExtraField>
    <swrc:Field swrc:key="comment" swrc:value="early paper on info vis, a survey of early tools. Good for background. Good references. - defines knowledge to be rather specific - divides infovis into &#039;program visualization&#039; and &#039;visual programming&#039; ?? more categories than that surely - &#034;a major problem area within Visual Programming is that of identifying suitable representational formalisms&#034; - makes point that no single formalism can be sufficiently general - Musen made program OPAL - uses flowchart to capture procedure for drug assignment - GILT &#039;takes a graph layout and combines it with icons&#039; - sounds similar to SHriMP - lot of tools based on LISP and showing how it functions and combines - KEATS (Motta et al) is a tool to do visual knolwedge acquisition - the thing missing is empirical validation: so you designed this tool, but who uses it? Is it useful? I&#039;ve never heard of it nor used its lessons in my work so maybe not - &#034;for many of these systems one of the criteria is that the user be an expert in the domain&#034; - check out ZOO (riekert 1988) - frame based kR and KIM [McAleese] - wonder if these tools have any list of questions they are trying to answer - what is required etc. What work has been done since then? (15 years since) - I think the tools leveraging Prolog or LISP are much too specific. Esp as these languages don&#039;t have common interpretations (different versions, different producers, may mean that the tool is not compatible). A truly useful tool will be rather language neutral - task is to find useful abstractions and represent them - that makes the job of getting a good visualization quite simple. - comment on the future- people offer reservations - must address these complaints somewhere - Liebermann - what has this guy done? honestly, the contributions are so nonsensical that it seems he&#039;s just some itinerant wandering moron who can&#039;t figure out a useful product"/>
  </swrc:hasExtraField>
<swrc:author>
  <rdf:Seq>
  <rdf:_1><swrc:Person swrc:name="B. Murray" /></rdf:_1>
  <rdf:_2><swrc:Person swrc:name="E. Macdaid" /></rdf:_2>
  </rdf:Seq>
</swrc:author>

<swrc:editor>
  <rdf:Seq>
  </rdf:Seq>
</swrc:editor></rdf:Description>
</rdf:RDF>