[x3d-public] FW: X3D Ontology problem

Sun Apr 10 19:13:12 PDT 2022

Tsvetanka Bcc'ed:

I was able to get past the xmlresolver issues in X3DUOM to Ontology and
X3DJSAIL.

Here's the patch:

$ svn diff build.xml
Index: build.xml
===================================================================

--- build.xml   (revision 33085)
+++ build.xml   (working copy)
@@ -161,9 +161,11 @@
         </exec>
         <!--
https://www.saxonica.com/documentation10/#!using-xsl/commandline -->
         <echo>saxon -? help</echo>
+       <!--
         <java classname="net.sf.saxon.Transform"
classpath="${saxon.dir}/${saxon.jar};." failonerror="true">
             <arg value="-?" description="help information"/>
         </java>
+       -->
         <echo>Check for node.js installation from https://nodejs.org</echo>
         <exec executable="${node.exe}">
             <arg value="--version"/>
@@ -445,7 +447,7 @@
         <echo message="create autogenerated Java source code:"/>
         <!--
https://stackoverflow.com/questions/51916221/javax-xml-bind-jaxbexception-implementation-of-jaxb-api-has-not-been-found-on-mo
-->
         <!--
https://stackoverflow.com/questions/48204141/replacements-for-deprecated-jpms-modules-with-java-ee-apis/48279048#48279048
-->
-        <java classname="net.sf.saxon.Transform"
classpath="${saxon.dir}/${saxon.jar};." fork="${fork}" failonerror="true">
+        <java classname="net.sf.saxon.Transform"
classpath="${saxon.dir}/${saxon.jar};${X3DJSAIL.lib.dir}/xmlresolver-4.2.0.jar;${X3DJSAIL.lib.dir}/xmlresolver-4.2.0-data.jar;."
fork="${fork}" failonerror="true">
             <!-- arg value="-t" description="timing information"/ -->
             <arg value="-warnings:recover" description="recover after
writing a warning message"/>
             <arg value="-o:TempSaiJava.txt" description="output-doc"/>
@@ -1293,7 +1295,7 @@
     <target name="BuildX3dOntologyFromX3duom.saxon" depends=""
description="Build X3D Ontology from X3D Unified Object Model (X3DUOM)" >
         <echo message="Following output is for X3D ontology version 4.0 in
Terse Triple Language (Turtle)"/>
         <!-- TODO other versions of X3D -->
-        <java classname="net.sf.saxon.Transform"
classpath="${saxon.dir}/${saxon.jar};." fork="${fork}">
+        <java classname="net.sf.saxon.Transform"
classpath="${saxon.dir}/${saxon.jar};${X3DJSAIL.lib.dir}/xmlresolver-4.2.0.jar;${X3DJSAIL.lib.dir}/xmlresolver-4.2.0-data.jar;."
fork="${fork}">
             <!-- arg value="-t" description="timing information"/ -->
             <arg value="-warnings:recover" description="recover after
writing a warning message"/>
             <arg
value="-s:${specifications.dir}/${X3dUnifiedObjectModel4.0}"
description="source-doc"/>

Here's evidence that the patch works, YMMV!

$ ant BuildX3dOntologyFromX3duom.saxon
Buildfile: C:\x3d-code\www.web3d.org\x3d\stylesheets\build.xml

BuildX3dOntologyFromX3duom.saxon:
     [echo] Following output is for X3D ontology version 4.0 in Terse
Triple Language (Turtle)
     [java] *** rename: FontStyle field 'style' renamed as 'styleSelection'
to avoid name collision with CSS style attribute
     [java] *** info:   Inline has multiple AdditionalInterface
definitions: X3DBoundedObject X3DUrlObject
     [java] *** info:   MovieTexture has multiple AdditionalInterface
definitions: X3DTexture2DNode X3DUrlObject
     [java] *** info:   PackagedShader has multiple AdditionalInterface
definitions: X3DProgrammableShaderObject X3DUrlObject
     [java] *** rename: ScreenFontStyle field 'style' renamed as
'styleSelection' to avoid name collision with CSS style attribute
     [java] *** info:   ShaderProgram has multiple AdditionalInterface
definitions: X3DProgrammableShaderObject X3DUrlObject
     [copy] Copying 1 file to C:\x3d-code\www.web3d.org\semantics\ontologies
     [copy] Copying
C:\x3d-code\www.web3d.org\x3d\stylesheets\X3dOntology4.0.ttl
to C:\x3d-code\www.web3d.org\semantics\ontologies\X3dOntology4.0.ttl
     [copy] Copying 1 file to C:\x3d-code\www.web3d.org\x3d\specifications
     [copy] Copying
C:\x3d-code\www.web3d.org\x3d\stylesheets\X3dOntology4.0.ttl
to C:\x3d-code\www.web3d.org\x3d\specifications\X3dOntology4.0.ttl
     [echo] OWL validation available at
     [echo]   http://mowl-power.cs.man.ac.uk:8080/validator (Profile OWL 2,
Report syntax: Manchester Owl Syntax)
     [echo]   http://visualdataweb.de/validator
     [echo]   https://www.web3d.org/x3d/specifications/X3dOntology4.0.ttl
     [echo]
https://www.web3d.org/x3d/content/semantics/ontologies/X3dOntology4.0.ttl

BUILD SUCCESSFUL
Total time: 3 seconds

On Sun, Apr 10, 2022 at 7:53 PM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

> [forwarded with permission]
>
>
>
> *From:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> *Sent:* Sunday, April 10, 2022 11:07 AM
> *To:* Цветанка Георгиева <cv.georgieva at live.uni-vt.bg>
> *Cc:* Jakub Flotyński <flotynski at kti.ue.poznan.pl>; Brutzman, Donald
> (Don) (CIV) <brutzman at nps.edu>
> *Subject:* RE: X3D Ontology problem
>
>
>
> [copy co-chair Dr. Jakub Flotyński]
>
>
>
> Thanks for your note and efforts Tsvetanka.
>
>
>
> This problem is occurring because multiple projects are involved with
> mutual inter-dependencies.  It the case you are reporting, X3DUOM is not
> visible in this X3D Ontology project.
>
>
>
> I will work on making the X3D Ontology project more portable
> (self-contained) and independent.  Meanwhile, you can simply use the
> provided files online or in version control.
>
>
>
>    - X3D Unified Object Model (X3DUOM)
>    - https://www.web3d.org/specifications/X3DUOM.html
>    - https://www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml
>    -
>    https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml
>
>
>
>    - X3D Ontology
>    - https://www.web3d.org/x3d/content/semantics/semantics.html
>    -
>    https://www.web3d.org/x3d/content/semantics/ontologies/X3dOntology4.0.ttl
>    -
>    https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/semantics/ontologies/X3dOntology4.0.ttl
>
>
>
> Future communications are welcome if needed.  If possible, please use
>
>    - x3d-public at web3d.org
>    - x3d-public is a public discussion list on all topics related to the
>    authoring and use of Extensible 3D (X3D) Graphics.
>    - is a public discussion list on all topics related to the authoring
>    and use of Extensible 3D (X3D) Graphics.
>    - https://www.web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
>
> Hoping to respect your privacy… Request your permission to forward your
> message and this response to that publicly archived mailing list.  Is that
> OK?
>
>
>
> Good luck with your work.
>
>
>
> 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 https://
> faculty.nps.edu/brutzman
>
>
>
> *From:* Цветанка Георгиева <cv.georgieva at live.uni-vt.bg>
> *Sent:* Sunday, April 10, 2022 7:30 AM
> *To:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> *Subject:* X3D Ontology problem
>
>
>
> Dear Don Brutzman!
>
> Could you help me solve a problem that arose when I tried to use the x3d
> to ttl conversion you developed.
>
> I obtain the error shown in the attached screenshot.
>
> Thank you in advance!
>
> Best regards,
>
> Tsvetanka Georgieva-Trifonova
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220410/0d379a46/attachment-0001.html>
