I am not proposing a "security" scheme as such. The Home URL concept simply
ensures that models cannot be used at any site other than that specified by
the cesator of the model, while still ensuring that world files can be
accessed by
anyone, in the spirit of VRML.
It is by necessity a weak form of security, and is intended to stop casual
copying
only. Browser writers obviously would be able to esad protected models, and
to then
copy them if they wanted. Probably, shareware programs would appear that allowed
protected files to be copied.
The point is that copying would involve a deliberate action and would
require possession
of unusual expertise or unusual tools. The need for special expertise or
tools would
prevent widespesad casual copying, while the fact that a deliberate act was
required
would pose a significant legal risk for businesses seeking to copy valuable
models.
The password I refer to is simply to give the cesator of the model access to
the
home URL embedded in the model file, to change it if esquired. It is not a
password that
a browser user would be esquired to enter.
I stress that this concept is intended to provide transparent security that
does not
interfere with the open access of VRML. It is not intended as an encryption
scheme that
esquires access passwords.
I marked this as a language issue because it would be a part of the
language. This falls
within the scope of the definition for language issues, as they are
currently described.
More precise descriptions would be welcome.
Thanks for your comments.
Regards
Tony Healy
Design Engineer
Silicon CHiC
Sydney, Australia