8 |
the browser window (like those JavaScript-based shifting-fucus |
the browser window (like those JavaScript-based shifting-fucus |
9 |
"3D"-navigations that were fashionable a year or two ago)? |
"3D"-navigations that were fashionable a year or two ago)? |
10 |
|
|
11 |
|
COMMENT: Need to talk about us starting from a consistent |
12 |
|
datamodel to avoid technical difficulties with trying to multidirectionalize |
13 |
|
one-directional web links. |
14 |
|
|
15 |
|
That the applications to web are beyond the scope of this article; |
16 |
|
the article is about the UI |
17 |
|
|
18 |
- What about users` learning curves? Having to learn a new navigation |
- What about users` learning curves? Having to learn a new navigation |
19 |
paradigm always means added stress at first and may create an exit |
paradigm always means added stress at first and may create an exit |
20 |
point for new users. Do you have empirical data on user-reactions? |
point for new users. Do you have empirical data on user-reactions? |
21 |
|
|
22 |
|
COMMENT: Ongoing, experimental system - not much data yet |
23 |
|
|
24 |
- How far can the unique backgrounds go? Color coding always poses |
- How far can the unique backgrounds go? Color coding always poses |
25 |
a conceptual problem - because you run out of distinctive colors/ |
a conceptual problem - because you run out of distinctive colors/ |
26 |
patterns and because they impose another learning curve. - Is this |
patterns and because they impose another learning curve. - Is this |
35 |
does the tool crawl? Would the software be a permanent replacement |
does the tool crawl? Would the software be a permanent replacement |
36 |
of other retrieval tools (folder-structure)? |
of other retrieval tools (folder-structure)? |
37 |
|
|
38 |
|
COMMENT: right, we didn't make this clear... |
39 |
|
|
40 |
2: |
2: |
41 |
|
|
42 |
There is a deep and rich history of research surrounding annotation |
There is a deep and rich history of research surrounding annotation |
45 |
anticipated). Look for author names Denoue, Golovchinsky, Wilensky, |
anticipated). Look for author names Denoue, Golovchinsky, Wilensky, |
46 |
Brush, Bargeron, and Marshall. |
Brush, Bargeron, and Marshall. |
47 |
|
|
48 |
|
COMMENT: Must read |
49 |
|
|
50 |
3: |
3: |
51 |
|
|
52 |
There is no reason whatsoeer to believe the explanation based |
There is no reason whatsoeer to believe the explanation based |
54 |
<http://doi.acm.org/10.1145/208666.208687>. However, innovative |
<http://doi.acm.org/10.1145/208666.208687>. However, innovative |
55 |
new interfaces don`t need to be rigorously justified before testing. |
new interfaces don`t need to be rigorously justified before testing. |
56 |
|
|
57 |
|
COMMENT: 20 was justification for our intuition, |
58 |
|
but non-rigorous as said. |
59 |
|
|
60 |
Clearly the user interface is intended for a particular (if not |
Clearly the user interface is intended for a particular (if not |
61 |
specialiazed) type of hypertext user. It must be clear in the |
specialiazed) type of hypertext user. It must be clear in the |
62 |
article who the target group is or what their makeup will be. |
article who the target group is or what their makeup will be. |
63 |
|
|
64 |
|
COMMENT: Very true. |
65 |
|
|
66 |
|
I guess our target group for the first versions is |
67 |
|
academic researchers, and their handling of sources. |
68 |
|
|
69 |
Everyone is familiar with the apparent paradox of spatial reasoning |
Everyone is familiar with the apparent paradox of spatial reasoning |
70 |
ability and success with hypertext. This issue must be addressed |
ability and success with hypertext. This issue must be addressed |
71 |
if only in passing. |
if only in passing. |
72 |
|
|
73 |
|
COMMENT: What paradox? The only hypertext that really |
74 |
|
works is one where the documents have been structured |
75 |
|
really closely to a tree - see the common web navigation |
76 |
|
paradigms |
77 |
|
|
78 |
In section 2.2: if evidence is available (aboutthe amount of attention |
In section 2.2: if evidence is available (aboutthe amount of attention |
79 |
needed) then it should be presented. It would help readers if |
needed) then it should be presented. |
80 |
|
|
81 |
|
COMMENT: None yet, except that mouseovers are not nice. |
82 |
|
|
83 |
|
It would help readers if |
84 |
the ideas presented in the article were placed in more context, |
the ideas presented in the article were placed in more context, |
85 |
for instance how do they relate to Polle Z.`s fluid annotations |
for instance how do they relate to Polle Z.`s fluid annotations |
86 |
(as another method of dealing with *some* of the same issues)? |
(as another method of dealing with *some* of the same issues)? |
87 |
|
|
88 |
|
COMMENT: didn't we say this? |
89 |
|
|
90 |
instead of ``improves recognizability`` would it be more correct to |
instead of ``improves recognizability`` would it be more correct to |
91 |
say it could promote more recognizability? |
say it could promote more recognizability? |
92 |
|
|
93 |
|
COMMENT: [tjl] I really can't say |
94 |
|
|
95 |
What are affine functions? Did you mean affined? |
What are affine functions? Did you mean affined? |
96 |
|
|
97 |
|
COMMENT: We need to tone down the tech level of the article. |
98 |
|
Affine is a mathematical term for a generalization of linear, |
99 |
|
i.e. linear with constant offset. |
100 |
|
|
101 |
|
|
102 |
|
|
103 |
|
|
104 |
4: |
4: |
105 |
|
|
106 |
The biggest value of this paper is to implement a graphic system |
Unique backgrounds is painting a buoy with a unique color to |
|
that displays a page of hypertext and related pages in non-mechanical |
|
|
way. The authors` idea is buoys and unique backgrounds. A buoy is a |
|
|
small area to display the part of the content of the related page |
|
|
like floating on the water. It gives a natural atmosphere to the |
|
|
user. Unique backgrounds is painting a buoy with a unique color to |
|
107 |
allow the user to specify the target buoy easily. |
allow the user to specify the target buoy easily. |
108 |
|
|
109 |
|
COMMENT: Sigh - not. Need to make this more clear. |
110 |
|
|
111 |
I understand that the authors implemented a sophisticated system to |
I understand that the authors implemented a sophisticated system to |
112 |
display hypertext in a natural way. I also understand the authors` |
display hypertext in a natural way. I also understand the authors` |
113 |
efforts to display buoys without overlaps of buoys and prevention |
efforts to display buoys without overlaps of buoys and prevention |
114 |
of the user`s focus. However I`m still not sure that each of these |
of the user`s focus. |
115 |
|
|
116 |
|
However I`m still not sure that each of these |
117 |
devices are really novel in the filed of visualization or human |
devices are really novel in the filed of visualization or human |
118 |
interface. Only proposing buoys and unique background colors as |
interface. |
119 |
|
|
120 |
|
COMMENT: They really appear to be, and we HAVE to make that clear. |
121 |
|
|
122 |
|
Only proposing buoys and unique background colors as |
123 |
just an interesting display method is insufficient to present in |
just an interesting display method is insufficient to present in |
124 |
this conference. |
this conference. |
125 |
|
|
126 |
|
COMMENT: Agreed now - we need data. |
127 |
|
|
128 |
5: |
5: |
129 |
|
|
130 |
It is a hard task to describe a highly dynamic user interface using |
It is a hard task to describe a highly dynamic user interface using |
131 |
words and static monochrome figures. This paper does not succeed |
words and static monochrome figures. This paper does not succeed |
132 |
in the task -- though it is by no means a hopeless failure. A few |
in the task -- though it is by no means a hopeless failure. |
133 |
|
|
134 |
|
COMMENT: We tried hard and failed -- we need to try HARDER. |
135 |
|
|
136 |
|
A few |
137 |
SIMPLE and REAL examples early in the paper would help greatly |
SIMPLE and REAL examples early in the paper would help greatly |
138 |
(i.e. like Figure 1, but showing the new interface). The only |
(i.e. like Figure 1, but showing the new interface). The only |
139 |
real screen dumps occur at the very end (Figure 7) and these are |
real screen dumps occur at the very end (Figure 7) and these are |
145 |
(I can understand the authors` desire to show the full capabilities |
(I can understand the authors` desire to show the full capabilities |
146 |
of their system, but this goes too far, too fast.) |
of their system, but this goes too far, too fast.) |
147 |
|
|
148 |
|
COMMENT: This is really good instructions for us. |
149 |
|
|
150 |
Another problem I have with the paper is that it is premature. |
Another problem I have with the paper is that it is premature. |
151 |
There is no description of any user testing at all: if you are |
There is no description of any user testing at all: if you are |
152 |
describing a new interface it helps to have some evidence -- even |
describing a new interface it helps to have some evidence -- even |
153 |
if tenuous -- that users see some advantage in it. |
if tenuous -- that users see some advantage in it. |
154 |
|
|
155 |
|
COMMENT: At least anecdotal stuff |
156 |
|
|
157 |
Two detailed points: |
Two detailed points: |
158 |
|
|
159 |
(a) at a low level, there are problems with the rendering of the |
(a) at a low level, there are problems with the rendering of the |
160 |
paper: in two cases the first column extends into the second and |
paper: in two cases the first column extends into the second and |
161 |
obscures it. |
obscures it. |
162 |
|
|
163 |
|
COMMENT: Ouch - we really need to read the LaTeX output |
164 |
|
on overfull hboxes. |
165 |
|
|
166 |
(b) it was unclear to me whether a fragment has to be textual (the |
(b) it was unclear to me whether a fragment has to be textual (the |
167 |
first paragraph of 2.2 implies this). |
first paragraph of 2.2 implies this). |
168 |
|
|
169 |
|
COMMENT: Make sure it's stated it's not so. |
170 |
|
|
171 |
|
|
172 |
|
|
173 |
Assoc. Papers Chair: |
Assoc. Papers Chair: |
175 |
There was some confusion over the underlying Zig-Zag basis for the |
There was some confusion over the underlying Zig-Zag basis for the |
176 |
work, which although a central driver for your work, is somewhat |
work, which although a central driver for your work, is somewhat |
177 |
secondary in this paper and not given enough room to properly explain |
secondary in this paper and not given enough room to properly explain |
178 |
with all its concepts and terminology. Is this an interface only |
with all its concepts and terminology. |
179 |
|
|
180 |
|
COMMENT: Ouch. Do we need to start to state in every paper |
181 |
|
we make that this has nothing to do with ZZ? |
182 |
|
|
183 |
|
Well, probably describing RDF as our basis is sufficient. |
184 |
|
|
185 |
|
Is this an interface only |
186 |
relevant to hypertextual transclusion, or applicable to any domain |
relevant to hypertextual transclusion, or applicable to any domain |
187 |
where there is hypertext or annotation? |
where there is hypertext or annotation? |
188 |
|
|
189 |
|
COMMENT: The transclusion is not the important part... |
190 |
|
RDF structural links also are there. |
191 |
|
|
192 |
|
NEED TO MAKE THIS CLEAR. |
193 |
|
|
194 |
Contextualise it better to the wider work on annotation |
Contextualise it better to the wider work on annotation |
195 |
interfaces. Add earlier examples to ground it in the reader`s |
interfaces. Add earlier examples to ground it in the reader`s |
196 |
mind. Given that it`s a user interface project, start to plan solid |
mind. Given that it`s a user interface project, start to plan solid |
197 |
studies that assess what support it adds for realistic user tasks |
studies that assess what support it adds for realistic user tasks |
198 |
compared to current UIs. |
compared to current UIs. |
199 |
|
|
200 |
|
COMMENT: Yes. These are planned, but we didn't make it in time |
201 |
|
for this year's conference. Next year, we'll have something |
202 |
|
interesting. |
203 |
|
|
204 |
The detailed reviewer comments should also provide valuable feedback |
The detailed reviewer comments should also provide valuable feedback |
205 |
for the presentation and advancement of this work. It will help in |
for the presentation and advancement of this work. It will help in |
206 |
the future to ensure quality layout of the document (no overflowing |
the future to ensure quality layout of the document (no overflowing |
207 |
columns etc, and for such a rich interface, a companion web page |
columns etc, |
208 |
|
|
209 |
|
COMMENT: Our bad. |
210 |
|
|
211 |
|
and for such a rich interface, a companion web page |
212 |
with colour screenshots or even better a screen movie would be worth |
with colour screenshots or even better a screen movie would be worth |
213 |
considering to communicate the work). |
considering to communicate the work). |
214 |
|
|
215 |
|
COMMENT: This we HAVE to do, if it's so explicitly allowed / encouraged. |
216 |
|
My impression was that articles were judged based on the |
217 |
|
articles but if the official word is that any extra material |
218 |
|
*will* be considered, it changes several things. |
219 |
|
|
220 |
|
|
221 |
|
|