HAS-Motion Software Documentation

This is an old revision of the document!

---

group definition]]** dialog. previously-saved query definitions can be loaded and applied to the cmo library to populate groups in the group definition dialog or from the group definitions drop-down menu's i3dopengroupdef.png **load group def & compute groups** option. ===== format ===== as an xml document, a .q3d file is made up of hierarchical elements that are demarcated by tags, indicated by the < and > characters. an element consists of a start tag, <//elementname//>, and end tag, <///elementname//>, and all of the characters in between. alternatively, an element can be defined by a single tag, <//elementname ///>. tags can also contain attributes in the //name="value"// format, further describing the associated element. 1. the top-level element in a .q3d file is //queries//. it contains an arbitrary (1-n) number of //query// elements. 2. the second-level element in a .q3d file is //query//. a //query// element has a //name// attribute (the corresponding group's name) and contains an arbitrary (1-n) number of //definition// elements. 3. the bottom-level element in a .q3d file is //definition//. a //definition// element consists of a single tag and encodes a single sub-group via a number of attributes. ===== dtd ===== formally, a .q3d file respects the document type definition (dtd): <code> <!doctype queries [ <!element queries query+> <!entity query definition+> <!attlist query name cdata #required > <!entity definition> <!attlist definition condition cdata #required query cdata #required workspace cdata #required type cdata #required folder cdata #required name cdata #required component cdata #required max_elements cdata #required negate_result cdata #required events cdata #required exclude_events cdata #required has_tag_ref cdata #required tag_logic cdata #required tag cdata #required has_subject_ref cdata #required subject cdata #required normalize_info cdata #required > ]> </code> }}