Schema TestDescription.xsd


schema location:  D:\Atml & SIWG\Web\ATML\TestDescription.xsd
targetNamespace:  urn:IEEE-1671.1:2009:TestDescription
 
Elements  Complex types  Simple types 
TestDescription  ActionOutcomeType  ComparisonResult 
ActionResultType  Detectability 
ActionType  ElectroOpticalInterfaceType 
AutomaticGeneration  FailureType 
binaryArrayDescription  OutcomeValue 
binaryDescription  SeverityLevel 
booleanArrayDescription  SignalCharacteristicRole 
booleanDescription  SignalRole 
CollectionDescription  SignalType 
complexArrayDescription  TestType 
complexDescription 
Component 
Condition 
Conditions 
Connection 
ConnectionDatum 
ConnectionDatumDescription 
dateTimeArrayDescription 
dateTimeDescription 
DatumDescriptionType 
DetailedConnectorLocation 
DetailedTestInformation 
DetectionIsolation 
doubleArrayDescription 
doubleDescription 
FaultData 
FaultFailureType 
hexadecimalArrayDescription 
hexadecimalDescription 
IeeeStd1641 
IeeeStd1641AttributeChanges 
IeeeStd1641InValues 
IeeeStd1641OutValues 
IeeeStd1641PortValues 
IncrementedValue 
IndexedArrayDescriptionType 
Initialization 
integerArrayDescription 
integerDescription 
InterfaceRequirements 
octalArrayDescription 
octalDescription 
OperationChange 
OperationCompare 
OperationConditional 
OperationConnect 
OperationDisable 
OperationDisconnect 
OperationEnable 
OperationMessageIn 
OperationMessageOut 
OperationOther 
OperationRead 
OperationReadStateVariable 
OperationRepeat 
OperationReset 
OperationResetAll 
Operations 
OperationSetStateVariable 
OperationSetup 
OperationType 
OperationWaitFor 
Outcome 
PerformanceCharacteristics 
PerformanceCharacteristicType 
PinFunction 
PostConditions 
PowerSpecification 
PreConditions 
Result 
SessionAction 
SessionOutcome 
SignalInformation 
SignalRequirements 
SignalSynchronization 
stringArrayDescription 
stringDescription 
Termination 
Test 
TestGroupDiagnosticModel 
TestGroupParallel 
TestGroupSequence 
TestGroupSerial 
TestGroupType 
TestGroupUnspecifiedOrder 
TsfClass 
TsfClassAttribute 
TsfClassAttributeName 
unsignedIntegerArrayDescription 
unsignedIntegerDescription 
UUT 
ValueDescription 
ValueFromActionParameter 
ValueFromActionResults 
ValueFromIterator 
ValueFromOperationMeasurement 
ValueFromOperationMessageIn 
ValueFromTestGroupParameter 


schema location:  D:\Atml & SIWG\Web\ATML\Common.xsd
targetNamespace:  urn:IEEE-1671:2010:Common
 
Groups  Complex types  Simple types  Attr. groups 
DatumQuality  binary  ArrayIndexor  ClassifiedAttributes 
binaryArray  ComparisonOperator  DocumentRootAttributes 
boolean  EqualityComparisonOperator  RepeatedItemAttributes 
booleanArray  HexValue  UnitAttributes 
Collection  LogicalOperator 
CollectionArray  MaskOperator 
complex  NonBlankString 
complexArray  NonBlankURI 
Connector  PortDirection 
ConnectorLocation  PortType 
ConnectorPin  StandardUnit 
dateTime  Uuid 
dateTimeArray 
DatumType 
Document 
DocumentList 
DocumentReference 
double 
doubleArray 
EnvironmentalElements 
EnvironmentalRequirements 
Extension 
HardwareInstance 
hexadecimal 
hexadecimalArray 
IdentificationNumber 
IndexedArrayType 
integer 
integerArray 
Interface 
ItemDescription 
ItemDescriptionReference 
ItemInstance 
ItemInstanceReference 
Limit 
LimitExpected 
LimitMask 
LimitPair 
long 
longArray 
MailingAddress 
ManufacturerData 
ManufacturerIdentificationNumber 
NamedValue 
octal 
octalArray 
Operator 
Organization 
Person 
PhysicalInterface 
Port 
SingleLimit 
SoftwareInstance 
string 
stringArray 
unsignedInteger 
unsignedIntegerArray 
unsignedLong 
unsignedLongArray 
UserDefinedIdentificationNumber 
Value 
WorkOrder 


schema location:  D:\Atml & SIWG\Web\ATML\HardwareCommon.xsd
targetNamespace:  urn:IEEE-1671:2010:HardwareCommon
 
Complex types  Simple types 
AnalogTriggerPropertyGroup  DigitalEdge 
Capabilities  DigitalLevel 
Capability  ErrorType 
CapabilityMap  LevelUnits 
Characteristic  PulseUnits 
ControlLanguage  TriggerPortType 
CrossPointSwitch 
DetectionType 
DigitalTriggerPropertyGroup 
Driver 
DriverModule 
FacilitiesRequirements 
Feature 
Generic 
Guaranteed 
HardwareItemDescription 
Item 
IVI 
IVI-C 
IVI-COM 
IVI.NET 
LANTriggerPropertyGroup 
LevelType 
Mapping 
MatrixPort 
MatrixSwitch 
MinPulseWidthType 
Network 
NetworkNode 
Nominal 
OperationalRequirements 
PhysicalCharacteristics 
PowerSpecifications 
Register 
RepeatedItem 
Resource 
Resources 
SCPI 
SoftwareTriggerPropertyGroup 
Specification 
SpecificationConditions 
SpecificationGroup 
Specifications 
Switch 
Switching 
SwitchPort 
Trigger 
TriggerPort 
TriggerPropertyGroup 
Triggers 
Typical 
VersionIdentifier 
VPP 


element TestDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
content complex
children TsfLibraries UUT InterfaceRequirements SignalRequirements PerformanceCharacteristics DetailedTestInformation FailureFaultData AutomaticGeneration
attributes
Name  Type  Use  Default  Fixed  Annotation
uuid  c:Uuidrequired      
documentation 
A universal unique identifier for the element containing this attribute.
classified  xs:booleanoptional      
documentation 
An indication that the element is or is not classified.
securityClassification  c:NonBlankStringoptional      
documentation 
A use-case determined string declaring the security classification level of the element containing this attribute and the subordinate branch of the XML document.
name  c:NonBlankString      
documentation 
Name of the instance document.
version  c:NonBlankString      
documentation 
Version of the instance document.
identity constraints
  Name  Refer  Selector  Field(s)  
key  componentKey    .//td:Component  @ID  
keyref  componentRef  td:componentKey  .//td:AdjustComponent  @componentID  
key  faultKey    .//td:Component/td:Faults/td:Fault  @ID  
keyref  faultOutcomeRef  td:faultKey  .//td:Outcome/td:DetectionIsolation/td:Faults/td:Fault  @faultID  
keyref  faultNextStepRef  td:faultKey  .//td:NextStep/td:DetectionIsolation/td:Faults/td:Fault  @faultID  
key  failureKey    .//td:FailureFaultData/td:Failures/td:Failure  @ID  
keyref  failureOutcomeRef  td:failureKey  .//td:Outcome/td:DetectionIsolation/td:Failures/td:Failure  @failureID  
keyref  failureNextStepRef  td:failureKey  .//td:NextStep/td:DetectionIsolation/td:Failures/td:Failure  @failureID  
key  inputKey    .//td:PerformanceCharacteristics/td:Inputs/td:Input  @ID  
keyref  inputRef  td:inputKey  .//td:RelatedInputs/td:RelatedInput  @inputID  
key  controlKey    .//td:PerformanceCharacteristics/td:Controls/td:Control  @ID  
keyref  controlRef  td:controlKey  .//td:RelatedControls/td:RelatedControl  @controlID  
key  tsfLibraryKey    ./td:TsfLibraries/td:TsfLibrary  @ID  
keyref  tsfLibraryRef  td:tsfLibraryKey  .//td:TsfClass  @tsfLibraryID  
key  toolKey    .//td:Tools/td:Tool  @ID  
keyref  toolRef  td:toolKey  .//td:Behavior/td:AutomaticGeneration  @toolID  
annotation
documentation 
This element shall contain information defining test performance, test conditions, diagnostic requirements, and support equipment to locate, align, and verify the proper operation of a UUT.
source
<xs:element name="TestDescription">
  <xs:annotation>
    <xs:documentation>This element shall contain information defining test performance, test conditions, diagnostic requirements, and support equipment to locate, align, and verify the proper operation of a UUT.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="TsfLibraries" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall identify the Test Signal Framework (TSF) Libraries referenced in the current instance document. These TSF Libraries describe the interface and behavior of IEEE Std 1641 signals used in the instance document. Refer to clause 6 of IEEE 1641 for information on describing TSF Libraries.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="TsfLibrary" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>Identifies one TSF Library by referencing the external XML documents that describe the interface and behavior of signals from the TSF Library.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="XmlSchemaURL" type="c:NonBlankURI">
                    <xs:annotation>
                      <xs:documentation>References the XML instance document that describes the interface and behavior of signals from the TSF Library. For each TSF Library, the file referenced by this element shall be identical to the file referenced by the ‘xsi:schemaLocation’ attribute of the root element. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="XmlInstanceDocumentURL" type="c:NonBlankURI">
                    <xs:annotation>
                      <xs:documentation>References the XML Schema document that defines the interface of the TSF Library.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="name" type="c:NonBlankString">
                  <xs:annotation>
                    <xs:documentation>Descriptive name for the TSF Library.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
                <xs:attribute name="ID" type="c:NonBlankString" use="required">
                  <xs:annotation>
                    <xs:documentation>Unique identifier, enables referencing of the TSF Library element.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="UUT" type="td:UUT">
        <xs:annotation>
          <xs:documentation>Shall contain descriptive information for the UUT.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="InterfaceRequirements" type="td:InterfaceRequirements" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall describe the characteristics of equipment and circuitry required to test the UUT, excluding the test equipment (e.g., UUT connector information).</xs:documentation>
        </xs:annotation>
        <xs:key name="interfaceConnectorKey">
          <xs:selector xpath="./c:Connectors/c:Connector"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="interfaceConnectorRef" refer="td:interfaceConnectorKey">
          <xs:selector xpath="./c:Ports/c:Port/c:ConnectorPins/c:ConnectorPin"/>
          <xs:field xpath="@connectorID"/>
        </xs:keyref>
        <xs:unique name="interfacePortNamesUnique">
          <xs:selector xpath="./c:Ports/c:Port"/>
          <xs:field xpath="@name"/>
        </xs:unique>
        <xs:key name="testPointKey">
          <xs:selector xpath="./td:TestPoints/td:TestPoint"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:key name="electroOpticalInterfaceKey">
          <xs:selector xpath="./td:ElectroOpticalInterfaces/td:ElectroOpticalInterface"/>
          <xs:field xpath="@ID"/>
        </xs:key>
      </xs:element>
      <xs:element name="SignalRequirements" type="td:SignalRequirements" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall specify all UUT signal requirements for testing the UUT.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="PerformanceCharacteristics" type="td:PerformanceCharacteristics" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall describe the performance characteristics of the UUT. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="DetailedTestInformation" type="td:DetailedTestInformation">
        <xs:annotation>
          <xs:documentation>Shall contain all of the sufficient data for each UUT test to completely describe all input conditions and measurements required.</xs:documentation>
        </xs:annotation>
        <xs:key name="stateVariableKey">
          <xs:selector xpath=".//td:StateVariable"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="stateVariableOperationRef" refer="td:stateVariableKey">
          <xs:selector xpath=".//td:Operation"/>
          <xs:field xpath="@stateVariableID"/>
        </xs:keyref>
        <xs:key name="stateVariableValueKey">
          <xs:selector xpath=".//td:StateVariable/td:Values/td:Value"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="stateVariableValueInitialRef" refer="td:stateVariableValueKey">
          <xs:selector xpath=".//td:StateVariable/td:InitialValue"/>
          <xs:field xpath="@valueID"/>
        </xs:keyref>
        <xs:keyref name="stateVariableValuePreConditionRef" refer="td:stateVariableValueKey">
          <xs:selector xpath=".//td:PreCondition/td:StateVariableValue"/>
          <xs:field xpath="@stateVariableValueID"/>
        </xs:keyref>
        <xs:keyref name="stateVariableValuePostConditionRef" refer="td:stateVariableValueKey">
          <xs:selector xpath=".//td:PostCondition/td:StateVariableValue"/>
          <xs:field xpath="@stateVariableValueID"/>
        </xs:keyref>
        <xs:keyref name="stateVariableValueOperationRef" refer="td:stateVariableValueKey">
          <xs:selector xpath=".//td:Operation"/>
          <xs:field xpath="@stateVariableValueID"/>
        </xs:keyref>
        <xs:key name="testGroupKey">
          <xs:selector xpath=".//td:TestGroup"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="testGroupEntryPointRef" refer="td:testGroupKey">
          <xs:selector xpath=".//td:TestGroupEntryPoint"/>
          <xs:field xpath="@testGroupID"/>
        </xs:keyref>
        <xs:keyref name="testGroupCallRef" refer="td:testGroupKey">
          <xs:selector xpath=".//td:Behavior/td:TestGroupCall"/>
          <xs:field xpath="@testGroupID"/>
        </xs:keyref>
        <xs:keyref name="testGroupStepRef" refer="td:testGroupKey">
          <xs:selector xpath=".//td:Step/td:TestGroupReference"/>
          <xs:field xpath="@testGroupID"/>
        </xs:keyref>
        <xs:keyref name="testGroupInitializationRef" refer="td:testGroupKey">
          <xs:selector xpath=".//td:InitializationTestGroup"/>
          <xs:field xpath="@testGroupID"/>
        </xs:keyref>
        <xs:keyref name="testGroupTerminationRef" refer="td:testGroupKey">
          <xs:selector xpath=".//td:TerminationTestGroup"/>
          <xs:field xpath="@testGroupID"/>
        </xs:keyref>
        <xs:key name="testGroupOutcomeKey">
          <xs:selector xpath=".//td:TestGroup/td:Outcomes/td:Outcome"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="testGroupOutcomeRef" refer="td:testGroupOutcomeKey">
          <xs:selector xpath=".//td:Step/td:Results/td:Result/td:TestGroupOutcomeReference"/>
          <xs:field xpath="@testGroupOutcomeID"/>
        </xs:keyref>
        <xs:key name="testGroupParameterKey">
          <xs:selector xpath=".//td:TestGroup/td:ParameterDescriptions/td:ParameterDescription"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="testGroupParameterDatumRef" refer="td:testGroupParameterKey">
          <xs:selector xpath=".//c:Datum"/>
          <xs:field xpath="@testGroupParameterID"/>
        </xs:keyref>
        <xs:keyref name="testGroupParameterValueRef" refer="td:testGroupParameterKey">
          <xs:selector xpath=".//td:ValueToParameter"/>
          <xs:field xpath="@testGroupParameterID"/>
        </xs:keyref>
        <xs:key name="testGroupTestResultKey">
          <xs:selector xpath=".//td:TestGroup/td:TestResultDescriptions/td:TestResultDescription"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="testGroupTestResultTestResultRef" refer="td:testGroupTestResultKey">
          <xs:selector xpath=".//td:Action/td:TestResults/td:TestResult/td:ValueToTestResult"/>
          <xs:field xpath="@testGroupTestResultID"/>
        </xs:keyref>
        <xs:keyref name="testGroupTestResultSessionDatumRef" refer="td:testGroupTestResultKey">
          <xs:selector xpath=".//td:Action/td:SessionData/td:SessionDatum/td:ValueToTestResult"/>
          <xs:field xpath="@testGroupTestResultID"/>
        </xs:keyref>
        <xs:key name="actionKey">
          <xs:selector xpath=".//td:Action"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="actionInitializationRef" refer="td:actionKey">
          <xs:selector xpath=".//td:InitializationAction"/>
          <xs:field xpath="@actionID"/>
        </xs:keyref>
        <xs:keyref name="actionTerminationRef" refer="td:actionKey">
          <xs:selector xpath=".//td:TerminationAction"/>
          <xs:field xpath="@actionID"/>
        </xs:keyref>
        <xs:keyref name="actionStepRef" refer="td:actionKey">
          <xs:selector xpath=".//td:Step/td:ActionReference"/>
          <xs:field xpath="@actionID"/>
        </xs:keyref>
        <xs:keyref name="actionTestGroupRef" refer="td:actionKey">
          <xs:selector xpath=".//td:TestGroup/td:ActionReferences/td:ActionReference"/>
          <xs:field xpath="@actionID"/>
        </xs:keyref>
        <xs:keyref name="actionEntryPointRef" refer="td:actionKey">
          <xs:selector xpath=".//td:ActionEntryPoint"/>
          <xs:field xpath="@actionID"/>
        </xs:keyref>
        <xs:key name="actionOutcomeKey">
          <xs:selector xpath=".//td:Action/td:Outcomes/td:Outcome"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="actionOutcomeResultRef" refer="td:actionOutcomeKey">
          <xs:selector xpath=".//td:Result/td:ActionOutcomeReference"/>
          <xs:field xpath="@actionOutcomeID"/>
        </xs:keyref>
        <xs:keyref name="actionOutcomeOperationRef" refer="td:actionOutcomeKey">
          <xs:selector xpath=".//td:Operation/td:Results/td:Result"/>
          <xs:field xpath="@actionOutcomeID"/>
        </xs:keyref>
        <xs:key name="testResultKey">
          <xs:selector xpath=".//td:Action/td:TestResults/td:TestResult"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="testResultDatumRef" refer="td:testResultKey">
          <xs:selector xpath=".//c:Datum/td:TestResult"/>
          <xs:field xpath="@testResultID"/>
        </xs:keyref>
        <xs:keyref name="testResultOperationRef" refer="td:testResultKey">
          <xs:selector xpath=".//td:Operation/td:ValueToTestResult"/>
          <xs:field xpath="@testResultID"/>
        </xs:keyref>
        <xs:keyref name="resultOutValueResultID" refer="td:testResultKey">
          <xs:selector xpath=".//td:IeeeStd1641/td:IeeeStd1641OutValues/td:ResultOutValue"/>
          <xs:field xpath="@resultID"/>
        </xs:keyref>
        <xs:key name="sessionDatumKey">
          <xs:selector xpath=".//td:Action/td:SessionData/td:SessionDatum"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="sessionDatumDatumRef" refer="td:sessionDatumKey">
          <xs:selector xpath=".//c:Datum/td:SessionDatum"/>
          <xs:field xpath="@sessionDatumID"/>
        </xs:keyref>
        <xs:keyref name="sessionDatumOperationRef" refer="td:sessionDatumKey">
          <xs:selector xpath=".//td:Operation/td:ValueToSessionDatum"/>
          <xs:field xpath="@sessionDatumID"/>
        </xs:keyref>
        <xs:key name="measurementKey">
          <xs:selector xpath=".//td:Operation/td:Measurement"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="measurementRef" refer="td:measurementKey">
          <xs:selector xpath=".//c:Datum"/>
          <xs:field xpath="@measurementID"/>
        </xs:keyref>
        <xs:key name="globalSignalKey">
          <xs:selector xpath=".//td:GlobalSignal/td:Source"/>
          <xs:field xpath="@ID"/>
        </xs:key>
        <xs:keyref name="globalSignalReferenceRef" refer="td:globalSignalKey">
          <xs:selector xpath=".//td:GlobalSignalReference"/>
          <xs:field xpath="@globalSignalID"/>
        </xs:keyref>
        <xs:keyref name="globalSignalOperationRef" refer="td:globalSignalKey">
          <xs:selector xpath=".//td:GlobalSignalOperation"/>
          <xs:field xpath="@globalSignalID"/>
        </xs:keyref>
      </xs:element>
      <xs:element name="FailureFaultData" type="td:FaultData" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall contain UUT fault data, including faults and failures. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="AutomaticGeneration" type="td:AutomaticGeneration" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall identify the Automatic Test Program Generation (ATPG) tools used to generate the test program.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attributeGroup ref="c:DocumentRootAttributes"/>
    <xs:attribute name="name" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Name of the instance document.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="version" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Version of the instance document.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
  <xs:key name="componentKey">
    <xs:selector xpath=".//td:Component"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="componentRef" refer="td:componentKey">
    <xs:selector xpath=".//td:AdjustComponent"/>
    <xs:field xpath="@componentID"/>
  </xs:keyref>
  <xs:key name="faultKey">
    <xs:selector xpath=".//td:Component/td:Faults/td:Fault"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="faultOutcomeRef" refer="td:faultKey">
    <xs:selector xpath=".//td:Outcome/td:DetectionIsolation/td:Faults/td:Fault"/>
    <xs:field xpath="@faultID"/>
  </xs:keyref>
  <xs:keyref name="faultNextStepRef" refer="td:faultKey">
    <xs:selector xpath=".//td:NextStep/td:DetectionIsolation/td:Faults/td:Fault"/>
    <xs:field xpath="@faultID"/>
  </xs:keyref>
  <xs:key name="failureKey">
    <xs:selector xpath=".//td:FailureFaultData/td:Failures/td:Failure"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="failureOutcomeRef" refer="td:failureKey">
    <xs:selector xpath=".//td:Outcome/td:DetectionIsolation/td:Failures/td:Failure"/>
    <xs:field xpath="@failureID"/>
  </xs:keyref>
  <xs:keyref name="failureNextStepRef" refer="td:failureKey">
    <xs:selector xpath=".//td:NextStep/td:DetectionIsolation/td:Failures/td:Failure"/>
    <xs:field xpath="@failureID"/>
  </xs:keyref>
  <xs:key name="inputKey">
    <xs:selector xpath=".//td:PerformanceCharacteristics/td:Inputs/td:Input"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="inputRef" refer="td:inputKey">
    <xs:selector xpath=".//td:RelatedInputs/td:RelatedInput"/>
    <xs:field xpath="@inputID"/>
  </xs:keyref>
  <xs:key name="controlKey">
    <xs:selector xpath=".//td:PerformanceCharacteristics/td:Controls/td:Control"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="controlRef" refer="td:controlKey">
    <xs:selector xpath=".//td:RelatedControls/td:RelatedControl"/>
    <xs:field xpath="@controlID"/>
  </xs:keyref>
  <xs:key name="tsfLibraryKey">
    <xs:selector xpath="./td:TsfLibraries/td:TsfLibrary"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="tsfLibraryRef" refer="td:tsfLibraryKey">
    <xs:selector xpath=".//td:TsfClass"/>
    <xs:field xpath="@tsfLibraryID"/>
  </xs:keyref>
  <xs:key name="toolKey">
    <xs:selector xpath=".//td:Tools/td:Tool"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="toolRef" refer="td:toolKey">
    <xs:selector xpath=".//td:Behavior/td:AutomaticGeneration"/>
    <xs:field xpath="@toolID"/>
  </xs:keyref>
</xs:element>

element TestDescription/TsfLibraries
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children TsfLibrary
annotation
documentation 
Shall identify the Test Signal Framework (TSF) Libraries referenced in the current instance document. These TSF Libraries describe the interface and behavior of IEEE Std 1641 signals used in the instance document. Refer to clause 6 of IEEE 1641 for information on describing TSF Libraries.
source
<xs:element name="TsfLibraries" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall identify the Test Signal Framework (TSF) Libraries referenced in the current instance document. These TSF Libraries describe the interface and behavior of IEEE Std 1641 signals used in the instance document. Refer to clause 6 of IEEE 1641 for information on describing TSF Libraries.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="TsfLibrary" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Identifies one TSF Library by referencing the external XML documents that describe the interface and behavior of signals from the TSF Library.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="XmlSchemaURL" type="c:NonBlankURI">
              <xs:annotation>
                <xs:documentation>References the XML instance document that describes the interface and behavior of signals from the TSF Library. For each TSF Library, the file referenced by this element shall be identical to the file referenced by the ‘xsi:schemaLocation’ attribute of the root element. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="XmlInstanceDocumentURL" type="c:NonBlankURI">
              <xs:annotation>
                <xs:documentation>References the XML Schema document that defines the interface of the TSF Library.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="name" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>Descriptive name for the TSF Library.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="ID" type="c:NonBlankString" use="required">
            <xs:annotation>
              <xs:documentation>Unique identifier, enables referencing of the TSF Library element.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element TestDescription/TsfLibraries/TsfLibrary
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children XmlSchemaURL XmlInstanceDocumentURL
attributes
Name  Type  Use  Default  Fixed  Annotation
name  c:NonBlankString      
documentation 
Descriptive name for the TSF Library.
ID  c:NonBlankStringrequired      
documentation 
Unique identifier, enables referencing of the TSF Library element.
annotation
documentation 
Identifies one TSF Library by referencing the external XML documents that describe the interface and behavior of signals from the TSF Library.
source
<xs:element name="TsfLibrary" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Identifies one TSF Library by referencing the external XML documents that describe the interface and behavior of signals from the TSF Library.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="XmlSchemaURL" type="c:NonBlankURI">
        <xs:annotation>
          <xs:documentation>References the XML instance document that describes the interface and behavior of signals from the TSF Library. For each TSF Library, the file referenced by this element shall be identical to the file referenced by the ‘xsi:schemaLocation’ attribute of the root element. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="XmlInstanceDocumentURL" type="c:NonBlankURI">
        <xs:annotation>
          <xs:documentation>References the XML Schema document that defines the interface of the TSF Library.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="name" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Descriptive name for the TSF Library.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="ID" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>Unique identifier, enables referencing of the TSF Library element.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element TestDescription/TsfLibraries/TsfLibrary/XmlSchemaURL
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankURI
properties
isRef 0
content simple
facets
minLength 1
annotation
documentation 
References the XML instance document that describes the interface and behavior of signals from the TSF Library. For each TSF Library, the file referenced by this element shall be identical to the file referenced by the ‘xsi:schemaLocation’ attribute of the root element. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically.
source
<xs:element name="XmlSchemaURL" type="c:NonBlankURI">
  <xs:annotation>
    <xs:documentation>References the XML instance document that describes the interface and behavior of signals from the TSF Library. For each TSF Library, the file referenced by this element shall be identical to the file referenced by the ‘xsi:schemaLocation’ attribute of the root element. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
</xs:element>

element TestDescription/TsfLibraries/TsfLibrary/XmlInstanceDocumentURL
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankURI
properties
isRef 0
content simple
facets
minLength 1
annotation
documentation 
References the XML Schema document that defines the interface of the TSF Library.
source
<xs:element name="XmlInstanceDocumentURL" type="c:NonBlankURI">
  <xs:annotation>
    <xs:documentation>References the XML Schema document that defines the interface of the TSF Library.</xs:documentation>
  </xs:annotation>
</xs:element>

element TestDescription/UUT
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:UUT
properties
isRef 0
content complex
children Description Category PhysicalCharacteristics Documentation TestData
annotation
documentation 
Shall contain descriptive information for the UUT.
source
<xs:element name="UUT" type="td:UUT">
  <xs:annotation>
    <xs:documentation>Shall contain descriptive information for the UUT.</xs:documentation>
  </xs:annotation>
</xs:element>

element TestDescription/InterfaceRequirements
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:InterfaceRequirements
properties
isRef 0
content complex
children Ports Connectors TestPoints ElectroOpticalInterfaces Fixtures SignalConditioning Extension
identity constraints
  Name  Refer  Selector  Field(s)  
key  interfaceConnectorKey    ./c:Connectors/c:Connector  @ID  
keyref  interfaceConnectorRef  td:interfaceConnectorKey  ./c:Ports/c:Port/c:ConnectorPins/c:ConnectorPin  @connectorID  
unique  interfacePortNamesUnique    ./c:Ports/c:Port  @name  
key  testPointKey    ./td:TestPoints/td:TestPoint  @ID  
key  electroOpticalInterfaceKey    ./td:ElectroOpticalInterfaces/td:ElectroOpticalInterface  @ID  
annotation
documentation 
Shall describe the characteristics of equipment and circuitry required to test the UUT, excluding the test equipment (e.g., UUT connector information).
source
<xs:element name="InterfaceRequirements" type="td:InterfaceRequirements" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describe the characteristics of equipment and circuitry required to test the UUT, excluding the test equipment (e.g., UUT connector information).</xs:documentation>
  </xs:annotation>
  <xs:key name="interfaceConnectorKey">
    <xs:selector xpath="./c:Connectors/c:Connector"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="interfaceConnectorRef" refer="td:interfaceConnectorKey">
    <xs:selector xpath="./c:Ports/c:Port/c:ConnectorPins/c:ConnectorPin"/>
    <xs:field xpath="@connectorID"/>
  </xs:keyref>
  <xs:unique name="interfacePortNamesUnique">
    <xs:selector xpath="./c:Ports/c:Port"/>
    <xs:field xpath="@name"/>
  </xs:unique>
  <xs:key name="testPointKey">
    <xs:selector xpath="./td:TestPoints/td:TestPoint"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:key name="electroOpticalInterfaceKey">
    <xs:selector xpath="./td:ElectroOpticalInterfaces/td:ElectroOpticalInterface"/>
    <xs:field xpath="@ID"/>
  </xs:key>
</xs:element>

element TestDescription/SignalRequirements
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:SignalRequirements
properties
isRef 0
content complex
children SignalRequirement
annotation
documentation 
Shall specify all UUT signal requirements for testing the UUT.
source
<xs:element name="SignalRequirements" type="td:SignalRequirements" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall specify all UUT signal requirements for testing the UUT.</xs:documentation>
  </xs:annotation>
</xs:element>

element TestDescription/PerformanceCharacteristics
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:PerformanceCharacteristics
properties
isRef 0
content complex
children Inputs Outputs Controls Extension
annotation
documentation 
Shall describe the performance characteristics of the UUT. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:element name="PerformanceCharacteristics" type="td:PerformanceCharacteristics" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describe the performance characteristics of the UUT. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
</xs:element>

element TestDescription/DetailedTestInformation
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:DetailedTestInformation
properties
isRef 0
content complex
children EntryPoints Actions TestGroups StateVariables GlobalSignals Extension
identity constraints
  Name  Refer  Selector  Field(s)  
key  stateVariableKey    .//td:StateVariable  @ID  
keyref  stateVariableOperationRef  td:stateVariableKey  .//td:Operation  @stateVariableID  
key  stateVariableValueKey    .//td:StateVariable/td:Values/td:Value  @ID  
keyref  stateVariableValueInitialRef  td:stateVariableValueKey  .//td:StateVariable/td:InitialValue  @valueID  
keyref  stateVariableValuePreConditionRef  td:stateVariableValueKey  .//td:PreCondition/td:StateVariableValue  @stateVariableValueID  
keyref  stateVariableValuePostConditionRef  td:stateVariableValueKey  .//td:PostCondition/td:StateVariableValue  @stateVariableValueID  
keyref  stateVariableValueOperationRef  td:stateVariableValueKey  .//td:Operation  @stateVariableValueID  
key  testGroupKey    .//td:TestGroup  @ID  
keyref  testGroupEntryPointRef  td:testGroupKey  .//td:TestGroupEntryPoint  @testGroupID  
keyref  testGroupCallRef  td:testGroupKey  .//td:Behavior/td:TestGroupCall  @testGroupID  
keyref  testGroupStepRef  td:testGroupKey  .//td:Step/td:TestGroupReference  @testGroupID  
keyref  testGroupInitializationRef  td:testGroupKey  .//td:InitializationTestGroup  @testGroupID  
keyref  testGroupTerminationRef  td:testGroupKey  .//td:TerminationTestGroup  @testGroupID  
key  testGroupOutcomeKey    .//td:TestGroup/td:Outcomes/td:Outcome  @ID  
keyref  testGroupOutcomeRef  td:testGroupOutcomeKey  .//td:Step/td:Results/td:Result/td:TestGroupOutcomeReference  @testGroupOutcomeID  
key  testGroupParameterKey    .//td:TestGroup/td:ParameterDescriptions/td:ParameterDescription  @ID  
keyref  testGroupParameterDatumRef  td:testGroupParameterKey  .//c:Datum  @testGroupParameterID  
keyref  testGroupParameterValueRef  td:testGroupParameterKey  .//td:ValueToParameter  @testGroupParameterID  
key  testGroupTestResultKey    .//td:TestGroup/td:TestResultDescriptions/td:TestResultDescription  @ID  
keyref  testGroupTestResultTestResultRef  td:testGroupTestResultKey  .//td:Action/td:TestResults/td:TestResult/td:ValueToTestResult  @testGroupTestResultID  
keyref  testGroupTestResultSessionDatumRef  td:testGroupTestResultKey  .//td:Action/td:SessionData/td:SessionDatum/td:ValueToTestResult  @testGroupTestResultID  
key  actionKey    .//td:Action  @ID  
keyref  actionInitializationRef  td:actionKey  .//td:InitializationAction  @actionID  
keyref  actionTerminationRef  td:actionKey  .//td:TerminationAction  @actionID  
keyref  actionStepRef  td:actionKey  .//td:Step/td:ActionReference  @actionID  
keyref  actionTestGroupRef  td:actionKey  .//td:TestGroup/td:ActionReferences/td:ActionReference  @actionID  
keyref  actionEntryPointRef  td:actionKey  .//td:ActionEntryPoint  @actionID  
key  actionOutcomeKey    .//td:Action/td:Outcomes/td:Outcome  @ID  
keyref  actionOutcomeResultRef  td:actionOutcomeKey  .//td:Result/td:ActionOutcomeReference  @actionOutcomeID  
keyref  actionOutcomeOperationRef  td:actionOutcomeKey  .//td:Operation/td:Results/td:Result  @actionOutcomeID  
key  testResultKey    .//td:Action/td:TestResults/td:TestResult  @ID  
keyref  testResultDatumRef  td:testResultKey  .//c:Datum/td:TestResult  @testResultID  
keyref  testResultOperationRef  td:testResultKey  .//td:Operation/td:ValueToTestResult  @testResultID  
keyref  resultOutValueResultID  td:testResultKey  .//td:IeeeStd1641/td:IeeeStd1641OutValues/td:ResultOutValue  @resultID  
key  sessionDatumKey    .//td:Action/td:SessionData/td:SessionDatum  @ID  
keyref  sessionDatumDatumRef  td:sessionDatumKey  .//c:Datum/td:SessionDatum  @sessionDatumID  
keyref  sessionDatumOperationRef  td:sessionDatumKey  .//td:Operation/td:ValueToSessionDatum  @sessionDatumID  
key  measurementKey    .//td:Operation/td:Measurement  @ID  
keyref  measurementRef  td:measurementKey  .//c:Datum  @measurementID  
key  globalSignalKey    .//td:GlobalSignal/td:Source  @ID  
keyref  globalSignalReferenceRef  td:globalSignalKey  .//td:GlobalSignalReference  @globalSignalID  
keyref  globalSignalOperationRef  td:globalSignalKey  .//td:GlobalSignalOperation  @globalSignalID  
annotation
documentation 
Shall contain all of the sufficient data for each UUT test to completely describe all input conditions and measurements required.
source
<xs:element name="DetailedTestInformation" type="td:DetailedTestInformation">
  <xs:annotation>
    <xs:documentation>Shall contain all of the sufficient data for each UUT test to completely describe all input conditions and measurements required.</xs:documentation>
  </xs:annotation>
  <xs:key name="stateVariableKey">
    <xs:selector xpath=".//td:StateVariable"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="stateVariableOperationRef" refer="td:stateVariableKey">
    <xs:selector xpath=".//td:Operation"/>
    <xs:field xpath="@stateVariableID"/>
  </xs:keyref>
  <xs:key name="stateVariableValueKey">
    <xs:selector xpath=".//td:StateVariable/td:Values/td:Value"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="stateVariableValueInitialRef" refer="td:stateVariableValueKey">
    <xs:selector xpath=".//td:StateVariable/td:InitialValue"/>
    <xs:field xpath="@valueID"/>
  </xs:keyref>
  <xs:keyref name="stateVariableValuePreConditionRef" refer="td:stateVariableValueKey">
    <xs:selector xpath=".//td:PreCondition/td:StateVariableValue"/>
    <xs:field xpath="@stateVariableValueID"/>
  </xs:keyref>
  <xs:keyref name="stateVariableValuePostConditionRef" refer="td:stateVariableValueKey">
    <xs:selector xpath=".//td:PostCondition/td:StateVariableValue"/>
    <xs:field xpath="@stateVariableValueID"/>
  </xs:keyref>
  <xs:keyref name="stateVariableValueOperationRef" refer="td:stateVariableValueKey">
    <xs:selector xpath=".//td:Operation"/>
    <xs:field xpath="@stateVariableValueID"/>
  </xs:keyref>
  <xs:key name="testGroupKey">
    <xs:selector xpath=".//td:TestGroup"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="testGroupEntryPointRef" refer="td:testGroupKey">
    <xs:selector xpath=".//td:TestGroupEntryPoint"/>
    <xs:field xpath="@testGroupID"/>
  </xs:keyref>
  <xs:keyref name="testGroupCallRef" refer="td:testGroupKey">
    <xs:selector xpath=".//td:Behavior/td:TestGroupCall"/>
    <xs:field xpath="@testGroupID"/>
  </xs:keyref>
  <xs:keyref name="testGroupStepRef" refer="td:testGroupKey">
    <xs:selector xpath=".//td:Step/td:TestGroupReference"/>
    <xs:field xpath="@testGroupID"/>
  </xs:keyref>
  <xs:keyref name="testGroupInitializationRef" refer="td:testGroupKey">
    <xs:selector xpath=".//td:InitializationTestGroup"/>
    <xs:field xpath="@testGroupID"/>
  </xs:keyref>
  <xs:keyref name="testGroupTerminationRef" refer="td:testGroupKey">
    <xs:selector xpath=".//td:TerminationTestGroup"/>
    <xs:field xpath="@testGroupID"/>
  </xs:keyref>
  <xs:key name="testGroupOutcomeKey">
    <xs:selector xpath=".//td:TestGroup/td:Outcomes/td:Outcome"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="testGroupOutcomeRef" refer="td:testGroupOutcomeKey">
    <xs:selector xpath=".//td:Step/td:Results/td:Result/td:TestGroupOutcomeReference"/>
    <xs:field xpath="@testGroupOutcomeID"/>
  </xs:keyref>
  <xs:key name="testGroupParameterKey">
    <xs:selector xpath=".//td:TestGroup/td:ParameterDescriptions/td:ParameterDescription"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="testGroupParameterDatumRef" refer="td:testGroupParameterKey">
    <xs:selector xpath=".//c:Datum"/>
    <xs:field xpath="@testGroupParameterID"/>
  </xs:keyref>
  <xs:keyref name="testGroupParameterValueRef" refer="td:testGroupParameterKey">
    <xs:selector xpath=".//td:ValueToParameter"/>
    <xs:field xpath="@testGroupParameterID"/>
  </xs:keyref>
  <xs:key name="testGroupTestResultKey">
    <xs:selector xpath=".//td:TestGroup/td:TestResultDescriptions/td:TestResultDescription"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="testGroupTestResultTestResultRef" refer="td:testGroupTestResultKey">
    <xs:selector xpath=".//td:Action/td:TestResults/td:TestResult/td:ValueToTestResult"/>
    <xs:field xpath="@testGroupTestResultID"/>
  </xs:keyref>
  <xs:keyref name="testGroupTestResultSessionDatumRef" refer="td:testGroupTestResultKey">
    <xs:selector xpath=".//td:Action/td:SessionData/td:SessionDatum/td:ValueToTestResult"/>
    <xs:field xpath="@testGroupTestResultID"/>
  </xs:keyref>
  <xs:key name="actionKey">
    <xs:selector xpath=".//td:Action"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="actionInitializationRef" refer="td:actionKey">
    <xs:selector xpath=".//td:InitializationAction"/>
    <xs:field xpath="@actionID"/>
  </xs:keyref>
  <xs:keyref name="actionTerminationRef" refer="td:actionKey">
    <xs:selector xpath=".//td:TerminationAction"/>
    <xs:field xpath="@actionID"/>
  </xs:keyref>
  <xs:keyref name="actionStepRef" refer="td:actionKey">
    <xs:selector xpath=".//td:Step/td:ActionReference"/>
    <xs:field xpath="@actionID"/>
  </xs:keyref>
  <xs:keyref name="actionTestGroupRef" refer="td:actionKey">
    <xs:selector xpath=".//td:TestGroup/td:ActionReferences/td:ActionReference"/>
    <xs:field xpath="@actionID"/>
  </xs:keyref>
  <xs:keyref name="actionEntryPointRef" refer="td:actionKey">
    <xs:selector xpath=".//td:ActionEntryPoint"/>
    <xs:field xpath="@actionID"/>
  </xs:keyref>
  <xs:key name="actionOutcomeKey">
    <xs:selector xpath=".//td:Action/td:Outcomes/td:Outcome"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="actionOutcomeResultRef" refer="td:actionOutcomeKey">
    <xs:selector xpath=".//td:Result/td:ActionOutcomeReference"/>
    <xs:field xpath="@actionOutcomeID"/>
  </xs:keyref>
  <xs:keyref name="actionOutcomeOperationRef" refer="td:actionOutcomeKey">
    <xs:selector xpath=".//td:Operation/td:Results/td:Result"/>
    <xs:field xpath="@actionOutcomeID"/>
  </xs:keyref>
  <xs:key name="testResultKey">
    <xs:selector xpath=".//td:Action/td:TestResults/td:TestResult"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="testResultDatumRef" refer="td:testResultKey">
    <xs:selector xpath=".//c:Datum/td:TestResult"/>
    <xs:field xpath="@testResultID"/>
  </xs:keyref>
  <xs:keyref name="testResultOperationRef" refer="td:testResultKey">
    <xs:selector xpath=".//td:Operation/td:ValueToTestResult"/>
    <xs:field xpath="@testResultID"/>
  </xs:keyref>
  <xs:keyref name="resultOutValueResultID" refer="td:testResultKey">
    <xs:selector xpath=".//td:IeeeStd1641/td:IeeeStd1641OutValues/td:ResultOutValue"/>
    <xs:field xpath="@resultID"/>
  </xs:keyref>
  <xs:key name="sessionDatumKey">
    <xs:selector xpath=".//td:Action/td:SessionData/td:SessionDatum"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="sessionDatumDatumRef" refer="td:sessionDatumKey">
    <xs:selector xpath=".//c:Datum/td:SessionDatum"/>
    <xs:field xpath="@sessionDatumID"/>
  </xs:keyref>
  <xs:keyref name="sessionDatumOperationRef" refer="td:sessionDatumKey">
    <xs:selector xpath=".//td:Operation/td:ValueToSessionDatum"/>
    <xs:field xpath="@sessionDatumID"/>
  </xs:keyref>
  <xs:key name="measurementKey">
    <xs:selector xpath=".//td:Operation/td:Measurement"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="measurementRef" refer="td:measurementKey">
    <xs:selector xpath=".//c:Datum"/>
    <xs:field xpath="@measurementID"/>
  </xs:keyref>
  <xs:key name="globalSignalKey">
    <xs:selector xpath=".//td:GlobalSignal/td:Source"/>
    <xs:field xpath="@ID"/>
  </xs:key>
  <xs:keyref name="globalSignalReferenceRef" refer="td:globalSignalKey">
    <xs:selector xpath=".//td:GlobalSignalReference"/>
    <xs:field xpath="@globalSignalID"/>
  </xs:keyref>
  <xs:keyref name="globalSignalOperationRef" refer="td:globalSignalKey">
    <xs:selector xpath=".//td:GlobalSignalOperation"/>
    <xs:field xpath="@globalSignalID"/>
  </xs:keyref>
</xs:element>

element TestDescription/FailureFaultData
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:FaultData
properties
isRef 0
content complex
children Failures FaultData Extension
annotation
documentation 
Shall contain UUT fault data, including faults and failures. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:element name="FailureFaultData" type="td:FaultData" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall contain UUT fault data, including faults and failures. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
</xs:element>

element TestDescription/AutomaticGeneration
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:AutomaticGeneration
properties
isRef 0
content complex
children Tools Extension
annotation
documentation 
Shall identify the Automatic Test Program Generation (ATPG) tools used to generate the test program.
source
<xs:element name="AutomaticGeneration" type="td:AutomaticGeneration" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall identify the Automatic Test Program Generation (ATPG) tools used to generate the test program.</xs:documentation>
  </xs:annotation>
</xs:element>

complexType ActionOutcomeType
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
abstract true
children Description PostConditions Extension
used by
complexTypes Outcome SessionOutcome
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankStringrequired      
documentation 
Unique identifier, enables referencing the action outcome.
qualifier  c:NonBlankString      
documentation 
Outcome qualifier (e.g., High, Low). When used, shall contain an adjective providing additional descriptive data for the ‘value’ attribute defined in derived types. When ‘value’ is “Aborted”, ‘qualifier’ shall provide essential descriptive or explanatory information regarding the reason for the action or test group not completing normally. Refer to B.2.12 for an example using qualifiers.
annotation
documentation 
Abstract base type for describing the outcome of an action (test or session action) or test group. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements.
source
<xs:complexType name="ActionOutcomeType" abstract="true">
  <xs:annotation>
    <xs:documentation>Abstract base type for describing the outcome of an action (test or session action) or test group. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Free-form description of the outcome.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="PostConditions" type="td:PostConditions" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Shall describe all postconditions for the action or test group, or for an individual outcome of that test or test group. Postconditions defined in a child element of Test/Conditions or SessionAction/Condition shall apply to all outcomes of that test or session action. Postconditions defined in a child element of Outcome shall apply only for that particular outcome, overriding the postconditions defined in a child element of Test/Conditions or SessionAction/Condition. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions (i.e., tests or session outcomes) and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Extension" type="c:Extension" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="ID" type="c:NonBlankString" use="required">
    <xs:annotation>
      <xs:documentation>Unique identifier, enables referencing the action outcome.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="qualifier" type="c:NonBlankString">
    <xs:annotation>
      <xs:documentation>Outcome qualifier (e.g., High, Low). When used, shall contain an adjective providing additional descriptive data for the ‘value’ attribute defined in derived types. When ‘value’ is “Aborted”, ‘qualifier’ shall provide essential descriptive or explanatory information regarding the reason for the action or test group not completing normally. Refer to B.2.12 for an example using qualifiers.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>

element ActionOutcomeType/Description
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankString
properties
isRef 0
content simple
facets
minLength 1
whiteSpace replace
annotation
documentation 
Free-form description of the outcome.
source
<xs:element name="Description" type="c:NonBlankString" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Free-form description of the outcome.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionOutcomeType/PostConditions
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:PostConditions
properties
isRef 0
content complex
children PostCondition
annotation
documentation 
Shall describe all postconditions for the action or test group, or for an individual outcome of that test or test group. Postconditions defined in a child element of Test/Conditions or SessionAction/Condition shall apply to all outcomes of that test or session action. Postconditions defined in a child element of Outcome shall apply only for that particular outcome, overriding the postconditions defined in a child element of Test/Conditions or SessionAction/Condition. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions (i.e., tests or session outcomes) and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.
source
<xs:element name="PostConditions" type="td:PostConditions" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describe all postconditions for the action or test group, or for an individual outcome of that test or test group. Postconditions defined in a child element of Test/Conditions or SessionAction/Condition shall apply to all outcomes of that test or session action. Postconditions defined in a child element of Outcome shall apply only for that particular outcome, overriding the postconditions defined in a child element of Test/Conditions or SessionAction/Condition. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions (i.e., tests or session outcomes) and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionOutcomeType/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
Provided to permit schema extensibility.
source
<xs:element name="Extension" type="c:Extension" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
  </xs:annotation>
</xs:element>

complexType ActionResultType
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
children Description ValueDescription ValueToTestResult Extension
used by
elements SessionAction/SessionData/SessionDatum Test/TestResults/TestResult
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankStringrequired      
documentation 
Unique identifier, enables referencing the result.
name  c:NonBlankStringrequired      
documentation 
Name of the action result.
documentRequirementID  c:NonBlankString      
documentation 
Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific.
annotation
documentation 
Abstract base type for describing one result of an action (i.e., test or session action). Note that this type is used as base type for other type definitions. 
source
<xs:complexType name="ActionResultType">
  <xs:annotation>
    <xs:documentation>Abstract base type for describing one result of an action (i.e., test or session action). Note that this type is used as base type for other type definitions. </xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Free-form description of the result.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="ValueDescription">
      <xs:annotation>
        <xs:documentation>Shall describe the data type and the unit of the result. Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants.</xs:documentation>
      </xs:annotation>
      <xs:complexType mixed="false">
        <xs:complexContent mixed="false">
          <xs:extension base="td:ValueDescription"/>
        </xs:complexContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="ValueToTestResult" minOccurs="0">
      <xs:annotation>
        <xs:documentation>When present, this element shall indicate that after action execution the value of the current action result is transferred to a test result of the containing test group. The data type, unit and qualifier of the referenced test result shall be identical to those of the current action result. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:attribute name="testGroupTestResultID" type="c:NonBlankString" use="required">
          <xs:annotation>
            <xs:documentation>ID of the test result the value of the current action result is transferred to.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
    <xs:element name="Extension" type="c:Extension" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="ID" type="c:NonBlankString" use="required">
    <xs:annotation>
      <xs:documentation>Unique identifier, enables referencing the result.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="name" type="c:NonBlankString" use="required">
    <xs:annotation>
      <xs:documentation>Name of the action result.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="documentRequirementID" type="c:NonBlankString">
    <xs:annotation>
      <xs:documentation>Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>

element ActionResultType/Description
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankString
properties
isRef 0
content simple
facets
minLength 1
whiteSpace replace
annotation
documentation 
Free-form description of the result.
source
<xs:element name="Description" type="c:NonBlankString" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Free-form description of the result.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionResultType/ValueDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:ValueDescription
properties
isRef 0
content complex
mixed false
children DatumDescription CollectionDescription IndexedArrayDescription
annotation
documentation 
Shall describe the data type and the unit of the result. Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants.
source
<xs:element name="ValueDescription">
  <xs:annotation>
    <xs:documentation>Shall describe the data type and the unit of the result. Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="false">
    <xs:complexContent mixed="false">
      <xs:extension base="td:ValueDescription"/>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

element ActionResultType/ValueToTestResult
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
testGroupTestResultID  c:NonBlankStringrequired      
documentation 
ID of the test result the value of the current action result is transferred to.
annotation
documentation 
When present, this element shall indicate that after action execution the value of the current action result is transferred to a test result of the containing test group. The data type, unit and qualifier of the referenced test result shall be identical to those of the current action result. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:element name="ValueToTestResult" minOccurs="0">
  <xs:annotation>
    <xs:documentation>When present, this element shall indicate that after action execution the value of the current action result is transferred to a test result of the containing test group. The data type, unit and qualifier of the referenced test result shall be identical to those of the current action result. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="testGroupTestResultID" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>ID of the test result the value of the current action result is transferred to.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionResultType/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
Provided to permit schema extensibility.
source
<xs:element name="Extension" type="c:Extension" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
  </xs:annotation>
</xs:element>

complexType ActionType
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
abstract true
children Description Parameters Behavior LocalSignals Conditions Extension
used by
element DetailedTestInformation/Actions/Action
complexTypes SessionAction Test
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankStringrequired      
documentation 
Unique identifier, enables referencing the action.
name  c:NonBlankStringrequired      
documentation 
Name of the action
classified  xs:boolean      
documentation 
Indicates if the action is classified.
securityClassification  c:NonBlankString      
documentation 
User-defined security classification for the action
customType  c:NonBlankString      
documentation 
Custom action type, used to indicate actions that belong to user-defined categories. The semantics attached to categories are user-specific. For example, actions from the same category may be implemented as a single function or procedure. When this attribute is used to provide a guideline for implementation, implementers may choose to follow or ignore the guideline.
cost  xs:double      
documentation 
Cost of action execution, representing the duration of execution, the financial cost associated with execution, or a value calculated by an objective function. May be used to optimize the order of execution.
documentRequirementID  c:NonBlankString      
documentation 
Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not mandated by this standard and can be application-specific.
annotation
documentation 
Abstract base type for test actions. The following derived types are defined in the schema: Test and SessionAction. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements.
source
<xs:complexType name="ActionType" abstract="true">
  <xs:annotation>
    <xs:documentation>Abstract base type for test actions. The following derived types are defined in the schema: Test and SessionAction. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Free-form description for the action.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="Parameters" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Shall describe the parameters of the action and shall specify their values. Refer to Annex B for examples on describing parameters. Refer to B.2.15 for usage information regarding parameters.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Parameter" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Shall describe one parameter of the action and shall specify its value. Parameters shall be used to represent values that determine the behavior of the action. This includes, for example: the characteristics of stimulus signals, measurement conditions, UUT pins where signals are applied or measured, the limits of parametric sweeps, the indices of UUT channels to be tested, string commands to be sent to the UUT, identification of firmware to be loaded in the UUT, etc. Parameters shall not be used to represent the limits of acceptable UUT operation, as those limits are described using TestResult descendants of complex type Test, which is derived from ActionType.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Free-form description of the parameter.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:choice>
                  <xs:element name="Value" type="c:Value">
                    <xs:annotation>
                      <xs:documentation>Shall specify the value of the parameter. The attributes of this element shall specify the unit (when applicable) and may specify a qualifier. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. The type ConnectionDatum shall be assigned to Datum descendants of this element to specify a connection as the parameter value. The type ValueFromTestGroupParameter shall be assigned to Datum descendants of this element to indicate a parameter value that originates from a Parameter of the containing Test Group. The type ValueFromActionResults shall be assigned to Datum descendants of this element to indicate a parameter value that originates from one or more Test Results of Tests or Session Data of Session Actions from the same Test Group.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="Reference" type="c:Document">
                    <xs:annotation>
                      <xs:documentation>When present, shall indicate that the value will be retrieved at run-time from an external document, instead of being encoded in the test program. This element shall reference the external document.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:choice>
                <xs:element name="ValueToParameter" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>When present, shall indicate that before action execution the value of the current parameter shall be assigned to a parameter of the called test group. The element can be present only when the current parameter belongs to an action whose behavior is "TestGroupCall". The data type, unit and qualifier of the referenced test group parameter shall be identical to those of the current parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
                  </xs:annotation>
                  <xs:complexType>
                    <xs:attribute name="testGroupParameterID" type="c:NonBlankString" use="required">
                      <xs:annotation>
                        <xs:documentation>ID of the test group parameter.</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
                <xs:element name="Extension" type="c:Extension" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="ID" type="c:NonBlankString" use="required">
                <xs:annotation>
                  <xs:documentation>Unique identifier, enables referencing the parameter.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="name" type="c:NonBlankString" use="required">
                <xs:annotation>
                  <xs:documentation>Name of the parameter.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="documentRequirementID" type="c:NonBlankString">
                <xs:annotation>
                  <xs:documentation>Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
      <xs:unique name="parameterNamesUnique2">
        <xs:selector xpath="./td:Parameter"/>
        <xs:field xpath="@name"/>
      </xs:unique>
    </xs:element>
    <xs:element name="Behavior">
      <xs:annotation>
        <xs:documentation>Shall describe the behavior of the action.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:choice>
          <xs:element name="Description" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>The presence of this element shall indicate that behavior is specified using free-form text. The element shall contain the descriptive text. Refer B.2 for an example that contains free-form description of test behavior.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="Operations" type="td:Operations">
            <xs:annotation>
              <xs:documentation>The presence of this element indicates that behavior is specified as a sequence of predefined operations. The operation described by the child elements shall be executed sequentially, in the order in which they appear in the instance document. Refer to B.4 for an example where test behavior is described through operations.</xs:documentation>
            </xs:annotation>
            <xs:unique name="operationIdUnique">
              <xs:selector xpath=".//td:Operations/td:Operation"/>
              <xs:field xpath="@ID"/>
            </xs:unique>
          </xs:element>
          <xs:element name="IeeeStd1641" type="td:IeeeStd1641">
            <xs:annotation>
              <xs:documentation>The presence of this element shall indicate that behavior is specified as a test definition conformant to IEEE Std 1641. Refer to B.3 for an example where test behavior is described through IEEE Std. 1641 signals. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
            </xs:annotation>
            <xs:unique name="signalNameKey">
              <xs:selector xpath=".//*"/>
              <xs:field xpath="@name"/>
            </xs:unique>
            <xs:keyref name="signalNameRef" refer="td:signalNameKey">
              <xs:selector xpath=".//*"/>
              <xs:field xpath="@signalName"/>
            </xs:keyref>
          </xs:element>
          <xs:element name="TestGroupCall">
            <xs:annotation>
              <xs:documentation>The presence of this element shall indicate that the action consists in the execution of a test group. The element shall identify the test group. If the test group has multiple entry points, execution shall start at the primary entry point. When the behavior specified for an action is “test group call”, the outcomes defined for that action shall be identical to those of the referenced test group. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically. Refer to B.4 for an example that contains test group calls.
</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:attribute name="testGroupID" type="c:NonBlankString" use="required">
                <xs:annotation>
                  <xs:documentation>ID of the test group that is executed.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
          <xs:element name="AutomaticGeneration">
            <xs:annotation>
              <xs:documentation>The presence of this element shall indicate that the part of the test program that corresponds to the current action will be generated automatically by an ATPG tool. The child elements shall identify the tool and the data files used for generation.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="DataFiles" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Shall contain the list of all data files processed or generated by the ATPG tool for the current test.</xs:documentation>
                  </xs:annotation>
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="DataFile" type="c:Document" maxOccurs="unbounded">
                        <xs:annotation>
                          <xs:documentation>Shall identify one data file.</xs:documentation>
                        </xs:annotation>
                      </xs:element>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="toolID" type="c:NonBlankString" use="required">
                <xs:annotation>
                  <xs:documentation>ID of the element describing the ATPG tool that generates the test.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
          <xs:element name="Extension" type="c:Extension">
            <xs:annotation>
              <xs:documentation>Provided to permit schema extensibility. Through this element, test behavior may be specified using XML content that conforms to an external XML schema.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:choice>
      </xs:complexType>
    </xs:element>
    <xs:element name="LocalSignals" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Shall identify local signals, shared by multiple operations specified for the current action. Local signals are referenced from operations. Refer to B.4.2 for usage information regarding local signals and to B.4 for an example.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="LocalSignal" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Shall describes one local signal, which may be a source signal, a measurement, or a connection.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:choice>
                <xs:element name="Source">
                  <xs:annotation>
                    <xs:documentation>Shall describe a local source signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationChange, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
                  </xs:annotation>
                  <xs:complexType>
                    <xs:attribute name="ID" type="c:NonBlankString">
                      <xs:annotation>
                        <xs:documentation>Unique identifier, enables referencing the local source signal.</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
                <xs:element name="Sensor">
                  <xs:annotation>
                    <xs:documentation>Shall describe a local sensor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationRead, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
                  </xs:annotation>
                  <xs:complexType>
                    <xs:attribute name="ID" type="c:NonBlankString">
                      <xs:annotation>
                        <xs:documentation>Unique identifier, enables referencing the local sensor signal.</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
                <xs:element name="Monitor">
                  <xs:annotation>
                    <xs:documentation>Shall describe a local monitor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationEnable, OperationDisable, OperationDisconnect, and OperationReset located in the current action. Can also be referenced from Synchronization child elements of any Operation element located in the current action.</xs:documentation>
                  </xs:annotation>
                  <xs:complexType>
                    <xs:attribute name="ID" type="c:NonBlankString">
                      <xs:annotation>
                        <xs:documentation>Unique identifier, enables referencing the local monitor signal.</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
              </xs:choice>
              <xs:attribute name="name" type="c:NonBlankString">
                <xs:annotation>
                  <xs:documentation>Name of the local signal. May be used for documentation purposes.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Conditions" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Shall specify the preconditions and postconditions for the action. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="PreConditions" type="td:PreConditions" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Shall describes all preconditions for the  action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. </xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="PostConditions" type="td:PostConditions" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Extension" type="c:Extension" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="ID" type="c:NonBlankString" use="required">
    <xs:annotation>
      <xs:documentation>Unique identifier, enables referencing the action.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="name" type="c:NonBlankString" use="required">
    <xs:annotation>
      <xs:documentation>Name of the action</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="classified" type="xs:boolean">
    <xs:annotation>
      <xs:documentation>Indicates if the action is classified.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="securityClassification" type="c:NonBlankString">
    <xs:annotation>
      <xs:documentation>User-defined security classification for the action</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="customType" type="c:NonBlankString">
    <xs:annotation>
      <xs:documentation>Custom action type, used to indicate actions that belong to user-defined categories. The semantics attached to categories are user-specific. For example, actions from the same category may be implemented as a single function or procedure. When this attribute is used to provide a guideline for implementation, implementers may choose to follow or ignore the guideline.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="cost" type="xs:double">
    <xs:annotation>
      <xs:documentation>Cost of action execution, representing the duration of execution, the financial cost associated with execution, or a value calculated by an objective function. May be used to optimize the order of execution.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="documentRequirementID" type="c:NonBlankString">
    <xs:annotation>
      <xs:documentation>Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not mandated by this standard and can be application-specific.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>

element ActionType/Description
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankString
properties
isRef 0
content simple
facets
minLength 1
whiteSpace replace
annotation
documentation 
Free-form description for the action.
source
<xs:element name="Description" type="c:NonBlankString" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Free-form description for the action.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Parameters
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children Parameter
identity constraints
  Name  Refer  Selector  Field(s)  
unique  parameterNamesUnique2    ./td:Parameter  @name  
annotation
documentation 
Shall describe the parameters of the action and shall specify their values. Refer to Annex B for examples on describing parameters. Refer to B.2.15 for usage information regarding parameters.
source
<xs:element name="Parameters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describe the parameters of the action and shall specify their values. Refer to Annex B for examples on describing parameters. Refer to B.2.15 for usage information regarding parameters.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Parameter" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Shall describe one parameter of the action and shall specify its value. Parameters shall be used to represent values that determine the behavior of the action. This includes, for example: the characteristics of stimulus signals, measurement conditions, UUT pins where signals are applied or measured, the limits of parametric sweeps, the indices of UUT channels to be tested, string commands to be sent to the UUT, identification of firmware to be loaded in the UUT, etc. Parameters shall not be used to represent the limits of acceptable UUT operation, as those limits are described using TestResult descendants of complex type Test, which is derived from ActionType.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Free-form description of the parameter.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:choice>
              <xs:element name="Value" type="c:Value">
                <xs:annotation>
                  <xs:documentation>Shall specify the value of the parameter. The attributes of this element shall specify the unit (when applicable) and may specify a qualifier. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. The type ConnectionDatum shall be assigned to Datum descendants of this element to specify a connection as the parameter value. The type ValueFromTestGroupParameter shall be assigned to Datum descendants of this element to indicate a parameter value that originates from a Parameter of the containing Test Group. The type ValueFromActionResults shall be assigned to Datum descendants of this element to indicate a parameter value that originates from one or more Test Results of Tests or Session Data of Session Actions from the same Test Group.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="Reference" type="c:Document">
                <xs:annotation>
                  <xs:documentation>When present, shall indicate that the value will be retrieved at run-time from an external document, instead of being encoded in the test program. This element shall reference the external document.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:choice>
            <xs:element name="ValueToParameter" minOccurs="0">
              <xs:annotation>
                <xs:documentation>When present, shall indicate that before action execution the value of the current parameter shall be assigned to a parameter of the called test group. The element can be present only when the current parameter belongs to an action whose behavior is "TestGroupCall". The data type, unit and qualifier of the referenced test group parameter shall be identical to those of the current parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:attribute name="testGroupParameterID" type="c:NonBlankString" use="required">
                  <xs:annotation>
                    <xs:documentation>ID of the test group parameter.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
            <xs:element name="Extension" type="c:Extension" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="ID" type="c:NonBlankString" use="required">
            <xs:annotation>
              <xs:documentation>Unique identifier, enables referencing the parameter.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="name" type="c:NonBlankString" use="required">
            <xs:annotation>
              <xs:documentation>Name of the parameter.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="documentRequirementID" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <xs:unique name="parameterNamesUnique2">
    <xs:selector xpath="./td:Parameter"/>
    <xs:field xpath="@name"/>
  </xs:unique>
</xs:element>

element ActionType/Parameters/Parameter
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children Description Value Reference ValueToParameter Extension
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankStringrequired      
documentation 
Unique identifier, enables referencing the parameter.
name  c:NonBlankStringrequired      
documentation 
Name of the parameter.
documentRequirementID  c:NonBlankString      
documentation 
Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific.
annotation
documentation 
Shall describe one parameter of the action and shall specify its value. Parameters shall be used to represent values that determine the behavior of the action. This includes, for example: the characteristics of stimulus signals, measurement conditions, UUT pins where signals are applied or measured, the limits of parametric sweeps, the indices of UUT channels to be tested, string commands to be sent to the UUT, identification of firmware to be loaded in the UUT, etc. Parameters shall not be used to represent the limits of acceptable UUT operation, as those limits are described using TestResult descendants of complex type Test, which is derived from ActionType.
source
<xs:element name="Parameter" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Shall describe one parameter of the action and shall specify its value. Parameters shall be used to represent values that determine the behavior of the action. This includes, for example: the characteristics of stimulus signals, measurement conditions, UUT pins where signals are applied or measured, the limits of parametric sweeps, the indices of UUT channels to be tested, string commands to be sent to the UUT, identification of firmware to be loaded in the UUT, etc. Parameters shall not be used to represent the limits of acceptable UUT operation, as those limits are described using TestResult descendants of complex type Test, which is derived from ActionType.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Free-form description of the parameter.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:choice>
        <xs:element name="Value" type="c:Value">
          <xs:annotation>
            <xs:documentation>Shall specify the value of the parameter. The attributes of this element shall specify the unit (when applicable) and may specify a qualifier. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. The type ConnectionDatum shall be assigned to Datum descendants of this element to specify a connection as the parameter value. The type ValueFromTestGroupParameter shall be assigned to Datum descendants of this element to indicate a parameter value that originates from a Parameter of the containing Test Group. The type ValueFromActionResults shall be assigned to Datum descendants of this element to indicate a parameter value that originates from one or more Test Results of Tests or Session Data of Session Actions from the same Test Group.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Reference" type="c:Document">
          <xs:annotation>
            <xs:documentation>When present, shall indicate that the value will be retrieved at run-time from an external document, instead of being encoded in the test program. This element shall reference the external document.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:choice>
      <xs:element name="ValueToParameter" minOccurs="0">
        <xs:annotation>
          <xs:documentation>When present, shall indicate that before action execution the value of the current parameter shall be assigned to a parameter of the called test group. The element can be present only when the current parameter belongs to an action whose behavior is "TestGroupCall". The data type, unit and qualifier of the referenced test group parameter shall be identical to those of the current parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="testGroupParameterID" type="c:NonBlankString" use="required">
            <xs:annotation>
              <xs:documentation>ID of the test group parameter.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="Extension" type="c:Extension" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="ID" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>Unique identifier, enables referencing the parameter.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="name" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>Name of the parameter.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="documentRequirementID" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/Parameters/Parameter/Description
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankString
properties
isRef 0
content simple
facets
minLength 1
whiteSpace replace
annotation
documentation 
Free-form description of the parameter.
source
<xs:element name="Description" type="c:NonBlankString" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Free-form description of the parameter.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Parameters/Parameter/Value
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Value
properties
isRef 0
content complex
children Datum Collection IndexedArray
annotation
documentation 
Shall specify the value of the parameter. The attributes of this element shall specify the unit (when applicable) and may specify a qualifier. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. The type ConnectionDatum shall be assigned to Datum descendants of this element to specify a connection as the parameter value. The type ValueFromTestGroupParameter shall be assigned to Datum descendants of this element to indicate a parameter value that originates from a Parameter of the containing Test Group. The type ValueFromActionResults shall be assigned to Datum descendants of this element to indicate a parameter value that originates from one or more Test Results of Tests or Session Data of Session Actions from the same Test Group.
source
<xs:element name="Value" type="c:Value">
  <xs:annotation>
    <xs:documentation>Shall specify the value of the parameter. The attributes of this element shall specify the unit (when applicable) and may specify a qualifier. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. The type ConnectionDatum shall be assigned to Datum descendants of this element to specify a connection as the parameter value. The type ValueFromTestGroupParameter shall be assigned to Datum descendants of this element to indicate a parameter value that originates from a Parameter of the containing Test Group. The type ValueFromActionResults shall be assigned to Datum descendants of this element to indicate a parameter value that originates from one or more Test Results of Tests or Session Data of Session Actions from the same Test Group.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Parameters/Parameter/Reference
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Document
properties
isRef 0
content complex
children URL Text Extension
attributes
Name  Type  Use  Default  Fixed  Annotation
uuid  c:Uuidrequired      
documentation 
The universal unique identifier for the document.
name  c:NonBlankStringrequired      
documentation 
A descriptive or common name for the document
controlNumber  c:NonBlankStringoptional      
documentation 
A unique identifier for the document.
version  c:NonBlankStringoptional      
documentation 
The version identification of the document.
annotation
documentation 
When present, shall indicate that the value will be retrieved at run-time from an external document, instead of being encoded in the test program. This element shall reference the external document.
source
<xs:element name="Reference" type="c:Document">
  <xs:annotation>
    <xs:documentation>When present, shall indicate that the value will be retrieved at run-time from an external document, instead of being encoded in the test program. This element shall reference the external document.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Parameters/Parameter/ValueToParameter
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
testGroupParameterID  c:NonBlankStringrequired      
documentation 
ID of the test group parameter.
annotation
documentation 
When present, shall indicate that before action execution the value of the current parameter shall be assigned to a parameter of the called test group. The element can be present only when the current parameter belongs to an action whose behavior is "TestGroupCall". The data type, unit and qualifier of the referenced test group parameter shall be identical to those of the current parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:element name="ValueToParameter" minOccurs="0">
  <xs:annotation>
    <xs:documentation>When present, shall indicate that before action execution the value of the current parameter shall be assigned to a parameter of the called test group. The element can be present only when the current parameter belongs to an action whose behavior is "TestGroupCall". The data type, unit and qualifier of the referenced test group parameter shall be identical to those of the current parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="testGroupParameterID" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>ID of the test group parameter.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/Parameters/Parameter/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
Provided to permit schema extensibility.
source
<xs:element name="Extension" type="c:Extension" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Behavior
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children Description Operations IeeeStd1641 TestGroupCall AutomaticGeneration Extension
annotation
documentation 
Shall describe the behavior of the action.
source
<xs:element name="Behavior">
  <xs:annotation>
    <xs:documentation>Shall describe the behavior of the action.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="Description" type="c:NonBlankString">
        <xs:annotation>
          <xs:documentation>The presence of this element shall indicate that behavior is specified using free-form text. The element shall contain the descriptive text. Refer B.2 for an example that contains free-form description of test behavior.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="Operations" type="td:Operations">
        <xs:annotation>
          <xs:documentation>The presence of this element indicates that behavior is specified as a sequence of predefined operations. The operation described by the child elements shall be executed sequentially, in the order in which they appear in the instance document. Refer to B.4 for an example where test behavior is described through operations.</xs:documentation>
        </xs:annotation>
        <xs:unique name="operationIdUnique">
          <xs:selector xpath=".//td:Operations/td:Operation"/>
          <xs:field xpath="@ID"/>
        </xs:unique>
      </xs:element>
      <xs:element name="IeeeStd1641" type="td:IeeeStd1641">
        <xs:annotation>
          <xs:documentation>The presence of this element shall indicate that behavior is specified as a test definition conformant to IEEE Std 1641. Refer to B.3 for an example where test behavior is described through IEEE Std. 1641 signals. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
        </xs:annotation>
        <xs:unique name="signalNameKey">
          <xs:selector xpath=".//*"/>
          <xs:field xpath="@name"/>
        </xs:unique>
        <xs:keyref name="signalNameRef" refer="td:signalNameKey">
          <xs:selector xpath=".//*"/>
          <xs:field xpath="@signalName"/>
        </xs:keyref>
      </xs:element>
      <xs:element name="TestGroupCall">
        <xs:annotation>
          <xs:documentation>The presence of this element shall indicate that the action consists in the execution of a test group. The element shall identify the test group. If the test group has multiple entry points, execution shall start at the primary entry point. When the behavior specified for an action is “test group call”, the outcomes defined for that action shall be identical to those of the referenced test group. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically. Refer to B.4 for an example that contains test group calls.
</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="testGroupID" type="c:NonBlankString" use="required">
            <xs:annotation>
              <xs:documentation>ID of the test group that is executed.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="AutomaticGeneration">
        <xs:annotation>
          <xs:documentation>The presence of this element shall indicate that the part of the test program that corresponds to the current action will be generated automatically by an ATPG tool. The child elements shall identify the tool and the data files used for generation.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="DataFiles" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Shall contain the list of all data files processed or generated by the ATPG tool for the current test.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="DataFile" type="c:Document" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:documentation>Shall identify one data file.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="toolID" type="c:NonBlankString" use="required">
            <xs:annotation>
              <xs:documentation>ID of the element describing the ATPG tool that generates the test.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="Extension" type="c:Extension">
        <xs:annotation>
          <xs:documentation>Provided to permit schema extensibility. Through this element, test behavior may be specified using XML content that conforms to an external XML schema.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>

element ActionType/Behavior/Description
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankString
properties
isRef 0
content simple
facets
minLength 1
whiteSpace replace
annotation
documentation 
The presence of this element shall indicate that behavior is specified using free-form text. The element shall contain the descriptive text. Refer B.2 for an example that contains free-form description of test behavior.
source
<xs:element name="Description" type="c:NonBlankString">
  <xs:annotation>
    <xs:documentation>The presence of this element shall indicate that behavior is specified using free-form text. The element shall contain the descriptive text. Refer B.2 for an example that contains free-form description of test behavior.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Behavior/Operations
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:Operations
properties
isRef 0
content complex
children Operation
identity constraints
  Name  Refer  Selector  Field(s)  
unique  operationIdUnique    .//td:Operations/td:Operation  @ID  
annotation
documentation 
The presence of this element indicates that behavior is specified as a sequence of predefined operations. The operation described by the child elements shall be executed sequentially, in the order in which they appear in the instance document. Refer to B.4 for an example where test behavior is described through operations.
source
<xs:element name="Operations" type="td:Operations">
  <xs:annotation>
    <xs:documentation>The presence of this element indicates that behavior is specified as a sequence of predefined operations. The operation described by the child elements shall be executed sequentially, in the order in which they appear in the instance document. Refer to B.4 for an example where test behavior is described through operations.</xs:documentation>
  </xs:annotation>
  <xs:unique name="operationIdUnique">
    <xs:selector xpath=".//td:Operations/td:Operation"/>
    <xs:field xpath="@ID"/>
  </xs:unique>
</xs:element>

element ActionType/Behavior/IeeeStd1641
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:IeeeStd1641
properties
isRef 0
content complex
children InValues OutValues PortValues Extension GlobalSignalOperations
identity constraints
  Name  Refer  Selector  Field(s)  
unique  signalNameKey    .//*  @name  
keyref  signalNameRef  td:signalNameKey  .//*  @signalName  
annotation
documentation 
The presence of this element shall indicate that behavior is specified as a test definition conformant to IEEE Std 1641. Refer to B.3 for an example where test behavior is described through IEEE Std. 1641 signals. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:element name="IeeeStd1641" type="td:IeeeStd1641">
  <xs:annotation>
    <xs:documentation>The presence of this element shall indicate that behavior is specified as a test definition conformant to IEEE Std 1641. Refer to B.3 for an example where test behavior is described through IEEE Std. 1641 signals. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
  <xs:unique name="signalNameKey">
    <xs:selector xpath=".//*"/>
    <xs:field xpath="@name"/>
  </xs:unique>
  <xs:keyref name="signalNameRef" refer="td:signalNameKey">
    <xs:selector xpath=".//*"/>
    <xs:field xpath="@signalName"/>
  </xs:keyref>
</xs:element>

element ActionType/Behavior/TestGroupCall
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
testGroupID  c:NonBlankStringrequired      
documentation 
ID of the test group that is executed.
annotation
documentation 
The presence of this element shall indicate that the action consists in the execution of a test group. The element shall identify the test group. If the test group has multiple entry points, execution shall start at the primary entry point. When the behavior specified for an action is “test group call”, the outcomes defined for that action shall be identical to those of the referenced test group. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically. Refer to B.4 for an example that contains test group calls.
source
<xs:element name="TestGroupCall">
  <xs:annotation>
    <xs:documentation>The presence of this element shall indicate that the action consists in the execution of a test group. The element shall identify the test group. If the test group has multiple entry points, execution shall start at the primary entry point. When the behavior specified for an action is “test group call”, the outcomes defined for that action shall be identical to those of the referenced test group. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically. Refer to B.4 for an example that contains test group calls.
</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="testGroupID" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>ID of the test group that is executed.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/Behavior/AutomaticGeneration
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children DataFiles
attributes
Name  Type  Use  Default  Fixed  Annotation
toolID  c:NonBlankStringrequired      
documentation 
ID of the element describing the ATPG tool that generates the test.
annotation
documentation 
The presence of this element shall indicate that the part of the test program that corresponds to the current action will be generated automatically by an ATPG tool. The child elements shall identify the tool and the data files used for generation.
source
<xs:element name="AutomaticGeneration">
  <xs:annotation>
    <xs:documentation>The presence of this element shall indicate that the part of the test program that corresponds to the current action will be generated automatically by an ATPG tool. The child elements shall identify the tool and the data files used for generation.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="DataFiles" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall contain the list of all data files processed or generated by the ATPG tool for the current test.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="DataFile" type="c:Document" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>Shall identify one data file.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="toolID" type="c:NonBlankString" use="required">
      <xs:annotation>
        <xs:documentation>ID of the element describing the ATPG tool that generates the test.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/Behavior/AutomaticGeneration/DataFiles
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children DataFile
annotation
documentation 
Shall contain the list of all data files processed or generated by the ATPG tool for the current test.
source
<xs:element name="DataFiles" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall contain the list of all data files processed or generated by the ATPG tool for the current test.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="DataFile" type="c:Document" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Shall identify one data file.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element ActionType/Behavior/AutomaticGeneration/DataFiles/DataFile
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Document
properties
isRef 0
content complex
children URL Text Extension
attributes
Name  Type  Use  Default  Fixed  Annotation
uuid  c:Uuidrequired      
documentation 
The universal unique identifier for the document.
name  c:NonBlankStringrequired      
documentation 
A descriptive or common name for the document
controlNumber  c:NonBlankStringoptional      
documentation 
A unique identifier for the document.
version  c:NonBlankStringoptional      
documentation 
The version identification of the document.
annotation
documentation 
Shall identify one data file.
source
<xs:element name="DataFile" type="c:Document" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Shall identify one data file.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Behavior/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
Provided to permit schema extensibility. Through this element, test behavior may be specified using XML content that conforms to an external XML schema.
source
<xs:element name="Extension" type="c:Extension">
  <xs:annotation>
    <xs:documentation>Provided to permit schema extensibility. Through this element, test behavior may be specified using XML content that conforms to an external XML schema.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/LocalSignals
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children LocalSignal
annotation
documentation 
Shall identify local signals, shared by multiple operations specified for the current action. Local signals are referenced from operations. Refer to B.4.2 for usage information regarding local signals and to B.4 for an example.
source
<xs:element name="LocalSignals" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall identify local signals, shared by multiple operations specified for the current action. Local signals are referenced from operations. Refer to B.4.2 for usage information regarding local signals and to B.4 for an example.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="LocalSignal" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Shall describes one local signal, which may be a source signal, a measurement, or a connection.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:choice>
            <xs:element name="Source">
              <xs:annotation>
                <xs:documentation>Shall describe a local source signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationChange, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:attribute name="ID" type="c:NonBlankString">
                  <xs:annotation>
                    <xs:documentation>Unique identifier, enables referencing the local source signal.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
            <xs:element name="Sensor">
              <xs:annotation>
                <xs:documentation>Shall describe a local sensor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationRead, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:attribute name="ID" type="c:NonBlankString">
                  <xs:annotation>
                    <xs:documentation>Unique identifier, enables referencing the local sensor signal.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
            <xs:element name="Monitor">
              <xs:annotation>
                <xs:documentation>Shall describe a local monitor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationEnable, OperationDisable, OperationDisconnect, and OperationReset located in the current action. Can also be referenced from Synchronization child elements of any Operation element located in the current action.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:attribute name="ID" type="c:NonBlankString">
                  <xs:annotation>
                    <xs:documentation>Unique identifier, enables referencing the local monitor signal.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:choice>
          <xs:attribute name="name" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>Name of the local signal. May be used for documentation purposes.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element ActionType/LocalSignals/LocalSignal
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children Source Sensor Monitor
attributes
Name  Type  Use  Default  Fixed  Annotation
name  c:NonBlankString      
documentation 
Name of the local signal. May be used for documentation purposes.
annotation
documentation 
Shall describes one local signal, which may be a source signal, a measurement, or a connection.
source
<xs:element name="LocalSignal" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Shall describes one local signal, which may be a source signal, a measurement, or a connection.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="Source">
        <xs:annotation>
          <xs:documentation>Shall describe a local source signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationChange, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="ID" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>Unique identifier, enables referencing the local source signal.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="Sensor">
        <xs:annotation>
          <xs:documentation>Shall describe a local sensor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationRead, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="ID" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>Unique identifier, enables referencing the local sensor signal.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="Monitor">
        <xs:annotation>
          <xs:documentation>Shall describe a local monitor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationEnable, OperationDisable, OperationDisconnect, and OperationReset located in the current action. Can also be referenced from Synchronization child elements of any Operation element located in the current action.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="ID" type="c:NonBlankString">
            <xs:annotation>
              <xs:documentation>Unique identifier, enables referencing the local monitor signal.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:choice>
    <xs:attribute name="name" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Name of the local signal. May be used for documentation purposes.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/LocalSignals/LocalSignal/Source
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankString      
documentation 
Unique identifier, enables referencing the local source signal.
annotation
documentation 
Shall describe a local source signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationChange, OperationDisconnect, and OperationReset located in the current action.
source
<xs:element name="Source">
  <xs:annotation>
    <xs:documentation>Shall describe a local source signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationChange, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="ID" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Unique identifier, enables referencing the local source signal.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/LocalSignals/LocalSignal/Sensor
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankString      
documentation 
Unique identifier, enables referencing the local sensor signal.
annotation
documentation 
Shall describe a local sensor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationRead, OperationDisconnect, and OperationReset located in the current action.
source
<xs:element name="Sensor">
  <xs:annotation>
    <xs:documentation>Shall describe a local sensor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationRead, OperationDisconnect, and OperationReset located in the current action.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="ID" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Unique identifier, enables referencing the local sensor signal.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/LocalSignals/LocalSignal/Monitor
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankString      
documentation 
Unique identifier, enables referencing the local monitor signal.
annotation
documentation 
Shall describe a local monitor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationEnable, OperationDisable, OperationDisconnect, and OperationReset located in the current action. Can also be referenced from Synchronization child elements of any Operation element located in the current action.
source
<xs:element name="Monitor">
  <xs:annotation>
    <xs:documentation>Shall describe a local monitor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationEnable, OperationDisable, OperationDisconnect, and OperationReset located in the current action. Can also be referenced from Synchronization child elements of any Operation element located in the current action.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="ID" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Unique identifier, enables referencing the local monitor signal.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element ActionType/Conditions
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children PreConditions PostConditions
annotation
documentation 
Shall specify the preconditions and postconditions for the action. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:element name="Conditions" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall specify the preconditions and postconditions for the action. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="PreConditions" type="td:PreConditions" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall describes all preconditions for the  action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="PostConditions" type="td:PostConditions" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element ActionType/Conditions/PreConditions
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:PreConditions
properties
isRef 0
content complex
children PreCondition Composition
annotation
documentation 
Shall describes all preconditions for the  action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. 
source
<xs:element name="PreConditions" type="td:PreConditions" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describes all preconditions for the  action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. </xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Conditions/PostConditions
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type td:PostConditions
properties
isRef 0
content complex
children PostCondition
annotation
documentation 
Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.
source
<xs:element name="PostConditions" type="td:PostConditions" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action.  Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action.</xs:documentation>
  </xs:annotation>
</xs:element>

element ActionType/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
Provided to permit schema extensibility.
source
<xs:element name="Extension" type="c:Extension" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
  </xs:annotation>
</xs:element>

complexType AutomaticGeneration
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
children Tools Extension
used by
element TestDescription/AutomaticGeneration
annotation
documentation 
Shall define the Automatic Test Program Generator (ATPG) tools that may be used to generate the test program or parts of the test program. Includes UUT simulators, fault simulators, test pattern generators, translators, post-processors, etc.
source
<xs:complexType name="AutomaticGeneration">
  <xs:annotation>
    <xs:documentation>Shall define the Automatic Test Program Generator (ATPG) tools that may be used to generate the test program or parts of the test program. Includes UUT simulators, fault simulators, test pattern generators, translators, post-processors, etc.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="Tools">
      <xs:annotation>
        <xs:documentation>Shall contain the list of ATPG tools.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="Tool" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Shall describe one ATPG tool.</xs:documentation>
            </xs:annotation>
            <xs:complexType mixed="false">
              <xs:complexContent mixed="false">
                <xs:extension base="c:SoftwareInstance">
                  <xs:sequence>
                    <xs:element name="DataFormat" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>Shall describe the format of data processed by the ATPG tool (e.g., IEEE Std 1445 DTIF).</xs:documentation>
                      </xs:annotation>
                      <xs:complexType>
                        <xs:sequence>
                          <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
                            <xs:annotation>
                              <xs:documentation>Free-form description of the format.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="ComplianceDocument" type="c:Document" minOccurs="0" maxOccurs="unbounded">
                            <xs:annotation>
                              <xs:documentation> References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF).</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                        </xs:sequence>
                        <xs:attribute name="name" type="c:NonBlankString">
                          <xs:annotation>
                            <xs:documentation>Name of the format.</xs:documentation>
                          </xs:annotation>
                        </xs:attribute>
                      </xs:complexType>
                    </xs:element>
                    <xs:element name="Extension" type="c:Extension" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                  </xs:sequence>
                  <xs:attribute name="ID" type="c:NonBlankString" use="required">
                    <xs:annotation>
                      <xs:documentation>Unique identifier, enables referencing the ATPG tool.</xs:documentation>
                    </xs:annotation>
                  </xs:attribute>
                  <xs:attribute name="type" type="c:NonBlankString" use="required">
                    <xs:annotation>
                      <xs:documentation>Tool type (e.g., pattern generator)</xs:documentation>
                    </xs:annotation>
                  </xs:attribute>
                  <xs:attribute name="name" type="c:NonBlankString">
                    <xs:annotation>
                      <xs:documentation>Optional tool name.</xs:documentation>
                    </xs:annotation>
                  </xs:attribute>
                </xs:extension>
              </xs:complexContent>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="Extension" type="c:Extension" minOccurs="0">
      <xs:annotation>
        <xs:documentation>User-defined ATPG data.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>

element AutomaticGeneration/Tools
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children Tool
annotation
documentation 
Shall contain the list of ATPG tools.
source
<xs:element name="Tools">
  <xs:annotation>
    <xs:documentation>Shall contain the list of ATPG tools.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Tool" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Shall describe one ATPG tool.</xs:documentation>
        </xs:annotation>
        <xs:complexType mixed="false">
          <xs:complexContent mixed="false">
            <xs:extension base="c:SoftwareInstance">
              <xs:sequence>
                <xs:element name="DataFormat" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Shall describe the format of data processed by the ATPG tool (e.g., IEEE Std 1445 DTIF).</xs:documentation>
                  </xs:annotation>
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
                        <xs:annotation>
                          <xs:documentation>Free-form description of the format.</xs:documentation>
                        </xs:annotation>
                      </xs:element>
                      <xs:element name="ComplianceDocument" type="c:Document" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                          <xs:documentation> References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF).</xs:documentation>
                        </xs:annotation>
                      </xs:element>
                    </xs:sequence>
                    <xs:attribute name="name" type="c:NonBlankString">
                      <xs:annotation>
                        <xs:documentation>Name of the format.</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:complexType>
                </xs:element>
                <xs:element name="Extension" type="c:Extension" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="ID" type="c:NonBlankString" use="required">
                <xs:annotation>
                  <xs:documentation>Unique identifier, enables referencing the ATPG tool.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="type" type="c:NonBlankString" use="required">
                <xs:annotation>
                  <xs:documentation>Tool type (e.g., pattern generator)</xs:documentation>
                </xs:annotation>
              </xs:attribute>
              <xs:attribute name="name" type="c:NonBlankString">
                <xs:annotation>
                  <xs:documentation>Optional tool name.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:complexContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>

element AutomaticGeneration/Tools/Tool
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of c:SoftwareInstance
properties
isRef 0
content complex
mixed false
children DescriptionDocumentReference Definition SerialNumber ReleaseDate DataFormat Extension
attributes
Name  Type  Use  Default  Fixed  Annotation
ID  c:NonBlankStringrequired      
documentation 
Unique identifier, enables referencing the ATPG tool.
type  c:NonBlankStringrequired      
documentation 
Tool type (e.g., pattern generator)
name  c:NonBlankString      
documentation 
Optional tool name.
annotation
documentation 
Shall describe one ATPG tool.
source
<xs:element name="Tool" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Shall describe one ATPG tool.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="false">
    <xs:complexContent mixed="false">
      <xs:extension base="c:SoftwareInstance">
        <xs:sequence>
          <xs:element name="DataFormat" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Shall describe the format of data processed by the ATPG tool (e.g., IEEE Std 1445 DTIF).</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Free-form description of the format.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="ComplianceDocument" type="c:Document" minOccurs="0" maxOccurs="unbounded">
                  <xs:annotation>
                    <xs:documentation> References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF).</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="name" type="c:NonBlankString">
                <xs:annotation>
                  <xs:documentation>Name of the format.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:complexType>
          </xs:element>
          <xs:element name="Extension" type="c:Extension" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
        <xs:attribute name="ID" type="c:NonBlankString" use="required">
          <xs:annotation>
            <xs:documentation>Unique identifier, enables referencing the ATPG tool.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="type" type="c:NonBlankString" use="required">
          <xs:annotation>
            <xs:documentation>Tool type (e.g., pattern generator)</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="name" type="c:NonBlankString">
          <xs:annotation>
            <xs:documentation>Optional tool name.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

element AutomaticGeneration/Tools/Tool/DataFormat
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
properties
isRef 0
content complex
children Description ComplianceDocument
attributes
Name  Type  Use  Default  Fixed  Annotation
name  c:NonBlankString      
documentation 
Name of the format.
annotation
documentation 
Shall describe the format of data processed by the ATPG tool (e.g., IEEE Std 1445 DTIF).
source
<xs:element name="DataFormat" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Shall describe the format of data processed by the ATPG tool (e.g., IEEE Std 1445 DTIF).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Description" type="c:NonBlankString" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Free-form description of the format.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ComplianceDocument" type="c:Document" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation> References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="name" type="c:NonBlankString">
      <xs:annotation>
        <xs:documentation>Name of the format.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>

element AutomaticGeneration/Tools/Tool/DataFormat/Description
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:NonBlankString
properties
isRef 0
content simple
facets
minLength 1
whiteSpace replace
annotation
documentation 
Free-form description of the format.
source
<xs:element name="Description" type="c:NonBlankString" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Free-form description of the format.</xs:documentation>
  </xs:annotation>
</xs:element>

element AutomaticGeneration/Tools/Tool/DataFormat/ComplianceDocument
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Document
properties
isRef 0
content complex
children URL Text Extension
attributes
Name  Type  Use  Default  Fixed  Annotation
uuid  c:Uuidrequired      
documentation 
The universal unique identifier for the document.
name  c:NonBlankStringrequired      
documentation 
A descriptive or common name for the document
controlNumber  c:NonBlankStringoptional      
documentation 
A unique identifier for the document.
version  c:NonBlankStringoptional      
documentation 
The version identification of the document.
annotation
documentation 
 References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF).
source
<xs:element name="ComplianceDocument" type="c:Document" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation> References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF).</xs:documentation>
  </xs:annotation>
</xs:element>

element AutomaticGeneration/Tools/Tool/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
Provided to permit schema extensibility.
source
<xs:element name="Extension" type="c:Extension" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Provided to permit schema extensibility.</xs:documentation>
  </xs:annotation>
</xs:element>

element AutomaticGeneration/Extension
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:Extension
properties
isRef 0
content complex
annotation
documentation 
User-defined ATPG data.
source
<xs:element name="Extension" type="c:Extension" minOccurs="0">
  <xs:annotation>
    <xs:documentation>User-defined ATPG data.</xs:documentation>
  </xs:annotation>
</xs:element>

complexType binaryArrayDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:IndexedArrayDescriptionType
properties
base td:IndexedArrayDescriptionType
mixed false
children Resolution ErrorLimits Range Confidence DefaultElementValue NominalElementValue
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
dimensions  c:ArrayIndexor      
documentation 
Specifies the array bounds for each dimension. Implicitly specifies the number of dimensions.
annotation
documentation 
Describes an array of binary values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified.
source
<xs:complexType name="binaryArrayDescription" mixed="false">
  <xs:annotation>
    <xs:documentation>Describes an array of binary values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified.</xs:documentation>
  </xs:annotation>
  <xs:complexContent mixed="false">
    <xs:extension base="td:IndexedArrayDescriptionType">
      <xs:sequence>
        <xs:element name="DefaultElementValue" type="c:binary" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="NominalElementValue" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>The value of an array element, for the nominal array value.</xs:documentation>
          </xs:annotation>
          <xs:complexType mixed="false">
            <xs:complexContent mixed="false">
              <xs:extension base="c:binary">
                <xs:attribute name="position" type="c:ArrayIndexor" use="required">
                  <xs:annotation>
                    <xs:documentation>Index of the element.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:extension>
            </xs:complexContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

element binaryArrayDescription/DefaultElementValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:binary
properties
isRef 0
content complex
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
value  required      
documentation 
A finite-length sequence of characters 0 and 1.
annotation
documentation 
Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.
source
<xs:element name="DefaultElementValue" type="c:binary" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.</xs:documentation>
  </xs:annotation>
</xs:element>

element binaryArrayDescription/NominalElementValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of c:binary
properties
isRef 0
content complex
mixed false
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
value  required      
documentation 
A finite-length sequence of characters 0 and 1.
position  c:ArrayIndexorrequired      
documentation 
Index of the element.
annotation
documentation 
The value of an array element, for the nominal array value.
source
<xs:element name="NominalElementValue" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The value of an array element, for the nominal array value.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="false">
    <xs:complexContent mixed="false">
      <xs:extension base="c:binary">
        <xs:attribute name="position" type="c:ArrayIndexor" use="required">
          <xs:annotation>
            <xs:documentation>Index of the element.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

complexType binaryDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:DatumDescriptionType
properties
base td:DatumDescriptionType
mixed false
children Resolution ErrorLimits Range Confidence NominalValue
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
annotation
documentation 
Describes a binary value. Where applicable, can be assigned to elements of type DatumDescriptionType.
source
<xs:complexType name="binaryDescription" mixed="false">
  <xs:annotation>
    <xs:documentation>Describes a binary value. Where applicable, can be assigned to elements of type DatumDescriptionType.</xs:documentation>
  </xs:annotation>
  <xs:complexContent mixed="false">
    <xs:extension base="td:DatumDescriptionType">
      <xs:sequence>
        <xs:element name="NominalValue" type="c:binary" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Nominal value. </xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

element binaryDescription/NominalValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:binary
properties
isRef 0
content complex
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
value  required      
documentation 
A finite-length sequence of characters 0 and 1.
annotation
documentation 
Nominal value. 
source
<xs:element name="NominalValue" type="c:binary" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Nominal value. </xs:documentation>
  </xs:annotation>
</xs:element>

complexType booleanArrayDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:IndexedArrayDescriptionType
properties
base td:IndexedArrayDescriptionType
mixed false
children Resolution ErrorLimits Range Confidence DefaultElementValue NominalElementValue
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
dimensions  c:ArrayIndexor      
documentation 
Specifies the array bounds for each dimension. Implicitly specifies the number of dimensions.
annotation
documentation 
Describes an array of boolean values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified.
source
<xs:complexType name="booleanArrayDescription" mixed="false">
  <xs:annotation>
    <xs:documentation>Describes an array of boolean values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified.</xs:documentation>
  </xs:annotation>
  <xs:complexContent mixed="false">
    <xs:extension base="td:IndexedArrayDescriptionType">
      <xs:sequence>
        <xs:element name="DefaultElementValue" type="c:boolean" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="NominalElementValue" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>The value of an array element, for the nominal array value.</xs:documentation>
          </xs:annotation>
          <xs:complexType mixed="false">
            <xs:complexContent mixed="false">
              <xs:extension base="c:boolean">
                <xs:attribute name="position" type="c:ArrayIndexor" use="required">
                  <xs:annotation>
                    <xs:documentation>Index of the element.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:extension>
            </xs:complexContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

element booleanArrayDescription/DefaultElementValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:boolean
properties
isRef 0
content complex
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
value  xs:booleanrequired      
documentation 
A finite-length sequence of characters 0 and 1.
annotation
documentation 
Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.
source
<xs:element name="DefaultElementValue" type="c:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.</xs:documentation>
  </xs:annotation>
</xs:element>

element booleanArrayDescription/NominalElementValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of c:boolean
properties
isRef 0
content complex
mixed false
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
value  xs:booleanrequired      
documentation 
A finite-length sequence of characters 0 and 1.
position  c:ArrayIndexorrequired      
documentation 
Index of the element.
annotation
documentation 
The value of an array element, for the nominal array value.
source
<xs:element name="NominalElementValue" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The value of an array element, for the nominal array value.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="false">
    <xs:complexContent mixed="false">
      <xs:extension base="c:boolean">
        <xs:attribute name="position" type="c:ArrayIndexor" use="required">
          <xs:annotation>
            <xs:documentation>Index of the element.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

complexType booleanDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:DatumDescriptionType
properties
base td:DatumDescriptionType
mixed false
children Resolution ErrorLimits Range Confidence NominalValue
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
annotation
documentation 
Describes a boolean value. Where applicable, can be assigned to elements of type DatumDescriptionType.
source
<xs:complexType name="booleanDescription" mixed="false">
  <xs:annotation>
    <xs:documentation>Describes a boolean value. Where applicable, can be assigned to elements of type DatumDescriptionType.</xs:documentation>
  </xs:annotation>
  <xs:complexContent mixed="false">
    <xs:extension base="td:DatumDescriptionType">
      <xs:sequence>
        <xs:element name="NominalValue" type="c:boolean" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Nominal value.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

element booleanDescription/NominalValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:boolean
properties
isRef 0
content complex
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
value  xs:booleanrequired      
documentation 
A finite-length sequence of characters 0 and 1.
annotation
documentation 
Nominal value.
source
<xs:element name="NominalValue" type="c:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Nominal value.</xs:documentation>
  </xs:annotation>
</xs:element>

complexType CollectionDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
children Resolution ErrorLimits Range Confidence ItemDescription
used by
element ValueDescription/CollectionDescription
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
annotation
documentation 
Describes a value that consists of a set of heterogeneous data items. Attributes standardUnit and nonStandardUnit shall be alternative. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.
source
<xs:complexType name="CollectionDescription">
  <xs:annotation>
    <xs:documentation>Describes a value that consists of a set of heterogeneous data items. Attributes standardUnit and nonStandardUnit shall be alternative. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:group ref="c:DatumQuality"/>
    <xs:element name="ItemDescription" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Describes one data item.</xs:documentation>
      </xs:annotation>
      <xs:complexType mixed="false">
        <xs:complexContent mixed="false">
          <xs:extension base="td:ValueDescription">
            <xs:attribute name="name" type="c:NonBlankString">
              <xs:annotation>
                <xs:documentation>Name of the data item.</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:extension>
        </xs:complexContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="c:UnitAttributes">
    <xs:annotation>
      <xs:documentation>Default unit, applies to data items for which a unit is not explicitly defined.</xs:documentation>
    </xs:annotation>
  </xs:attributeGroup>
</xs:complexType>

element CollectionDescription/ItemDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:ValueDescription
properties
isRef 0
content complex
mixed false
children DatumDescription CollectionDescription IndexedArrayDescription
attributes
Name  Type  Use  Default  Fixed  Annotation
name  c:NonBlankString      
documentation 
Name of the data item.
annotation
documentation 
Describes one data item.
source
<xs:element name="ItemDescription" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Describes one data item.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="false">
    <xs:complexContent mixed="false">
      <xs:extension base="td:ValueDescription">
        <xs:attribute name="name" type="c:NonBlankString">
          <xs:annotation>
            <xs:documentation>Name of the data item.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

complexType complexArrayDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:IndexedArrayDescriptionType
properties
base td:IndexedArrayDescriptionType
mixed false
children Resolution ErrorLimits Range Confidence DefaultElementValue NominalElementValue
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
dimensions  c:ArrayIndexor      
documentation 
Specifies the array bounds for each dimension. Implicitly specifies the number of dimensions.
annotation
documentation 
Describes an array of complex numeric values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified.
source
<xs:complexType name="complexArrayDescription" mixed="false">
  <xs:annotation>
    <xs:documentation>Describes an array of complex numeric values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified.</xs:documentation>
  </xs:annotation>
  <xs:complexContent mixed="false">
    <xs:extension base="td:IndexedArrayDescriptionType">
      <xs:sequence>
        <xs:element name="DefaultElementValue" type="c:complex" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="NominalElementValue" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>The value of an array element, for the nominal array value.</xs:documentation>
          </xs:annotation>
          <xs:complexType mixed="false">
            <xs:complexContent mixed="false">
              <xs:extension base="c:complex">
                <xs:attribute name="position" type="c:ArrayIndexor" use="required">
                  <xs:annotation>
                    <xs:documentation>Index of the element.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:extension>
            </xs:complexContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

element complexArrayDescription/DefaultElementValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type c:complex
properties
isRef 0
content complex
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
real  xs:doublerequired      
documentation 
The real part of the complex value.
imaginary  xs:doublerequired      
documentation 
The imaginary part of the complex value.
annotation
documentation 
Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.
source
<xs:element name="DefaultElementValue" type="c:complex" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements.</xs:documentation>
  </xs:annotation>
</xs:element>

element complexArrayDescription/NominalElementValue
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of c:complex
properties
isRef 0
content complex
mixed false
children Resolution ErrorLimits Range Confidence
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional      
nonStandardUnit  c:NonBlankStringoptional      
unitQualifier  c:NonBlankStringoptional      
real  xs:doublerequired      
documentation 
The real part of the complex value.
imaginary  xs:doublerequired      
documentation 
The imaginary part of the complex value.
position  c:ArrayIndexorrequired      
documentation 
Index of the element.
annotation
documentation 
The value of an array element, for the nominal array value.
source
<xs:element name="NominalElementValue" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The value of an array element, for the nominal array value.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="false">
    <xs:complexContent mixed="false">
      <xs:extension base="c:complex">
        <xs:attribute name="position" type="c:ArrayIndexor" use="required">
          <xs:annotation>
            <xs:documentation>Index of the element.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

complexType complexDescription
diagram
namespace urn:IEEE-1671.1:2009:TestDescription
type extension of td:DatumDescriptionType
properties
base td:DatumDescriptionType
mixed false
children Resolution ErrorLimits Range Confidence NominalValue
attributes
Name  Type  Use  Default  Fixed  Annotation
standardUnit  c:StandardUnitoptional