Review Comment:
The paper suggests that the problem of "semantic gap" between unstructured and structured content may be solved if the two can be authored, visualized and explored in an integrated manner. A formalism called WYSIWYM including the binding between UI elements and semantic representation models is proposed to reach the possible integration. The contributions of this paper include:
1) Propose a formalism called WYSIWYM (What You See is What You Mean), which implies a methodology of how to develop and evaluate a UI interface that users can view, explore and author semantically enriched unstructured content in a user-friendly way. The idea is interesting and somewhat original.
2) Take a comprehensive survey of different UI categorizations and UI techniques used in representing semantic models ranging from tree-based to graph-based and even hyper-graph-based, and draw a detailed binding table between varies of UI techniques and different semantic representation models. The survey requires great effort and maybe useful for tool builders to develop UI.
3) Develop two tools, RDFaCE and Pharmer, which try to show WYSIWYM formalism can help to build semantic editors with high usability. Though the article does not tell the reader what is WYSIWYM and what is not intuitively, the demos and corresponding articles on the web site provide some idea.
Though it is impressive and interesting, the following issues require further consideration:
1) The UI techniques listed are a little limited. Just list a few: 1. Techniques such as animation are not included. 2. "Associating" UI category only includes "Line connectors" and "Arrow connectors". For hierarchy relationship, nested items can be shown inside one another, the technique is widely used as suggested in reference paper [6]. 3. The "zooming" elements vary on different applications, it may be further categorized.
2) The demos mainly demonstrate highlight typed-text and some “callouts”, The UI that shows semantic representation model, such as tree, graph and hyper-graph, is not included. Furthermore, if the tree, graph and hyper-graph denote "structured content", it seems it is still unsolved about how to integration the "unstructured and structured content".
3) There is a gap between the formalism and the tools. e.g. How the formalism and different bindings guide the tool building process or helps to evaluate the tool usability?
In spite of the above issues, it may be a useful survey and a startup material for different readers to understand the key point of building UI interfaces of semantic-enriched content.
|
