I'm new to this list, so pardon me if this has been covered.
Are there ways or plans to extend <area> to handle 3D references?
For example with archeological sites, having a 3D spatial profile, the
<structMap> works nicely for representing site/building/room/surface/detail
hierarchies. And xml and image files are nicely referenced from each <div>
with <fptr>. In our case, each building <div> also has a QTVR file
representing its 3D space. The problem comes when referring to a specific
region of that QTVR from room, surface, or detail <div> levels. The natural
way to do it would be to use <area> to hold specific node_id, pan_angle,
tilt_angle, and field_of_view parameters on the QTVR file. But I don't see
how to use <area> to accommodate these particular QTVR parameters, or
indeed any other 3D parameters.
What we'll probably do is package all QTVR view parameters in an xml file
and refer to specific "views" via <area ..BETYPE="IDREF"/>. Would that be
the right way to handle this? Is there a better way? These view parameters
aren't global to the QTVR file but rather unique to specific views. So
holding them solely in <area> seems truer to spirit, say if <area> were
extensible like the metadata sections.
Thanks for any suggestions,
Northwestern University, Evanston, IL. USA
[log in to unmask]