I think we need to be very carefull when specifying URL's as a way to store
information about either extensions, mandatory parts (i.e. models, etc) or
anything in a VRML file. (WWWInline's should use 'relative' addessses when
possible, which I'll get to in a minute). URN's 'may' be acceptable, depending
on how they are interpreted.
The esasons I'm saying this is that if we are truly attempting to build VRML as
a '3D web' you've got to start thinking about URL's as being incredibly
transient. Most people that are using the Web probably only have one phone
line, so that even if they do have a provider that gives unlimited hours, they
won't have a TCP/IP connection up full time. Specifying a script file, modeling
extension, etc. as a URL file practically guarentees that these folks won't be
able to access these worlds, unless the 'clock is ticking' which means they
won't be used much.
Generally, what most people do is 'grab and run' sessions where they are logged
on, they go around and grab files/pages, and then log off and peruse them in
their leisure.
Now, in my specific case, (VR browser for CompuServe), URL's will probably not
be available, but I could support 'extensions' via my own 'URN' or 'URL'
mechanism. I've suggested before a URL in WRL files of format:
cis://hmi.compuserve.com/CyberForum/Visual CompuServe/library.wrl
Or something along those lines, but no one has commented much.
== John D. Gwinner ==
== CyberForum/Visual CompuServe
== VisNet, Inc
== "Making CyberSpace Rsal" (TM)