[X3D-Public] Contour2D containerField analysis
Joe D Williams
joedwil at earthlink.net
Tue Sep 3 08:41:26 PDT 2013
> But I guess this was already discussed, that's why Don didn't want
> us to
get him started on that :)
SIncere Thanks for letting that rest quietly. However, I have abstract
trust that schemification could somehow allow putting all these
considerations into authortime.
Thanks and Best,
Joe
----- Original Message -----
From: "Michalis Kamburelis" <michalis.kambi at gmail.com>
To: "Joe D Williams" <joedwil at earthlink.net>
Cc: "Brutzman, Donald (Don) (CIV)" <brutzman at nps.navy.mil>; "Vincent
Marchetti" <vmarchetti at ameritech.net>; "Cad3D working group"
<Cad at web3d.org>; "X3D Graphics public mailing list"
<x3d-public at web3d.org>
Sent: Monday, September 02, 2013 8:32 AM
Subject: Re: [X3D-Public] Contour2D containerField analysis
> Joe D Williams wrote:
>>> Don't' get me started /don't get me started on that! No further
>>> discussion needed there.
>>
>>
>> Right, all you gotta do to fully step up to XML Schema and get rid
>> of
>> containerField :) or else to make sure that if the containerField
>> is not
>> there we give a suitable default, and that if it is there then is
>> it a
>> correct choice. That way we don't need masses of wrappers in our
>> user
>> code, like if we actually transcoded literally and did not rely on
>> a
>> schema to advise the processor about structures and content models.
>
> Completely getting rid of containerField will require changes, at
> least around Collision.proxy and MetadataSet.value definitions.
> Right now, using these fields requires you to use containerField, as
> you put there nodes that in other circumstances are attached to
> different fields. Getting rid of containerField will probably
> require inventing some new nodes to make things unambiguous even
> without containerField.
>
> BTW, I completely agree, I'm all after getting rid of
> containerField. But I guess this was already discussed, that's why
> Don didn't want us to get him started on that :)
>
> Regards,
> Michalis
More information about the X3D-Public
mailing list