[X3D-Public] X3D element and attribute table for XML case, lower case [HTML5 Bug 8238]

[Don Brutzman]

thanks for the review Joe

Joe D Williams wrote:
> Hi Don,
> I think this list is too long and potentially confusing because it
> contains nodes used purely to collect node types in the schema like:
> ColorCoordinateNormalTextureCoordinateContentModel
> 
> To me, this and otheres are not really a 'true' abstract node type,
> but just a 'convenience' vehicle for grouping objects and attributes.

These were listed on the initiallist provided to bug 8238
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8238

> I think the list would be more informative and easier to comprehend
> without these 'convenience' elements.
> 
> A really good ones to look at are:
> Table L.2 - Version content.
> http://www.web3d.org/x3d/specifications/ISO-IEC-19775-1.2-X3D-AbstractSpecification/Part01/versionContent.html
> 
> and
> Node index
> http://www.web3d.org/x3d/specifications/ISO-IEC-19775-1.2-X3D-AbstractSpecification/Part01/nodeIndex.html
> 
> and
> Figure 4.2 - Interface hierarchy
> http://www.web3d.org/x3d/specifications/ISO-IEC-19775-1.2-X3D-AbstractSpecification/Part01/concepts.html#f-Objecthierarchy
> 
> 
> So, I think we really should only list abstract and concrete nodes

I agree with concrete nodes...  We should not include interfaces or abstract
nodes since they will not appear in any authored content, particularly as
part of a compound HTML5/X3D document.  So the lists I've posted should match
the node + attribute index provided in Table L.2 for X3D v3.2.

Updated online at
http://x3d.svn.sourceforge.net/viewvc/x3d/www.web3d.org/x3d/stylesheets/X3dElementsAttributesLowerCaseTable.txt

That makes sense to you too I hope Joe.  Again thanks for your scrutiny.

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  work +1.831.656.2149
X3D, virtual worlds, underwater robots, XMSF  http://web.nps.navy.mil/~brutzman