[x3d-public] Please fix X3dToJson.xslt to work with Saxon-CE, Saxon-Js and xslt3

[Don Brutzman]

Several responses.

a.  X3dToJson.xslt works.  Each error you have found that is a stylesheet error has been fixed so far, the majority are false positives and reflect known (or intentional) errors in scenes.  Let's keep reducing your error population, as discussed checking "meta" tags can reveal whether an .x3d model has a known error.

b. I am using the open-source version of Saxon saxon9he.jar for greatest repeatability by others and it is included in the build.  You are welcome to use any form of saxon.  This should not effect X3dToJson.xslt since it is written according to an open standard.

Suggest that better identification and filtering of false positives is appropriate.

Thanks for your efforts.

On 4/11/2021 11:23 PM, John Carlson wrote:
> 
> 
> Please fix X3dToJson.xslt to work with modern Saxon, in particular
> xslt3. Out of 189 .x3d files, 158 of them produce non-validating JSON files.
> 
> So the question is, do I need to get a support contract with Saxon, or
> do we need to change X3dToJson.xslt for the better?
> 
> If it's too difficult to generate an X3D JSON file with newer XSLT,
> maybe we need a different JSON encoding?  I know saxon9he.jar works
> fine, I'm just worried about deprecation, future or present lack of
> support, etc.
> 
> This isn't an error here or there, it's pervasive in most of my JSON files.
> 
> (hint: search for Illegal)
> 
> Thanks,
> 
> John
> 

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman