[X3D-Public] containerField is should or must ? largeattributes; compression

[Joe D Williams]

also, same for color - three points and three colors - in the example. 
One of the greatest conveniences of X3D is dealing in real verifyable 
structured strongly typed fields. I still see the <fieldValue> element 
as a stopgap and emergency measure (instead of just naming the element 
by the attr data name) but that should not mean we drop strong field 
typing at any authoring step.

Thanks Again and Best Regards,
Joe





----- Original Message ----- 
From: "Joe D Williams" <joedwil at earthlink.net>
To: "Johannes Behr" <johannes.behr at igd.fraunhofer.de>; "John A. 
Stewart" <alex.stewart at crc.ca>
Cc: "X3D Graphics public mailing list" <x3d-public at web3d.org>
Sent: Monday, August 23, 2010 7:54 AM
Subject: Re: [X3D-Public] containerField is should or must ? 
largeattributes;compression


I disagree with count field here

            <fieldValue count="9" name="point">
                0 0 0, 1 0 0, 0 1 0
            </fieldValue>

I think the count should be 3 because point is an MFVec3f.
In order to get the validation in the same way as for attrs, then the
count if given should match the number of fields expected when trhe
data was encoded as an attribute.

Thanks and Best Regards,
Joe



----- Original Message ----- 
From: "Johannes Behr" <johannes.behr at igd.fraunhofer.de>
To: "John A. Stewart" <alex.stewart at crc.ca>
Cc: "X3D Graphics public mailing list" <x3d-public at web3d.org>
Sent: Monday, August 23, 2010 4:08 AM
Subject: Re: [X3D-Public] containerField is should or must ?
largeattributes; compression



On 9 Aug 2010, at 15:18, John A. Stewart wrote:

>
> On 2010-08-09, at 12:49 AM, Braden McDaniel wrote:
>>>
>>>
>>> so the idea is appealing.  has anybody yet:
>>> - implemented it in a player, or estimated the work-effort 
>>> involved?
>>
>> I think I recall reading that this is implemented in 
>> InstantReality.

Yes it is. The InstantReality loader can handle data encoded in
CData-blocks since beta7
The count-field is optional:

        <IndexedTriangleSet>
          <fieldValue count="3" name="index">
              0 1 2
          </fieldValue>
          <Coordinate>
            <fieldValue count="9" name="point">
                0 0 0, 1 0 0, 0 1 0
            </fieldValue>
          </Coordinate>
          <Color>
            <fieldValue count="9" name="color">
                0 0 1, 1 0 0, 0 1 0
            </fieldValue>
          </Color>
        </IndexedTriangleSet>

regards
johannes

>
> It was (is), as well as in FreeWRL, if the X3D header indicates 
> version 3.3
>
> -----------------------------------------------------------
> John A. Stewart
> alex.stewart at crc.ca
>
> Network Systems and Technologies -
>        Systemes et technologies des reseaux
> Communications Research Centre Canada  |
>         Centre de recherches sur les communications Canada
>
> 3701 Carling Ave.  |  3701, avenue Carling
> PO Box 11490, Station H  |  CP 11490, succursale H
>         Ottawa ON K2H 8S2   |  Ottawa (Ontario) K2H 8S2
>
> http://www.crc.ca
>
>
>
>
>
>
>
>
> _______________________________________________
> X3D-Public mailing list
> X3D-Public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org

--
Dr. Johannes Behr
Leiter Projektbereich VR

Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
Tel +49 6151 155-510  |  Fax +49 6151 155-196
johannes.behr at igd.fraunhofer.de  |  www.igd.fraunhofer.de


_______________________________________________
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