At 11:43 AM 3/21/00 -0500, John Cowan wrote:
Not quite the issue. VRML, which is not XML-compatible, is application/vrml.
If VRML is reformulated to be XML-compatible (in a new version), do we
then register application/vrml-xml? I think we do.
If/when that happens, it's not going to be called VRML any more; it's going
to be a new kind of thing. I believe currently they go by the internal
monicker of "x3d"; so that would be
model/x3d-xml
The idea is to avoid the existence of both foo/bar and foo/bar-xml - SVG,
for example, plans to (already has?) register only image/svg-xml. -Tim