[x3d-public] X3D schema, DTD updates: new ClassicVRML encoding, inputOnly/outputOnly fields now complete

Wed Jun 10 10:33:03 PDT 2015

Let the X3DOM folks take care of that. The example of the spine direction bug can be seen here:

http://www.jishop.com/temp/x3d/

Click on Extrusions and check out the two topmost ones. They look flat, not triangular.

The bug record at X3DOM is here: https://github.com/x3dom/x3dom/issues/499

-----Original Message-----
From: doug sanden [mailto:highaspirations at hotmail.com] 
Sent: Wednesday, June 10, 2015 1:05 PM
To: X3D Graphics public mailing list
Subject: Re: [x3d-public] X3D schema, DTD updates: new ClassicVRML encoding, inputOnly/outputOnly fields now complete

x3dom twisted bar does look a bit weird (in the middle, beside freewrl and vivaty) http://dug9.users.sourceforge.net/web3d/temp/TwistedBarComparision.jpg
Generally the right shape, but is it normals that are off?

----------------------------------------
> From: VAlekseyev at niaid.nih.gov
> To: x3d-public at web3d.org
> Date: Wed, 10 Jun 2015 16:30:09 +0000
> Subject: Re: [x3d-public] X3D schema, DTD updates: new ClassicVRML 
> encoding, inputOnly/outputOnly fields now complete
>
> See this: 
> http://www.web3d.org/x3d/content/examples/Vrml2.0Sourcebook/Chapter15-
> Extrusion/Figure15.15TwistedBar.xhtml
>
> Screwy enough?
>
> But my point is different. If you direct the screw in the Z direction (instead of the default Y), X3DOM will not display it properly.
>
>
>
> -----Original Message-----
> From: doug sanden [mailto:highaspirations at hotmail.com]
> Sent: Wednesday, June 10, 2015 12:09 PM
> To: X3D Graphics public mailing list
> Subject: Re: [x3d-public] X3D schema, DTD updates: new ClassicVRML 
> encoding, inputOnly/outputOnly fields now complete
>
>> 3. The wording for generating the first (and only) SCP for collinear  
>> spines is unclear; specifically, "rotation along the axis" is a funny  
>> notion. I can imagine a translation along the axis and a rotation  
>> around an axis, but not a "rotation along something". Here's how I  
>> understand it: you calculate a rotation that takes the vector (0,1,0)  
>> to the spine direction vector (the first nonnull spine segment), then  
>> you apply the same rotation to the vector (0,0,1), and that's the Z  
>> for the SCP. Notably, that's *not* how the popular X3DOM  
>> implementation treats those cases.
>>
> Is this how you make a screw?
>
> ----------------------------------------
>> From: highaspirations at hotmail.com
>> To: x3d-public at web3d.org
>> Date: Wed, 10 Jun 2015 10:02:55 -0600
>> Subject: Re: [x3d-public] X3D schema, DTD updates: new ClassicVRML 
>> encoding, inputOnly/outputOnly fields now complete
>>
>> Alekseyev,
>> My recommendation: make an importer parameter setting for extrusion interpretation:
>> [*] filter out duplicate spine points [ ] x3dom interpretaiton of 
>> duplicate spine points This allows you to continue your excellent and 
>> much needed effort without waiting for someone to say something 
>> definitive about an edge case -Doug
>>
>>
>>
>> ----------------------------------------
>>> From: VAlekseyev at niaid.nih.gov
>>> To: brutzman at nps.edu; x3d at web3d.org; x3d-public at web3d.org
>>> Date: Wed, 10 Jun 2015 15:20:08 +0000
>>> Subject: Re: [x3d-public] X3D schema, DTD updates: new ClassicVRML 
>>> encoding, inputOnly/outputOnly fields now complete
>>>
>>> In the spirit of the spec review, did anyone maybe get a chance to review the Extrusion spec in light of the problems that I've outlined at http://web3d.org/pipermail/x3d-public_web3d.org/2015-June/003412.html ?
>>>
>>> There's one more problem with coincident spine points that I forgot to mention: the algorithm for CSP Y calculation in case of coincident spine points is inconsistent with the "special cases" rule that CSP for coincident points should match. It's entirely unclear rule takes precedence.
>>>
>>>
>>> -----Original Message-----
>>> From: Don Brutzman [mailto:brutzman at nps.edu]
>>> Sent: Tuesday, June 09, 2015 12:05 AM
>>> To: x3d at web3d.org; X3D Graphics public mailing list
>>> Subject: [x3d-public] X3D schema, DTD updates: new ClassicVRML 
>>> encoding, inputOnly/outputOnly fields now complete
>>>
>>> Lots of scrutiny and activity have resulted in numerous constructive changes to the X3D Schema and X3D DTD.
>>>
>>> New autogenerated product, includes both node signatures and example use:
>>>
>>> X3D Part 2: ClassicVRML encoding specification:
>>> Clause 6 Encoding of nodes.
>>> http://www.web3d.org/specifications/stylesheets/VrmlEncodingOfNodes.
>>> h
>>> tml
>>>
>>> Additional progress: the inputOnly, outputOnly fields are now completely defined, allowing complete definition of X3D Scene Access Interface (SAI) for Java.
>>>
>>> Java Binding Annex B Abstract node interfaces 
>>> http://www.web3d.org/specifications/JavaLanguageBinding/Part2/abstra
>>> c
>>> ts.html
>>>
>>> Java Binding Annex C Concrete node interfaces 
>>> http://www.web3d.org/specifications/JavaLanguageBinding/Part2/concre
>>> t
>>> es.html
>>>
>>> X3D Schema update activity:
>>> ====================================================================
>>> =
>>> ========
>>> 8 June 2015, walmsley brutzman
>>> - (v3.1+) Added axisRotation to CylinderSensor and PlaneSensor.
>>> - geoSystemType is MFString, not SFString
>>> - Added numerous accessType inputOnly/outputOnly annotation appinfo 
>>> entries to facilitate API autogeneration
>>> - Removed redundant node annotation appinfo entries when already 
>>> included by inherited node type
>>> - Note that CADAssembly children ViewpointGroup and OrthoViewpoint 
>>> require Navigation component level 3, which is higher than Viewpoint 
>>> provided in CADInterchange profile
>>> - removed SquadOrientationInterpolator closed field, erroneous; 
>>> added normalizeVelocity field
>>> - removed texCoord field from NurbsPatchSurface, duplicative with 
>>> X3DNurbsSurfaceGeometryNode
>>> - removed texCoord and controlPointfields from NurbsTrimmedSurface, 
>>> duplicative with X3DNurbsSurfaceGeometryNode
>>> - NurbsCurve2D is not a renderable geometry node, removed from geometry content model.
>>> - ComposedCubeMapTexture contained-element field name corrected from "topUrl" to "top"
>>> - Added missing fields: SurfaceEmitter coordIndex, VolumeEmitter 
>>> internal
>>> - BoundaryEnhancementVolumeStyle content model fixed/simplified
>>> - fixed capitalization, spelling etc. of detected errors in 
>>> field-name enumerations for each accessType; added corresponding 
>>> annotation/appinfo inputOnly/outputOnly events
>>> - detected, fixed irregular use of commas and [brackets] in elements 
>>> with multiple X3D element defaults
>>> - fixed Layer content model, allowing zero or more children
>>> - ensured all annotation/appinfo SFNode/MFNode inputOnly, outputOnly 
>>> events have default type included
>>> - refactored Programmable Shaders component nodes, minimized use of 
>>> mixed content (contained CDATA text)
>>> - (v3.2+) CollisionCollection base type X3DNode, default containerField="collider"
>>> - moved fraction_changed from X3DTimeDependentNode to TimeSensor
>>> - TODO noted problem: actual containerField for AudioClip is "source" not "children"
>>> - (v3.2+) Contact base type X3DNode, matching spec
>>> - (v3.1+) LocalFog is not bindable, implements X3DChildNode with 
>>> additionalInterface X3DFogObject
>>> - (v3.2+) LayoutGroup additionalInterface X3DGroupingNode, TODO 
>>> review content-model collisions if direct inheritance used
>>> - (v3.1+) Text node added outputOnly event "origin", lineBounds is 
>>> type MFVec2f
>>> - Resolved appinfo fields for X3DSoundSourceNode and 
>>> X3DTimeDependentNode
>>> - Removed duplicate appinfo set_bind field from GeoViewpoint 
>>> inherited from X3DBindableNode
>>> - (V3.2+) Added missing children, addChildren, and RemoveChildren 
>>> fields to LayoutGroup
>>> - (V3.2+) Added missing containerField to Contact
>>> - Add missing MedicalInterchange profile
>>> - Added QA test, ensured that MFString default values are quoted 
>>> ====================================================================
>>> =
>>> ========
>>>
>>> X3D DTD update activity:
>>> ====================================================================
>>> =
>>> ========
>>> 8 June 2015, walmsley brutzman
>>> - corrected MultiTexture not part of Texture2DNodes, instead part of AppearanceChildNodes etc.
>>> - (v3.3+) corrected content model for VolumeStyle nodes, omitting 
>>> MultiTexture
>>> - (v3.2+) CollisionCollection default containerField="collider"
>>> - Added MedicalInterchange profile
>>> ====================================================================
>>> =
>>> ========
>>>
>>> These assets can be found on the X3D Specifications: XML Schema and DOCTYPE Validation page.
>>>
>>> http://www.web3d.org/specifications
>>>
>>> Full documentation updates have been autogenerated for the XML Schema and DOCTYPE, available for X3D versions 3.0 through 3.4. Recommended version:
>>>
>>> http://www.web3d.org/specifications/X3dSchemaDocumentation3.3/x3d-3.
>>> 3
>>> .html
>>> http://www.web3d.org/specifications/X3dDoctypeDocumentation3.3.html
>>>
>>> The X3D Working Group also maintains the X3D Graphics Standards: Specification Relationships diagram up to date, showing the roadmap for all major planned work.
>>>
>>> http://www.web3d.org/specifications/X3dSpecificationRelationships.pn
>>> g 
>>> http://www.web3d.org/specifications/X3dSpecificationRelationships.pd
>>> f
>>>
>>> Please note that X3D version 3.4 is experimental and supports specification development.
>>>
>>> Changes are tested through validation regression testing of 3800+ open source X3D scenes.
>>>
>>> X3D Resources: Examples
>>> http://www.web3d.org/x3d/content/examples/X3dResources.html#Examples
>>>
>>> X3D Resources: Quality Assurance (QA) 
>>> http://www.web3d.org/x3d/content/examples/X3dResources.html#QualityA
>>> s
>>> surance
>>>
>>> Corresponding updates have also been made to:
>>>
>>> X3D Tooltips
>>> http://www.web3d.org/x3d/content/examples/X3dResources.html#Tooltips
>>>
>>> Refreshes will soon follow to:
>>>
>>> X3D Validator
>>> https://savage.nps.edu/X3dValidator
>>>
>>> X3D-Edit Authoring Tool
>>> https://savage.nps.edu/X3D-Edit
>>>
>>> Several further changes are under investigation on the mailing lists:
>>> - Content model for IndexLineSet, LineSet and PointSet.
>>> - Content model for LayoutGroup.
>>> - Interface hierarchy for AudioClip and MovieTexture.
>>>
>>> Feedback welcome, thanks for all testing and contributions. Have fun with X3D!
>>>
>>> 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
>>>
>>> _______________________________________________
>>> x3d-public mailing list
>>> 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
>>
>> _______________________________________________
>> x3d-public mailing list
>> 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
>
> _______________________________________________
> x3d-public mailing list
> 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