[X3D-Public] [x3dom-developers] initial X3D JSON conversion support using X3dToJson.xslt
johannes.behr at igd.fraunhofer.de
Mon Oct 13 04:37:28 PDT 2014
> > Only, if you write [...]so this is more a VRML/X3D-inspired format, not "real X3D".[...], do you mean the "3D universe" will rather split into two "multiverses"?
> I meant that I'm kinda looking at it from the perspective of "if I was starting from scratch today, what would I need" than a conversion of an existing format to JSON, hence I'd totally understand if some things might not fit the goals of JSON X3D because it's probably more important for a standard with multiple encodings to be able to convert seamlessly between encodings.
Well. The question is, if JSON is a good format for all 3D aspects at all. And we don't think so:
JSON does not support compression, streaming, binary encoding, ...
But it works well for scene-graph structure data and X3D is a solid scene-graph description.
> > I think there shouldn't be a default type. Otherwise an application needs to know these default values, which again makes it harder to implement tools.
> I hesitated with the default _type and you're right, let's always specify the value: not only it is more explicit, but also the definition is usable even without knowing the container context (and remains valid even if moved to another container that doesn't have (or uses a different) default _type, hence it's simpler and safer to require _type to have a value).
> See you,
> X3D-Public mailing list
> X3D-Public at web3d.org
Dr. Johannes Behr
Head of Department: Visual Computing System Technologies
Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5 | 64283 Darmstadt | Germany
Tel +49 6151 155-510 | Fax +49 6151 155-196
johannes.behr at igd.fraunhofer.de | www.igd.fraunhofer.de
More information about the X3D-Public