i think the problem is analogous to designing
html. In theory, it should be left to the graphic artist / designer,
however, because of the state of things, it falls into the hands of
the programmer. Until a system is better mapped out, it will certainly
require a closer relationship between the visual designer and the
Writing for the newMedia necessitates a certain familiarity
with the structure and layout of any interActive state (cdRom or
web). However, as i'm discovering (and in the process of implementing),
a database becomes the
sole focus for the technical design team (i.e. what kind of information
is this database responsible for?). Once
this mechanism is established, the visual design team can layout the
rules and the look for the interFace
(the way you might do traditionally or in pageMaker or quark).
So the short answer is that the navigation and
the logic of interactivity
is very dependent upon the information model at first.
Once that is established, the designer and writer can
set about working on the presentation,
in much the same way a script writer would work, i.e. storyboard structure.
up on xml
(it's what may replace html)
basically its goal is to separate the context
from the layout.
All objects have both a context (i.e. a meaning) and a layout
(a place in space).
When xml becomes fully used in the web, you will see how web
designers will be much more graphic oriented, while the context,
the content (as in meaning of the words etc.) will exist separate
from the look.