[x3d-public] unconnected proto fields

[Andreas Plesch]

A ProtoDeclaration may have fields in the interface definition which
are then not connected to any fields or nodes in the ProtoBody.

This is usually not the case since it does not seem to serve a
purpose. Nonetheless authors may inadvertently define such unconnected
fields in a ProtoInterface.

Is there a requirement for such a connection ?

Could there be a sensible use case for unconnected Proto fields ?

How should a browser react to this?

Silently ignore ? This is apparently the behaviour of many X3D
browsers currently.
Fail early ? To prevent any subsequent problems flowing from such an
occurrence ? This is what x3dom currently does.
A warning ? Seems reasonable unless there is a spec. requirement.

-Andreas

-- 
Andreas Plesch
Waltham, MA 02453