<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">The spec already refers to ID in the
XML encoding. It is documented in 4.3.4
(<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#DEFAndUSEAttributeSyntax">http://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#DEFAndUSEAttributeSyntax</a>).<br>
<br>
" A USE attribute indicates that a node is a reference copy of a
DEF node with the same ID. DEF is assigned XML type ID, and USE is
assigned XML type IDREF, respectively. The same name-construction
conventions regarding legal character combinations apply.<br>
<br>
Each DEF (ID) value in a scene shall be unique. Non-unique node
DEF names in the body of ProtoDeclare definitions will cause
validation errors when checked by the X3D DTD or Schema. This is a
limitation of XML that requires each XML DTD and Schema to have a
single namespace for ID types. "<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
<br>
On 3/20/2016 10:09 AM, John Carlson wrote:<br>
</div>
<blockquote
cite="mid:CAGC3UEn2SXzYXkAWGWMJvZg_7fGVrStDgo6kyk+AR-Y4veAssg@mail.gmail.com"
type="cite">
<p dir="ltr">I'll second the proposal. Also I'd like to propose
adding CSS selectors for values of the fromNode and toNode
attributes on ROUTEs if not already in the standard. Thus if
you have a node with id="foo" you could use a route with
toNode="#foo". Class attributes would work similarly for fan in
fan out.</p>
<p dir="ltr">John</p>
<div class="gmail_quote">On Mar 20, 2016 11:23 AM, "Andreas
Plesch" <<a moz-do-not-send="true"
href="mailto:andreasplesch@gmail.com">andreasplesch@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Since Don mentioned that nobody has proposed
introducing an 'id' attribute, let me then propose adding an
'id' SFString attribute to all nodes for x3d 4.0.</p>
<p dir="ltr">The reason is simply compatibility with the DOM
on web pages in the case where x3d nodes are interpreted as
DOM elements.</p>
<p dir="ltr">Andreas</p>
<div class="gmail_quote">On Mar 20, 2016 10:01 AM, <<a
moz-do-not-send="true"
href="mailto:x3d-public-request@web3d.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public-request@web3d.org">x3d-public-request@web3d.org</a></a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Send
x3d-public mailing list submissions to<br>
<a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
or, via email, send a message with subject or body 'help'
to<br>
<a moz-do-not-send="true"
href="mailto:x3d-public-request@web3d.org"
target="_blank">x3d-public-request@web3d.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:x3d-public-owner@web3d.org" target="_blank">x3d-public-owner@web3d.org</a><br>
<br>
When replying, please edit your Subject line so it is more
specific<br>
than "Re: Contents of x3d-public digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. X3D V4.0 beta? (John Carlson)<br>
2. Re: X3D V4.0 beta? (Don Brutzman)<br>
3. X3dToJson.xslt stylesheet converter: documentation
update<br>
(Don Brutzman)<br>
4. Re: Volunteer needed, X3D JSON to X3D XML,
X3D Canonicalizer,<br>
comparison (<a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a>)<br>
5. Re: x3d json schema validation on x3d resources
examples<br>
results (Clement IGONET)<br>
6. Re: x3d json schema validation on x3d resources
examples<br>
results (Roy Walmsley)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 19 Mar 2016 22:32:21 -0400<br>
From: John Carlson <<a moz-do-not-send="true"
href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>
To: X3D Graphics public mailing list <<a
moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>><br>
Subject: [x3d-public] X3D V4.0 beta?<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:66C61C24-D110-427D-A64B-56B23FA4283C@gmail.com"
target="_blank">66C61C24-D110-427D-A64B-56B23FA4283C@gmail.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Is it possible to get an advanced X3D V4.0 beta XML schema
and X3D JSON schema, with class and id attributes
(assuming they are going to be added and are defined
similar to HTML?). Is this a difficult or major change?
Or should I run without a schema for a while?<br>
<br>
John<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 19 Mar 2016 20:46:22 -0700<br>
From: Don Brutzman <<a moz-do-not-send="true"
href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br>
To: John Carlson <<a moz-do-not-send="true"
href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>
Cc: X3D Graphics public mailing list <<a
moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>><br>
Subject: Re: [x3d-public] X3D V4.0 beta?<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:56EE1D0E.4040107@nps.edu" target="_blank">56EE1D0E.4040107@nps.edu</a>><br>
Content-Type: text/plain; charset="windows-1252";
format=flowed<br>
<br>
On 3/19/2016 7:32 PM, John Carlson wrote:<br>
> Is it possible to get an advanced X3D V4.0 beta XML
schema and X3D JSON schema, with class and id attributes
(assuming they are going to be added and are defined
similar to HTML?).<br>
<br>
Active draft XML Schema and XML DTD for X3D v4.0 are
online at the usual locations.<br>
<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/specifications"
rel="noreferrer" target="_blank">http://www.web3d.org/specifications</a><br>
<br>
Attributes for class are already present in all versions.<br>
<br>
Attributes DEF and USE have XML data types ID and IDREF
respectively.<br>
<br>
Nobody has proposed an attribute 'id' yet. It would be
good to begin listing reasons to do so, if there are any.<br>
<br>
JSON Schema v3.3 is current work created manually by Roy
Walmsley. When we are all comfortable with the design
patterns, autogenerating such a schema for all X3D
versions is certainly feasible. Of note is that
definitions of JSON Schemas themselves are not
authoritative yet, we are currently using the latest
(expired) RFC draft 4.<br>
<br>
> Is this a difficult or major change? Or should I run
without a schema for a while?<br>
<br>
Since the differences are currently minimal, I think you
could use the X3D v3.3 JSON Schema for v4.0 (or other
versions) if need be. However be sure to carefully label
any such v4 scenes as experimental in case some one
belatedly finds them someday with usual expectations of
reliability.<br>
<br>
all the best, Don<br>
--<br>
Don Brutzman Naval Postgraduate School, Code USW/Br
<a moz-do-not-send="true" href="mailto:brutzman@nps.edu"
target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
<a moz-do-not-send="true" href="tel:%2B1.831.656.2149"
value="+18316562149" target="_blank">+1.831.656.2149</a><br>
X3D graphics, virtual worlds, navy robotics <a
moz-do-not-send="true"
href="http://faculty.nps.edu/brutzman" rel="noreferrer"
target="_blank"><a class="moz-txt-link-freetext" href="http://faculty.nps.edu/brutzman">http://faculty.nps.edu/brutzman</a></a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sat, 19 Mar 2016 20:52:45 -0700<br>
From: Don Brutzman <<a moz-do-not-send="true"
href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br>
To: X3D Graphics public mailing list <<a
moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>><br>
Subject: [x3d-public] X3dToJson.xslt stylesheet converter:<br>
documentation update<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:56EE1E8D.9090003@nps.edu" target="_blank">56EE1E8D.9090003@nps.edu</a>><br>
Content-Type: text/plain; charset="utf-8"; format=flowed<br>
<br>
From this past week's X3D JSON teleconference:<br>
<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/stylesheets/X3dToJson.html#encoding"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/stylesheets/X3dToJson.html#encoding</a><br>
<br>
* Encoding. JSON files are implicitly allowed to have an
encoding of UTF-8, UTF-16 or UTF-32. The "X3D" object is
given a field such as "encoding":"UTF-8" to indicate the
scene author's expected encoding. This expression of file
encoding corresponds to the header statement syntax
required for the VRML97, ClassicVRML and XML file formats.<br>
<br>
The excerpted examples are also updated to show SFNode
syntax for all SFNode children, e.g. appearance, geometry,
texture etc.<br>
<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/stylesheets/X3dToJson.html#HelloWorld.json"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/stylesheets/X3dToJson.html#HelloWorld.json</a><br>
<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/stylesheets/X3dToJson.html#TestJsonEncoding.json"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/stylesheets/X3dToJson.html#TestJsonEncoding.json</a><br>
<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/stylesheets/X3dToJson.html#OrigamiCranes.json"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/stylesheets/X3dToJson.html#OrigamiCranes.json</a><br>
<br>
all the best, Don<br>
--<br>
Don Brutzman Naval Postgraduate School, Code USW/Br
<a moz-do-not-send="true" href="mailto:brutzman@nps.edu"
target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
<a moz-do-not-send="true" href="tel:%2B1.831.656.2149"
value="+18316562149" target="_blank">+1.831.656.2149</a><br>
X3D graphics, virtual worlds, navy robotics <a
moz-do-not-send="true"
href="http://faculty.nps.edu/brutzman" rel="noreferrer"
target="_blank"><a class="moz-txt-link-freetext" href="http://faculty.nps.edu/brutzman">http://faculty.nps.edu/brutzman</a></a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 20 Mar 2016 06:39:57 +0000<br>
From: "<a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a>"
<<a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a>><br>
To: John Carlson <<a moz-do-not-send="true"
href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>,
X3D Graphics public mailing<br>
list <<a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
Subject: Re: [x3d-public] Volunteer needed, X3D JSON to
X3D XML, X3D<br>
Canonicalizer, comparison<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:3B2B4E2B-574D-4C64-9CF7-5387E6629919@igonet.fr"
target="_blank">3B2B4E2B-574D-4C64-9CF7-5387E6629919@igonet.fr</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi John.<br>
Well, it just looks like Unit Test to put in place.<br>
I could be your guy.<br>
<br>
Clement.<br>
<br>
Le 19 mars 2016 23:48:02 UTC+01:00, John Carlson <<a
moz-do-not-send="true" href="mailto:yottzumm@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a></a>> a ?crit :<br>
>I am soliciting for a volunteer for X3D JSON to X3D
XML conversion<br>
>work. This would entail:<br>
><br>
>* Using the X3D JSON Loader associated code to convert
X3D Resources<br>
>examples JSON to XML (and DOM).<br>
>* Running the X3D Canonicalizer to convert to
canonicalized X3D XML<br>
>* Running a comparison between X3D Resources examples
X3D XML and XML<br>
>output from X3D Canonicalizer<br>
>* Reporting any discrepancies to X3D JSON Working
Group<br>
>* Integrating any improvements into the X3D JSON
Loader associated<br>
>code, contributing to X3D JSON Loader development work
in generating<br>
>X3D XML.<br>
><br>
>Other activities may include:<br>
><br>
>* Integrating the X3D JSON Schema into the X3D JSON
Loader<br>
><br>
>You must be a self-motivated self-starter. JavaScript
and Node.js<br>
>(scripting) knowledge would be useful. Limited
knowledge of X3D<br>
>desired. Knowledge of XML entities, escaping,
quoting, JSON desired,<br>
>but may be learned. Java knowledge might be useful in
the future.<br>
><br>
>I?d do it myself, but I recently came out of
retirement.<br>
><br>
>The purpose of this is to validate that the JSON
loader can essentially<br>
>produces equivalent XML to X3dToJson.xslt input
(roundtripping). A<br>
>blissful side effect we hope is that the JSON loader
will be able to<br>
>handle the various quoting and escaping that is coming
towards us.<br>
><br>
>Thanks,<br>
><br>
>John<br>
>_______________________________________________<br>
>x3d-public mailing list<br>
><a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
><a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
<a moz-do-not-send="true" href="mailto:clement@igonet.fr"
target="_blank">clement@igonet.fr</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a moz-do-not-send="true"
href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160320/ee81072d/attachment-0001.html"
rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160320/ee81072d/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sun, 20 Mar 2016 14:34:43 +0100<br>
From: Clement IGONET <<a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a>><br>
To: John Carlson <<a moz-do-not-send="true"
href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>,
Roy Walmsley<br>
<<a moz-do-not-send="true"
href="mailto:roy.walmsley@ntlworld.com" target="_blank">roy.walmsley@ntlworld.com</a>><br>
Cc: X3D Graphics public mailing list <<a
moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a></a>><br>
Subject: Re: [x3d-public] x3d json schema validation on
x3d resources<br>
examples results<br>
Message-ID:<br>
<<a moz-do-not-send="true"
href="mailto:CAPjSTuXyR7TumjTfre0Zw0ZN-FxgAieebBw4qvMFNpiprpKqCw@mail.gmail.com"
target="_blank">CAPjSTuXyR7TumjTfre0Zw0ZN-FxgAieebBw4qvMFNpiprpKqCw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Bad use cases:<br>
Case 1:<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarth.xhtml"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarth.xhtml</a><br>
The x3d data have a reference to:<br>
<a moz-do-not-send="true"
href="http://x3d-earth.nps.edu/7_levels_plus/tiles/0/globe.x3d"
rel="noreferrer" target="_blank">http://x3d-earth.nps.edu/7_levels_plus/tiles/0/globe.x3d</a><br>
This link is no more accessible.<br>
<br>
Case 2:<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarthOpenAerialMap.xhtml"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarthOpenAerialMap.xhtml</a><br>
Broken link: <a moz-do-not-send="true"
href="http://x3d-earth.nps.edu/oamdemo.x3d"
rel="noreferrer" target="_blank">http://x3d-earth.nps.edu/oamdemo.x3d</a><br>
<br>
Case 3:<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/_pages/page16.html"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/_pages/page16.html</a><br>
Broken link: <a moz-do-not-send="true"
href="http://x3d-earth.nps.edu/osmdemo.x3d"
rel="noreferrer" target="_blank">http://x3d-earth.nps.edu/osmdemo.x3d</a><br>
<br>
=> These examples does not work anymore for a long
time.<br>
<br>
Who could fix it?<br>
<br>
Cl?ment.<br>
<br>
On Sat, Mar 19, 2016 at 11:38 PM, <a
moz-do-not-send="true" href="mailto:clement@igonet.fr"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:clement@igonet.fr">clement@igonet.fr</a></a> <<a
moz-do-not-send="true" href="mailto:clement@igonet.fr"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:clement@igonet.fr">clement@igonet.fr</a></a>> wrote:<br>
> For geo examples, a lot of examples miss inline x3d
url (url to x3d files no<br>
> more available online).<br>
> These examples can't work anywhere in anyway...<br>
><br>
><br>
> Le 19 mars 2016 23:17:00 UTC+01:00, John Carlson <<a
moz-do-not-send="true" href="mailto:yottzumm@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a></a>> a<br>
> ?crit :<br>
>><br>
>> We?ve got 245 files failing JSON schema with the
everit validator, and<br>
>> 3322 validating. That?s around 93% validating.<br>
>><br>
>> 90 of these schema validation error involve
geoSystem. 4 are missing<br>
>> encoding. Here they are:<br>
>><br>
>>
examples//Basic/development/WrapperTagsExampleJsonCommentsAlternative.json<br>
>>
examples//X3dForAdvancedModeling/Buildings/Building.json<br>
>><br>
>><br>
>>
examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommentedAlternativeEncoding.json<br>
>><br>
>><br>
>>
examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommentedOriginalEncoding.json<br>
>><br>
>><br>
>> John<br>
>><br>
>> ________________________________<br>
>><br>
>> x3d-public mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
>> <a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
><br>
><br>
> <a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sun, 20 Mar 2016 14:00:19 -0000<br>
From: "Roy Walmsley" <<a moz-do-not-send="true"
href="mailto:roy.walmsley@ntlworld.com" target="_blank">roy.walmsley@ntlworld.com</a>><br>
To: "'Clement IGONET'" <<a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a>><br>
Cc: "'John Carlson'" <<a moz-do-not-send="true"
href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>,
"Don Brutzman"<br>
<<a moz-do-not-send="true"
href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>>,
"'X3D Graphics public mailing list'"<br>
<<a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
Subject: Re: [x3d-public] x3d json schema validation on
x3d resources<br>
examples results<br>
Message-ID: <005201d182b0$d6f5e830$84e1b890$@<a
moz-do-not-send="true" href="http://ntlworld.com"
rel="noreferrer" target="_blank">ntlworld.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Clement,<br>
<br>
Thank you for your reporting these instances.<br>
<br>
Don and I can review these cases and agree fixes, which
Don can implement.<br>
<br>
Regards,<br>
<br>
Roy<br>
<br>
-----Original Message-----<br>
From: Clement IGONET [mailto:<a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a>]<br>
Sent: 20 March 2016 13:35<br>
To: John Carlson; Roy Walmsley<br>
Cc: X3D Graphics public mailing list<br>
Subject: Re: [x3d-public] x3d json schema validation on
x3d resources examples results<br>
<br>
Bad use cases:<br>
Case 1:<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarth.xhtml"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarth.xhtml</a><br>
The x3d data have a reference to:<br>
<a moz-do-not-send="true"
href="http://x3d-earth.nps.edu/7_levels_plus/tiles/0/globe.x3d"
rel="noreferrer" target="_blank">http://x3d-earth.nps.edu/7_levels_plus/tiles/0/globe.x3d</a><br>
This link is no more accessible.<br>
<br>
Case 2:<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarthOpenAerialMap.xhtml"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarthOpenAerialMap.xhtml</a><br>
Broken link: <a moz-do-not-send="true"
href="http://x3d-earth.nps.edu/oamdemo.x3d"
rel="noreferrer" target="_blank">http://x3d-earth.nps.edu/oamdemo.x3d</a><br>
<br>
Case 3:<br>
<a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/_pages/page16.html"
rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/_pages/page16.html</a><br>
Broken link: <a moz-do-not-send="true"
href="http://x3d-earth.nps.edu/osmdemo.x3d"
rel="noreferrer" target="_blank">http://x3d-earth.nps.edu/osmdemo.x3d</a><br>
<br>
=> These examples does not work anymore for a long
time.<br>
<br>
Who could fix it?<br>
<br>
Cl?ment.<br>
<br>
On Sat, Mar 19, 2016 at 11:38 PM, <a
moz-do-not-send="true" href="mailto:clement@igonet.fr"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:clement@igonet.fr">clement@igonet.fr</a></a> <<a
moz-do-not-send="true" href="mailto:clement@igonet.fr"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:clement@igonet.fr">clement@igonet.fr</a></a>> wrote:<br>
> For geo examples, a lot of examples miss inline x3d
url (url to x3d<br>
> files no more available online).<br>
> These examples can't work anywhere in anyway...<br>
><br>
><br>
> Le 19 mars 2016 23:17:00 UTC+01:00, John Carlson <<a
moz-do-not-send="true" href="mailto:yottzumm@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a></a>><br>
> a ?crit :<br>
>><br>
>> We?ve got 245 files failing JSON schema with the
everit validator,<br>
>> and<br>
>> 3322 validating. That?s around 93% validating.<br>
>><br>
>> 90 of these schema validation error involve
geoSystem. 4 are missing<br>
>> encoding. Here they are:<br>
>><br>
>>
examples//Basic/development/WrapperTagsExampleJsonCommentsAlternative<br>
>> .json
examples//X3dForAdvancedModeling/Buildings/Building.json<br>
>><br>
>><br>
>>
examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommented<br>
>> AlternativeEncoding.json<br>
>><br>
>><br>
>>
examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommented<br>
>> OriginalEncoding.json<br>
>><br>
>><br>
>> John<br>
>><br>
>> ________________________________<br>
>><br>
>> x3d-public mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
>> <a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
><br>
><br>
> <a moz-do-not-send="true"
href="mailto:clement@igonet.fr" target="_blank">clement@igonet.fr</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of x3d-public Digest, Vol 84, Issue 26<br>
******************************************<br>
</blockquote>
</div>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a moz-do-not-send="true" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
<a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
X3D Co-Chair<br>
Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>