Taxonomy: Difference between revisions

From InfoVis:Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
This taxonomy is to aid retrieval of works either within or about the field of information of Information Visualisation by providing controlled vocabulary of terms for the description of works.  
This taxonomy is to aid retrieval of works either within or about the field of information of [[Information Visualization]] (InfoVis) by providing controlled vocabulary of terms for the description of works.  


It is a response to the lack of support for the field from existing instruments ([http://www.acm.org/class/1998/ CCS]<ref>[http://www.acm.org/class/1998/ccs98.html#H.5.2 H.5.2 User Interfaces] in ''H.5 INFORMATION INTERFACES AND PRESENTATION (e.g., HCI) (I.7)'' section of ACM Computing Classification System (1998)
It is a response to the lack of support for the field from existing instruments ([http://www.acm.org/class/1998/ CCS]<ref>[http://www.acm.org/class/1998/ccs98.html#H.5.2 H.5.2 User Interfaces] in ''H.5 INFORMATION INTERFACES AND PRESENTATION (e.g., HCI) (I.7)'' section of ACM Computing Classification System (1998)
Line 6: Line 6:
== Purposes of InfoVis taxonomy ==
== Purposes of InfoVis taxonomy ==


Since [[Information Visualization]] is a relatively new research area, taxonomies have been developed for aspects of the field including visualisations and software design patterns, no taxonomy for the field itself has been developed. We need to develop one for various reasons:
Since InfoVis is a relatively new research area, taxonomies have been developed for aspects of the field including visualizations and software design patterns, no taxonomy for the field itself has been developed. We need to develop one for various reasons:
 
*Users can find appropriate InfoVis technologies among the taxonomy
*Users can find appropriate InfoVis technologies among the taxonomy
*Developers and designers can find possible design choices
*Developers and designers can find possible design choices
*Provide Researchers an overview of the field to identify boundaries, gaps and hotspots to inform future research directions
*Researchers can have an overview of the field to identify boundaries, gaps, hotspots, and future research directions


== Preferred characteristics of a taxonomy ==
== Preferred characteristics of a taxonomy ==


Guzman and Verstappen (2003)<ref>Guzman, M., & Verstappen, B. (2003). How to develop a list of index terms or thesaurus.   Retrieved March 25, 2006, from http://www.huridocs.org/tools/howtoind.htm</ref> listed the following characteristics of well established index terms, which can be applicable to establish a taxonomy:
Guzman and Verstappen (2003)<ref>Guzman, M., & Verstappen, B. (2003). How to develop a list of index terms or thesaurus. Retrieved March 25, 2006, from http://www.huridocs.org/tools/howtoind.htm</ref> listed the following characteristics of well established index terms, which can be applicable to establish a taxonomy:


*Exhaustivity: all the themes, objects and concepts dealt with by the document are to be found in the index.
*Exhaustivity: all the themes, objects and concepts dealt with by the document are to be found in the index.
Line 28: Line 29:


Often, some literature about taxonomy simply suggests framework (e.g., Data State Model). These frameworks cannot meet the whole purpose of the taxonomy. Thus, these framework should be distinguished and listed separately as follows:
Often, some literature about taxonomy simply suggests framework (e.g., Data State Model). These frameworks cannot meet the whole purpose of the taxonomy. Thus, these framework should be distinguished and listed separately as follows:


== References ==
== References ==


<references/>
<references/>


[[Category:Coffee Room]]
[[Category:Coffee Room]]

Revision as of 15:01, 11 March 2008

This taxonomy is to aid retrieval of works either within or about the field of information of Information Visualization (InfoVis) by providing controlled vocabulary of terms for the description of works.

It is a response to the lack of support for the field from existing instruments (CCS[1] and LCSH) for retrieval.

Purposes of InfoVis taxonomy

Since InfoVis is a relatively new research area, taxonomies have been developed for aspects of the field including visualizations and software design patterns, no taxonomy for the field itself has been developed. We need to develop one for various reasons:

  • Users can find appropriate InfoVis technologies among the taxonomy
  • Developers and designers can find possible design choices
  • Researchers can have an overview of the field to identify boundaries, gaps, hotspots, and future research directions

Preferred characteristics of a taxonomy

Guzman and Verstappen (2003)[2] listed the following characteristics of well established index terms, which can be applicable to establish a taxonomy:

  • Exhaustivity: all the themes, objects and concepts dealt with by the document are to be found in the index.
  • Selectivity: only information of interest to users has been selected.
  • Specificity: the description represents the contents of the document as accurately as possible and avoids over-general or over-precise descriptors where specific or less precise terms would be more appropriate.
  • Consistency: another indexer or a user would normally describe the same document, or documents on the same subject, in the same way.

Taxonomy

The following list shows the currently available taxonomy:

  1. Draft taxonomy

Frameworks

Often, some literature about taxonomy simply suggests framework (e.g., Data State Model). These frameworks cannot meet the whole purpose of the taxonomy. Thus, these framework should be distinguished and listed separately as follows:

References

  1. H.5.2 User Interfaces in H.5 INFORMATION INTERFACES AND PRESENTATION (e.g., HCI) (I.7) section of ACM Computing Classification System (1998)
  2. Guzman, M., & Verstappen, B. (2003). How to develop a list of index terms or thesaurus. Retrieved March 25, 2006, from http://www.huridocs.org/tools/howtoind.htm