Paul Sandoz wrote:
>Hi,
>
>
>Alan, for binary X3D documents it might be possible to use a well-formed
>XML document that when converted to a fast infoset document produces a
>final vocabulary that is used as the external vocabulary detailed in the
>X3D specification. After all it is just a matter of putting the
>namespaces, EIIs and AIIs in the correct order.
>
>
>
Its a nice to have but not required. Ie we have out spec prose for ISO
which predefines some of the tables. But, I doubt
we can just use an XML format. That said, I'd much rather maintain an
XML document then a piece of code somewhere that builds it dynamically
each time.
One thought, is there any reason to allow a user-specified data block
for each entry. I'm thinking this might be useful to hang custom algorithm
information... ie the URL pointing to the encoder to use for it. If a
vocabulary was just assigning them by element/attribute name.
>Paul.
>
>
>vocabulary factory
>
> create vocabulary
>
>
>vocabulary
>
> set/get table
>
> clear
>
>
>referenced vocabulary
>
> set/get URI
>
> set/get vocabulary
>
>
>generic serializer
> // before serialize
>
> set external vocabulary
>
> set initial vocabulary
>
> set dynamic vocabulary
>
> // after serialize
>
> get dynamic vocabulary
>
> get final vocabulary
>
>
>generic parser
> // before parse
>
> set hash of external vocabularies
>
> set dynamic vocabulary
>
> // after parse
>
> get external vocabulary
>
> get initial vocabulary
>
> get dynamic vocabulary
>
> get final vocabulary
>
>
>