The id attribute is required, and must be globally unique. If you change anything, including the version, or whatever, be sure to change the id (guid). The idref must refer to a SourceDefinition defined in the header of this file. See CommutativeRelationshipKind to find out which relationships are commutative. If you have a generic concept, like cancer, and have a sub-category, like breast cancer, then say 'breast cancer' SubcategoryOf 'cancer'. Declares whcih relationship kinds are commutative A unique key to identify the first concept in the relationship A unique key to identify the second concept in the relationship Row#s start with 1, and sequence non-decreasingly (e.g. 1,1,2,2,3,4,5) XPLAIN XPLAIN This can be either a concept of type Unit (such as lbs) or a UnitSubset (such as LbsRangeWeightSubset). There is zero-or one of these per 'test' concept. Each contains a list of items, or a single ItemRef - the conceptID to look at for the REAL PanelItem data (note - PanelRefs MUST be within this file - as they maybe processed at compilation time). For now, this is all optional (backward compatability as of 2006-02-01). We should require at least one source, and probably a defaultsource. The DefaultSource is what is applied implicitly to all data in the file if it has no SourceReference attribute. Source used to describe/display the file itself (e.g. in picker dialogs selecting if the file is to be used). A unique key to identify the concpet about which the rest of the content element applies. URL Web Links for additional information about the given concept for now, only allow a single panel - also - only valid if category = TEST A list of binary-large-objects, such as images, etc. These can be referernced by IDREF above (initially just from Icon-GIF-64x64, but soon also from inside special documentation elements (as part of <img>s).