[X3D-Public] [X3D] containerField is should or must ?

[Alan Hudson]

On 8/5/2010 6:59 PM, Tony Parisi wrote:
>> There's no question that containerField is made necessary by other
>> aspects of the XML encoding. Unfortunately, time has shown that those
>> aspects are themselves poor design choices.
>>
>> fieldValue wrapper nodes were talked about some months ago as an
>> approach to resolve issues with overly large attribute values. These
>> wrappers also render containerField unnecessary; and in light of their
>> availability, it probably makes sense to deprecate containerField.
>>
As it stands now we avoid the XML encoding for any real sized files.  I 
am a fan of being able to completely validate the file.  So when I teach 
X3D I use the XML encoding to help them catch errors.  But for 
production usage we stick with .x3dv or .x3db.