[x3d-public] id attribute proposal

[Don Brutzman]

Obvious questions:

a. can DEF/USE simply be utilized instead?  First law of engineering: "if it isn't broken, don't fix it."

b. if DEF/USE cannot or ought not to be utilized, then how is is backwards compatibility handled?  This includes Inline content loaded into a parent scene.

c. what does X3DOM currently do?

d. what does Cobweb currently do?


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
> [...]

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