I am moving away from .json and towards .x3dj to distinguish from other .json for Castle file loading. X3DJSAIL should do similar. As a first step, .x3dj file extension should be allowed when toFileJSON() is called.
Good idea,. We need to proceed deliberately since .x3dj is not yet an approved MIME type. Further, using .json means many tools handle the file properly.
Action plan:
- add a preference to X3DJSAIL.properties allowing user to change default
- review on x3d-public then submit MIME type application to IETF
- once approved and propagated, consider which extension is preferred default
- ensure the forthcoming Web3D standard on JSON encoding documents all of this correctly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another thing you’re probably aware of is Holger’s x3d-tidy requires
specifying .x3dj.
I believe that .json should remain an option in X3DJSAIL. Putting the
default in the properties file is good.
Changing X3DJSAIL properties is a good idea, just realize my code is spread
across many folders, so setting the properties file full path in an
environmental variable is desirable, if not already done.
What I will attempt to do in X3DJSONLD is use an environmental variable for
the extension, some work is already done. I have been using JSONEXT
environmental variable for some things. This involves testing many
scripts I haven’t changed for years. Poor programming on my part. What I
will hopefully come up with is a way to alter one string, and the whole
system just works.
Good idea,. We need to proceed deliberately since .x3dj is not yet an
approved MIME type. Further, using .json means many tools handle the file
properly.
Action plan:
- add a preference to X3DJSAIL.properties allowing user to change default
- review on x3d-public then submit MIME type application to IETF
- once approved and propagated, consider which extension is preferred
default
- ensure the forthcoming Web3D standard on JSON encoding documents all of
this correctly.
Status: open Milestone: X3D4 Created: Sun Sep 14, 2025 02:43 AM UTC by John W Carlson Last Updated: Sun Sep 14, 2025 02:43 AM UTC Owner: Don Brutzman
I am moving away from .json and towards .x3dj to distinguish from other
.json for Castle file loading. X3DJSAIL should do similar. As a first step,
.x3dj file extension should be allowed when toFileJSON() is called.
Good idea,. We need to proceed deliberately since .x3dj is not yet an approved MIME type. Further, using .json means many tools handle the file properly.
Action plan:
- add a preference to X3DJSAIL.properties allowing user to change default
- review on x3d-public then submit MIME type application to IETF
- once approved and propagated, consider which extension is preferred default
- ensure the forthcoming Web3D standard on JSON encoding documents all of this correctly.
Another thing you’re probably aware of is Holger’s x3d-tidy requires
specifying .x3dj.
I believe that .json should remain an option in X3DJSAIL. Putting the
default in the properties file is good.
Changing X3DJSAIL properties is a good idea, just realize my code is spread
across many folders, so setting the properties file full path in an
environmental variable is desirable, if not already done.
What I will attempt to do in X3DJSONLD is use an environmental variable for
the extension, some work is already done. I have been using JSONEXT
environmental variable for some things. This involves testing many
scripts I haven’t changed for years. Poor programming on my part. What I
will hopefully come up with is a way to alter one string, and the whole
system just works.
John
On Sun, Sep 14, 2025 at 10:05 AM Don Brutzman brutzman@users.sourceforge.net wrote:
Related
Tickets: #73