On Fri, 02 Mar 2001 11:36:16 -0500, Ralph Hartley wrote:
>But not only are names ugly, they are also untrustworthy and
>incompatible. They really need to be converted into something universal
>and unambiguous. This translation needs to be done AS CLOSE TO THE
>SOURCE OF THE DATA AS POSSIBLE. Otherwise something will be lost in
>translation.
Sounds like using a common unit base for storing data. The problem is the original data is not stored; it must
be recreated from the "new" data. If pulling the original station ID back into the shot is too much work, is it
really worthwhile? Does the original data get corrupted because is has been changed, even by this simple
substitution?
>How do those editors handle attributes of type IDREF? If there is no
>matching ID, the file is not valid XML. Do "XML editors" always produce
>valid XML?
Depends. If there is a DTD or Schema and validation is enabled, an attempt to insert an invalid element will
throw an exception (in Java and probably C/++ as well). So you can create anything you want but if you want
it valid, there must be some sort of template for the parser/DOM manager to use for comparison.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Mon Apr 02 2001 - 18:00:00 CEST