Contained within <CatalogueConstraint>s, <TargetVisit>s are links to <Target>s plus additional information pertinant to scheduling observations. This information is given via the attributes "minimum=", and "maximum=", which are the min/max number of visits for the referenced target. When combined with the selection criteria from <CatalogueConstraint>, a detailed management of what should be done is possible. Non-RTML content can be included via an external schema. |
<xs:complexType name="TargetVisitComplexType"> <xs:annotation> <xs:documentation>Contained within <CatalogueConstraint>s, <TargetVisit>s are links to <Target>s plus additional information pertinant to scheduling observations. This information is given via the attributes "minimum=", and "maximum=", which are the min/max number of visits for the referenced target. When combined with the selection criteria from <CatalogueConstraint>, a detailed management of what should be done is possible. Non-RTML content can be included via an external schema.</xs:documentation> </xs:annotation> <xs:sequence> <xs:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="minimum" type="xs:positiveInteger"/> <xs:attribute name="maximum" type="xs:positiveInteger"/> <xs:attributeGroup ref="RTMLAttributes"/> </xs:complexType> |