element <RedshiftFrame>
Namespace:
http://www.ivoa.net/xml/STC/stc-v1.30.xsd
Type:
redshiftFrameType
Content:
complex, 8 attributes, 4 elements
Nillable:
 (can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
globally in stc-v1.30.xsd; see XML source
Used:
never
XML Representation Summary
<RedshiftFrame
    IDREF_type
 = 
 xs:string
    ID_type
 = 
 xs:string
    id
 = 
 xs:ID
    idref
 = 
 xs:IDREF
    ucd
 = 
 xs:string
    value_type
 = 
 ("VELOCITY" | "REDSHIFT") : "VELOCITY"
    xlink:href
 = 
 xs:anyURI
    xlink:type
 = 
 ("simple" | "extended" | "locator" | "arc" | "resource" | "title") : "simple"
    >
   
Content: 
 Name?, DopplerDefinition, ReferencePosition
</RedshiftFrame>
Content model elements (3):
DopplerDefinition (type dopplerDefinitionType),
Name (type xs:string),
ReferencePosition
Included in content model of elements (3):
AstroCoordSystem,
AstroCoordSystem,
coordsystem (type astroCoordSystemType)
Annotation
Contains the Doppler definitions, including whether the values are velocity or redshift (value_type)
XML Source (see within schema source)
<xs:element name="RedshiftFrame" nillable="true" type="redshiftFrameType">
<xs:annotation>
<xs:documentation>
Contains the Doppler definitions, including whether the values are velocity or redshift (value_type)
</xs:documentation>
</xs:annotation>
</xs:element>
Attribute Detail (all declarations; 8)
id
Type:
xs:ID
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:
xs:string
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:
xs:IDREF
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:
xs:string
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:
xs:string
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="ucd" type="xs:string" use="optional"/>
value_type
Type:
anonymous (restriction of xs:string)
Use:
optional
Default:
"VELOCITY"
Defined:
locally within redshiftFrameType complexType
Anonymous simpleType
Derivation:
restriction of xs:string
XML Source (see within schema source)
<xs:attribute default="VELOCITY" name="value_type" use="optional">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="VELOCITY"/>
<xs:enumeration value="REDSHIFT"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
xlink:href
Type:
xs:anyURI
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; 4)
DopplerDefinition
Type:
dopplerDefinitionType, simple content
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
locally within redshiftFrameType complexType
The Doppler definition used: optical, radio, or pseudo-relativistic (i.e., how is a redshift converted to a velocity); the most common is optical, except when the reference is LSR (usually radio)
XML Source (see within schema source)
<xs:element name="DopplerDefinition" nillable="true" type="dopplerDefinitionType">
<xs:annotation>
<xs:documentation>
The Doppler definition used: optical, radio, or pseudo-relativistic (i.e., how is a redshift converted to a velocity); the most common is optical, except when the reference is LSR (usually radio)
</xs:documentation>
</xs:annotation>
</xs:element>
Name
Type:
xs:string, simple content
Defined:
locally within coordFrameType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" name="Name" type="xs:string"/>
Name
Type:
xs:string, simple content
Defined:
locally within coordFrameType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" name="Name" type="xs:string"/>
ReferencePosition
Type:
referencePositionType, empty content
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
may be substituted with 44 elements
Defined:
by reference within redshiftFrameType complexType
The reference frame for the Doppler velocities or redshfts; note presence of LSR
XML Source (see within schema source)
<xs:element ref="ReferencePosition">
<xs:annotation>
<xs:documentation>
The reference frame for the Doppler velocities or redshfts; note presence of LSR
</xs:documentation>
</xs:annotation>
</xs:element>
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/