[x3d-public] X3D4 finalization endgame: Field naming reconciliation as synonyms

[Don Brutzman]

Clearly duplicated definition of synonym field values is a model error that validation-oriented tools will notice and report.

As carefully phrased in prior response and in existing specification, when an X3D model is erroneous then behavior is undefined.

So there is no need to define expected response (first second alphabetical neither nor) and no additional burden on implementers to cope with duplicates.  The implementation can ignore silently, protest once, protest twice, halt and catch fire, whatever.  8)

On 11/29/2020 10:10 AM, John Carlson wrote:
> 
> Fixed editing mistake.
> 
> On Sun, Nov 29, 2020 at 12:09 PM John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> wrote:
> 
>     I think it's more critical when both oldName and newName exist in XML or VRML (in JSON, last takes precedence, I think). Which value do you store last when both the new and old attributes are specified in XML?   Some kind of ordering will exist in the tools processing the XML, but without a standard, there may be alternate implementations.

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