6.7. Child objects list

<object name="NAME" type="TYPE LIST"  optional="yes OR no">
    <description>
        Describe the purpose or meaning of this child object here.
    </description>
</object>
...

        

Include an object element here for each child object this type expects. Include a contextual object name in the name attribute, or use a value of "*" (star) if the name is irrelevant. Include a list of types the child object must have in the type attribute, seperated by commas. If the child object is not required, use a value of "yes" in the optional attribute. If omitted, optional defaults to "no".

Object names may contain any character, except "," (comma), '/' (slash), '^' (caret), '?' (question mark) and '#' (number or hash mark), '"' (quote), '&' (ampersand), '<' (left angle) or '>' (right angle).

Different OTDs may define subobjects with the same name. What this means, whether it causes any problems or conflicts, is entirely dependent on the types and their implementations. There probably won't be any major problems; the nature of metaobjects fits with this kind of combining.

To help avoid name conflicts between subobjects for different types, use the following naming convention: prepend the object name with your type's group name and a colon, like this:

group:object_name

For example:

a3dl:orientation