AbcGeom Schemas vs. Abc Properties

[Pete Segal]

When reading an archive, I iterate over the IObjects and test each against matching schemas:

        if (AbcG::IXform::matches(objHeader))
            ...
        else if (AbcG::ISubD::matches(objHeader))
            ...
        else if (AbcG::IPolyMesh::matches(objHeader))
            ...
        else if (AbcG::IPoints::matches(objHeader))
            ...

I then use the appropriate schema to extract the data from these objects. As expected, I have also observed that these objects also have compound properties that match the schemas, but typically (so far) no other properties.

This leads me to two groups of questions:

1) Once I know that the object matches a schema should I be ignoring (a) the one compound property that matches the schema or (b) all remaining properties? If not, see #2.

2) What is the recommended procedure for handling objects does not match a schema? Is this where we'd expect to find information on things like lights and materials? Is there/will there be guidelines/registry for standardizing/categorizing these extra properties?

Thanks,

Pete

[Steve LaVietes]

AbcGeom is concerned only with the objects which match those Schema.
Unless a non-matching object is expected to have children which do
match, I'd silently ignore it for now.

Conventions for things like materials (which are usually
renderer-specific) will likely arise over time -- but aren't planned
to be part of AbcGeom 1.0.

-stevel

> --
> You received this message because you are subscribed to the Google
> Groups "alembic-discussion" group.
> To post to this group, send email to alembic-d...@googlegroups.com
> To unsubscribe from this group, send email to
> alembic-discuss...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/alembic-discussion?hl=en
>
> For RSS or Atom feeds related to Alembic, see:
>
> http://groups.google.com/group/alembic-dev/feeds
>
> http://groups.google.com/group/alembic-discussion/feeds
>