element <TimeRefDirection>
Namespace:
Type:
Content:
complex, 8 attributes, 9 elements
Defined:
locally at 2 locations in stc-v1.30.xsd
XML Representation Summary
<TimeRefDirection
    IDREF_type
 = 
xs:string
    ID_type
 = 
xs:string
    coord_system_id
 = 
xs:IDREF
    id
 = 
xs:ID
    idref
 = 
xs:IDREF
    ucd
 = 
xs:string
    xlink:href
 = 
xs:anyURI
    xlink:type
 = 
("simple" | "extended" | "locator" | "arc" | "resource" | "title") : "simple"
    >
   
Content: 
GenCoordinate*, Time?, Position?, Velocity?, Spectral?, Redshift?, CoordFile?, Orbit?
</TimeRefDirection>
Content model elements (8):
Included in content model of elements (2):
Definition Locations
Annotations (1) (by all definition locations)
Locations:
within timeFrameType complexType [def], within timeFrameType complexType [def]
Annotation:
Some time transformations (e.g., change of RefPos) depend on an assumed directonal position of the source
Attribute Detail (all declarations; 8)
coord_system_id
Type:
Use:
required
Defined:
locally within coordsType complexType
XML Source (see within schema source)
<xs:attribute name="coord_system_id" type="xs:IDREF" use="required"/>

id
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="id" type="xs:ID" use="optional"/>

ID_type
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="ID_type" type="xs:string" use="optional"/>

idref
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="idref" type="xs:IDREF" use="optional"/>

IDREF_type
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="IDREF_type" type="xs:string" use="optional"/>

ucd
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="ucd" type="xs:string" use="optional"/>

xlink:href
Type:
Use:
optional
Defined:
by reference within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute ref="xlink:href" use="optional"/>

xlink:type
Type:
anonymous (restriction of xs:NMTOKEN)
Use:
optional
Default:
"simple"
Defined:
by reference within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute default="simple" ref="xlink:type" use="optional"/>
Content Element Detail (all declarations; 9)
CoordFile
Type:
astroCoordsFileType, complex content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
locally within astroCoordsType complexType
Some or all coordinate values may be given in file
XML Source (see within schema source)
<xs:element minOccurs="0" name="CoordFile" nillable="true" type="astroCoordsFileType">
<xs:annotation>
<xs:documentation>
Some or all coordinate values may be given in file
</xs:documentation>
</xs:annotation>
</xs:element>

GenCoordinate
Type:
coordinateType, complex content
Subst.Gr:
may substitute for 2 elements; may be substituted with 8 elements
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within coordsType complexType
XML Source (see within schema source)
<xs:element ref="GenCoordinate"/>

GenCoordinate
Type:
coordinateType, complex content
Subst.Gr:
may substitute for 2 elements; may be substituted with 8 elements
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within coordsType complexType
XML Source (see within schema source)
<xs:element ref="GenCoordinate"/>

Orbit
Type:
orbitType, complex content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
locally within astroCoordsType complexType
Orbit specified by orbital elements
XML Source (see within schema source)
<xs:element minOccurs="0" name="Orbit" nillable="true" type="orbitType">
<xs:annotation>
<xs:documentation>Orbit specified by orbital elements</xs:documentation>
</xs:annotation>
</xs:element>

Position
Type:
coordinateType, complex content
Subst.Gr:
may substitute for 2 elements; may be substituted with 6 elements
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within astroCoordsType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" ref="Position"/>

Redshift
Type:
redshiftCoordinateType, complex content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within astroCoordsType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" ref="Redshift"/>

Spectral
Type:
spectralCoordinateType, complex content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within astroCoordsType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" ref="Spectral"/>

Time
Type:
timeCoordinateType, complex content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within astroCoordsType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" ref="Time"/>

Velocity
Type:
coordinateType, complex content
Subst.Gr:
may substitute for 2 elements; may be substituted with 6 elements
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
by reference within astroCoordsType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" ref="Velocity"/>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.0 using DocFlex/XML XSDDoc 2.2.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/