ProjectComplexType

<xs:complexType name="ProjectComplexType">
  <xs:annotation>
    <xs:documentation>Description of the people/institutions and scientific reasons behind the observing request, corresponding to what is usually called "Phase I" information. The minimum information is a single <Contact>. More than one optional <ProjectID> (e.g. different institutions), <Contact> (different investigators), and optional <Keyword> may be given. Observing time is can be allocated either via <Contact> or <TimeAllocation>. The possibility of using hierarchical projects is mainly intended for the transfer of server (rather than client) information. The <AckText> element, when given my servers, should be used in any publications resulting from observations. The <VOEventReference> should contain a syntactically correct IVOA ivorn of a VOEvent message.</xs:documentation>
  </xs:annotation>
  <xs:choice minOccurs="0" maxOccurs="unbounded">
    <xs:element name="AckText" type="MixedContentComplexType"/>
    <xs:element name="Contact" type="ContactComplexType"/>
    <xs:element name="ObservingPeriod" type="ObservingPeriodComplexType"/>
    <xs:element name="Title" type="xs:string"/>
    <xs:element name="Abstract" type="xs:string"/>
    <xs:element name="ScientificJustification" type="MixedContentComplexType"/>
    <xs:element name="TechnicalJustification" type="MixedContentComplexType"/>
    <xs:element name="Keyword" type="xs:string"/>
    <xs:element name="Priority" type="PriorityComplexType"/>
    <xs:element name="TimeAllocation" type="TimeAllocationComplexType"/>
    <xs:element name="VOEventReference" type="xs:token"/>
    <xs:element name="Project" type="ProjectComplexType"/>
    <xs:any namespace="##other" processContents="strict"/>
  </xs:choice>
  <xs:attribute name="ProjectID" type="xs:token"/>
  <xs:attributeGroup ref="RTMLAttributes"/>
</xs:complexType>