[x3d-public] id attribute proposal

Leonard Daly web3d at realism.com
Sun Mar 20 17:16:34 PDT 2016


The spec already refers to ID in the XML encoding. It is documented in 
4.3.4 
(http://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#DEFAndUSEAttributeSyntax).

" 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.

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. "


Leonard Daly





On 3/20/2016 10:09 AM, John Carlson wrote:
>
> 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.
>
> John
>
> On Mar 20, 2016 11:23 AM, "Andreas Plesch" <andreasplesch at gmail.com 
> <mailto:andreasplesch at gmail.com>> wrote:
>
>     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.
>
>     The reason is simply compatibility with the DOM on web pages in
>     the case where x3d nodes are interpreted as DOM elements.
>
>     Andreas
>
>     On Mar 20, 2016 10:01 AM, <x3d-public-request at web3d.org
>     <mailto:x3d-public-request at web3d.org>> wrote:
>
>         Send x3d-public mailing list submissions to
>         x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>
>         To subscribe or unsubscribe via the World Wide Web, visit
>         http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>         or, via email, send a message with subject or body 'help' to
>         x3d-public-request at web3d.org <mailto:x3d-public-request at web3d.org>
>
>         You can reach the person managing the list at
>         x3d-public-owner at web3d.org <mailto:x3d-public-owner at web3d.org>
>
>         When replying, please edit your Subject line so it is more
>         specific
>         than "Re: Contents of x3d-public digest..."
>
>
>         Today's Topics:
>
>            1. X3D V4.0 beta? (John Carlson)
>            2. Re: X3D V4.0 beta? (Don Brutzman)
>            3. X3dToJson.xslt stylesheet converter: documentation      
>         update
>               (Don Brutzman)
>            4. Re: Volunteer needed, X3D JSON to X3D XML, X3D
>         Canonicalizer,
>               comparison (clement at igonet.fr <mailto:clement at igonet.fr>)
>            5. Re: x3d json schema validation on x3d resources  examples
>               results (Clement IGONET)
>            6. Re: x3d json schema validation on x3d resources  examples
>               results (Roy Walmsley)
>
>
>         ----------------------------------------------------------------------
>
>         Message: 1
>         Date: Sat, 19 Mar 2016 22:32:21 -0400
>         From: John Carlson <yottzumm at gmail.com
>         <mailto:yottzumm at gmail.com>>
>         To: X3D Graphics public mailing list <x3d-public at web3d.org
>         <mailto:x3d-public at web3d.org>>
>         Subject: [x3d-public] X3D V4.0 beta?
>         Message-ID: <66C61C24-D110-427D-A64B-56B23FA4283C at gmail.com
>         <mailto:66C61C24-D110-427D-A64B-56B23FA4283C at gmail.com>>
>         Content-Type: text/plain; charset=us-ascii
>
>         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?
>
>         John
>
>
>         ------------------------------
>
>         Message: 2
>         Date: Sat, 19 Mar 2016 20:46:22 -0700
>         From: Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>>
>         To: John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>>
>         Cc: X3D Graphics public mailing list <x3d-public at web3d.org
>         <mailto:x3d-public at web3d.org>>
>         Subject: Re: [x3d-public] X3D V4.0 beta?
>         Message-ID: <56EE1D0E.4040107 at nps.edu
>         <mailto:56EE1D0E.4040107 at nps.edu>>
>         Content-Type: text/plain; charset="windows-1252"; format=flowed
>
>         On 3/19/2016 7:32 PM, John Carlson wrote:
>         > 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?).
>
>         Active draft XML Schema and XML DTD for X3D v4.0 are online at
>         the usual locations.
>
>         http://www.web3d.org/specifications
>
>         Attributes for class are already present in all versions.
>
>         Attributes DEF and USE have XML data types ID and IDREF
>         respectively.
>
>         Nobody has proposed an attribute 'id' yet.  It would be good
>         to begin listing reasons to do so, if there are any.
>
>         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.
>
>         > Is this a difficult or major change? Or should I run without
>         a schema for a while?
>
>         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.
>
>         all the best, Don
>         --
>         Don Brutzman  Naval Postgraduate School, Code USW/Br
>         brutzman at nps.edu <mailto:brutzman at nps.edu>
>         Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA
>         +1.831.656.2149 <tel:%2B1.831.656.2149>
>         X3D graphics, virtual worlds, navy robotics
>         http://faculty.nps.edu/brutzman
>
>
>
>         ------------------------------
>
>         Message: 3
>         Date: Sat, 19 Mar 2016 20:52:45 -0700
>         From: Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>>
>         To: X3D Graphics public mailing list <x3d-public at web3d.org
>         <mailto:x3d-public at web3d.org>>
>         Subject: [x3d-public] X3dToJson.xslt stylesheet converter:
>                 documentation   update
>         Message-ID: <56EE1E8D.9090003 at nps.edu
>         <mailto:56EE1E8D.9090003 at nps.edu>>
>         Content-Type: text/plain; charset="utf-8"; format=flowed
>
>          From this past week's X3D JSON teleconference:
>
>         http://www.web3d.org/x3d/stylesheets/X3dToJson.html#encoding
>
>         * 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.
>
>         The excerpted examples are also updated to show SFNode syntax
>         for all SFNode children, e.g. appearance, geometry, texture etc.
>
>         http://www.web3d.org/x3d/stylesheets/X3dToJson.html#HelloWorld.json
>
>         http://www.web3d.org/x3d/stylesheets/X3dToJson.html#TestJsonEncoding.json
>
>         http://www.web3d.org/x3d/stylesheets/X3dToJson.html#OrigamiCranes.json
>
>         all the best, Don
>         --
>         Don Brutzman  Naval Postgraduate School, Code USW/Br
>         brutzman at nps.edu <mailto:brutzman at nps.edu>
>         Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA
>         +1.831.656.2149 <tel:%2B1.831.656.2149>
>         X3D graphics, virtual worlds, navy robotics
>         http://faculty.nps.edu/brutzman
>
>
>
>         ------------------------------
>
>         Message: 4
>         Date: Sun, 20 Mar 2016 06:39:57 +0000
>         From: "clement at igonet.fr <mailto:clement at igonet.fr>"
>         <clement at igonet.fr <mailto:clement at igonet.fr>>
>         To: John Carlson <yottzumm at gmail.com
>         <mailto:yottzumm at gmail.com>>, X3D Graphics public mailing
>                 list <x3d-public at web3d.org <mailto:x3d-public at web3d.org>>
>         Subject: Re: [x3d-public] Volunteer needed, X3D JSON to X3D
>         XML,        X3D
>                 Canonicalizer, comparison
>         Message-ID: <3B2B4E2B-574D-4C64-9CF7-5387E6629919 at igonet.fr
>         <mailto:3B2B4E2B-574D-4C64-9CF7-5387E6629919 at igonet.fr>>
>         Content-Type: text/plain; charset="utf-8"
>
>         Hi John.
>         Well, it just looks like Unit Test to put in place.
>         I could be your guy.
>
>         Clement.
>
>         Le 19 mars 2016 23:48:02 UTC+01:00, John Carlson
>         <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> a ?crit :
>         >I am soliciting for a volunteer for X3D JSON to X3D XML
>         conversion
>         >work.  This would entail:
>         >
>         >* Using the X3D JSON Loader associated code to convert X3D
>         Resources
>         >examples JSON to XML (and DOM).
>         >* Running the X3D Canonicalizer to convert to canonicalized
>         X3D XML
>         >* Running a comparison between X3D Resources examples X3D XML
>         and XML
>         >output from X3D Canonicalizer
>         >* Reporting any discrepancies to X3D JSON Working Group
>         >* Integrating any improvements into the X3D JSON Loader
>         associated
>         >code, contributing to X3D JSON Loader development work in
>         generating
>         >X3D XML.
>         >
>         >Other activities may include:
>         >
>         >* Integrating the X3D JSON Schema into the X3D JSON Loader
>         >
>         >You must be a self-motivated self-starter.  JavaScript and
>         Node.js
>         >(scripting) knowledge would be useful.  Limited knowledge of X3D
>         >desired.  Knowledge of XML entities, escaping, quoting, JSON
>         desired,
>         >but may be learned.  Java knowledge might be useful in the
>         future.
>         >
>         >I?d do it myself, but I recently came out of retirement.
>         >
>         >The purpose of this is to validate that the JSON loader can
>         essentially
>         >produces equivalent XML to X3dToJson.xslt input
>         (roundtripping).  A
>         >blissful side effect we hope is that the JSON loader will be
>         able to
>         >handle the various quoting and escaping that is coming
>         towards us.
>         >
>         >Thanks,
>         >
>         >John
>         >_______________________________________________
>         >x3d-public mailing list
>         >x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>         >http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>         clement at igonet.fr <mailto:clement at igonet.fr>
>         -------------- next part --------------
>         An HTML attachment was scrubbed...
>         URL:
>         <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160320/ee81072d/attachment-0001.html>
>
>         ------------------------------
>
>         Message: 5
>         Date: Sun, 20 Mar 2016 14:34:43 +0100
>         From: Clement IGONET <clement at igonet.fr
>         <mailto:clement at igonet.fr>>
>         To: John Carlson <yottzumm at gmail.com
>         <mailto:yottzumm at gmail.com>>, Roy Walmsley
>                 <roy.walmsley at ntlworld.com
>         <mailto:roy.walmsley at ntlworld.com>>
>         Cc: X3D Graphics public mailing list <x3d-public at web3d.org
>         <mailto:x3d-public at web3d.org>>
>         Subject: Re: [x3d-public] x3d json schema validation on x3d
>         resources
>                 examples results
>         Message-ID:
>                
>         <CAPjSTuXyR7TumjTfre0Zw0ZN-FxgAieebBw4qvMFNpiprpKqCw at mail.gmail.com
>         <mailto:CAPjSTuXyR7TumjTfre0Zw0ZN-FxgAieebBw4qvMFNpiprpKqCw at mail.gmail.com>>
>         Content-Type: text/plain; charset=UTF-8
>
>         Bad use cases:
>         Case 1:
>         http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarth.xhtml
>         The x3d data have a reference to:
>         http://x3d-earth.nps.edu/7_levels_plus/tiles/0/globe.x3d
>         This link is no more accessible.
>
>         Case 2:
>         http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarthOpenAerialMap.xhtml
>         Broken link: http://x3d-earth.nps.edu/oamdemo.x3d
>
>         Case 3:
>         http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/_pages/page16.html
>         Broken link: http://x3d-earth.nps.edu/osmdemo.x3d
>
>         => These examples does not work anymore for a long time.
>
>         Who could fix it?
>
>         Cl?ment.
>
>         On Sat, Mar 19, 2016 at 11:38 PM, clement at igonet.fr
>         <mailto:clement at igonet.fr> <clement at igonet.fr
>         <mailto:clement at igonet.fr>> wrote:
>         > For geo examples, a lot of examples miss inline x3d url (url
>         to x3d files no
>         > more available online).
>         > These examples can't work anywhere in anyway...
>         >
>         >
>         > Le 19 mars 2016 23:17:00 UTC+01:00, John Carlson
>         <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> a
>         > ?crit :
>         >>
>         >> We?ve got 245 files failing JSON schema with the everit
>         validator, and
>         >> 3322 validating.  That?s around 93% validating.
>         >>
>         >> 90 of these schema validation error involve geoSystem. 4
>         are missing
>         >> encoding. Here they are:
>         >>
>         >>
>         examples//Basic/development/WrapperTagsExampleJsonCommentsAlternative.json
>         >> examples//X3dForAdvancedModeling/Buildings/Building.json
>         >>
>         >>
>         >>
>         examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommentedAlternativeEncoding.json
>         >>
>         >>
>         >>
>         examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommentedOriginalEncoding.json
>         >>
>         >>
>         >> John
>         >>
>         >> ________________________________
>         >>
>         >> x3d-public mailing list
>         >> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>         >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>         >
>         >
>         > clement at igonet.fr <mailto:clement at igonet.fr>
>
>
>
>         ------------------------------
>
>         Message: 6
>         Date: Sun, 20 Mar 2016 14:00:19 -0000
>         From: "Roy Walmsley" <roy.walmsley at ntlworld.com
>         <mailto:roy.walmsley at ntlworld.com>>
>         To: "'Clement IGONET'" <clement at igonet.fr
>         <mailto:clement at igonet.fr>>
>         Cc: "'John Carlson'" <yottzumm at gmail.com
>         <mailto:yottzumm at gmail.com>>, "Don Brutzman"
>                 <brutzman at nps.edu <mailto:brutzman at nps.edu>>,    "'X3D
>         Graphics public mailing list'"
>                 <x3d-public at web3d.org <mailto:x3d-public at web3d.org>>
>         Subject: Re: [x3d-public] x3d json schema validation on x3d
>         resources
>                 examples results
>         Message-ID: <005201d182b0$d6f5e830$84e1b890$@ntlworld.com
>         <http://ntlworld.com>>
>         Content-Type: text/plain;       charset="UTF-8"
>
>         Clement,
>
>         Thank you for your reporting these instances.
>
>         Don and I can review these cases and agree fixes, which Don
>         can implement.
>
>         Regards,
>
>         Roy
>
>         -----Original Message-----
>         From: Clement IGONET [mailto:clement at igonet.fr
>         <mailto:clement at igonet.fr>]
>         Sent: 20 March 2016 13:35
>         To: John Carlson; Roy Walmsley
>         Cc: X3D Graphics public mailing list
>         Subject: Re: [x3d-public] x3d json schema validation on x3d
>         resources examples results
>
>         Bad use cases:
>         Case 1:
>         http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarth.xhtml
>         The x3d data have a reference to:
>         http://x3d-earth.nps.edu/7_levels_plus/tiles/0/globe.x3d
>         This link is no more accessible.
>
>         Case 2:
>         http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/HelloEarthOpenAerialMap.xhtml
>         Broken link: http://x3d-earth.nps.edu/oamdemo.x3d
>
>         Case 3:
>         http://www.web3d.org/x3d/content/examples/Basic/GeoSpatial/_pages/page16.html
>         Broken link: http://x3d-earth.nps.edu/osmdemo.x3d
>
>         => These examples does not work anymore for a long time.
>
>         Who could fix it?
>
>         Cl?ment.
>
>         On Sat, Mar 19, 2016 at 11:38 PM, clement at igonet.fr
>         <mailto:clement at igonet.fr> <clement at igonet.fr
>         <mailto:clement at igonet.fr>> wrote:
>         > For geo examples, a lot of examples miss inline x3d url (url
>         to x3d
>         > files no more available online).
>         > These examples can't work anywhere in anyway...
>         >
>         >
>         > Le 19 mars 2016 23:17:00 UTC+01:00, John Carlson
>         <yottzumm at gmail.com <mailto:yottzumm at gmail.com>>
>         > a ?crit :
>         >>
>         >> We?ve got 245 files failing JSON schema with the everit
>         validator,
>         >> and
>         >> 3322 validating.  That?s around 93% validating.
>         >>
>         >> 90 of these schema validation error involve geoSystem. 4
>         are missing
>         >> encoding. Here they are:
>         >>
>         >>
>         examples//Basic/development/WrapperTagsExampleJsonCommentsAlternative
>         >> .json examples//X3dForAdvancedModeling/Buildings/Building.json
>         >>
>         >>
>         >>
>         examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommented
>         >> AlternativeEncoding.json
>         >>
>         >>
>         >>
>         examples//X3dForAdvancedModeling/HelloWorldScenes/HelloWorldCommented
>         >> OriginalEncoding.json
>         >>
>         >>
>         >> John
>         >>
>         >> ________________________________
>         >>
>         >> x3d-public mailing list
>         >> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>         >> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>         >
>         >
>         > clement at igonet.fr <mailto:clement at igonet.fr>
>
>
>
>
>         ------------------------------
>
>         Subject: Digest Footer
>
>         _______________________________________________
>         x3d-public mailing list
>         x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>         http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
>         ------------------------------
>
>         End of x3d-public Digest, Vol 84, Issue 26
>         ******************************************
>
>
>     _______________________________________________
>     x3d-public mailing list
>     x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>     http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org


-- 
*Leonard Daly*
X3D Co-Chair
Cloud Consultant
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160320/7320a3ec/attachment-0001.html>


More information about the x3d-public mailing list