complexType "tr:OutputFormat"
Namespace:
Content:
complex, 1 attribute, 2 elements
Defined:
globally in TAPRegExt.xsd; see XML source
Includes:
definitions of 1 attribute, 2 elements
Used:
XML Representation Summary
<...
    ivo-id
 = 
xs:anyURI
    >
   
Content: 
mime, alias*
</...>
Content Model Elements (2):
alias (type xs:token),
mime (type xs:token)
All Direct / Indirect Based Elements (1):
Known Usage Locations
Annotation
Annotation 1 [src]:
An output format supported by the service.
Annotation 2 [src]:
All TAP services must support VOTable output, with media types as requested by the FORMAT parameter if applicable (cf.~section 2.7.1 of the TAP standard). The primary identifier for an output format is the RFC 2046 media type. If you want to register an output format, you must use a media type (or make one up using the x- syntax), although the concrete media syntax is not enforced by the schema. For more detailed specification, an IVOID may be used.
XML Source (see within schema source)
<xs:complexType name="OutputFormat">
<xs:annotation>
<xs:documentation>
An output format supported by the service.
</xs:documentation>
<xs:documentation>
All TAP services must support VOTable output, with media types as
requested by the FORMAT parameter if applicable (cf.~section 2.7.1
of the TAP standard).

The primary identifier for an output format is the RFC 2046 media
type. If you want to register an output format, you must
use a media type (or make one up using the x- syntax), although
the concrete media syntax is not enforced by the schema.

For more detailed specification, an IVOID may be used.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="mime" type="xs:token">
<xs:annotation>
<xs:documentation>
The media type of this format.
</xs:documentation>
<xs:documentation>
The format of this string is specified by RFC 2046.
The service has to accept this string as a
value of the FORMAT parameter.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="alias" type="xs:token">
<xs:annotation>
<xs:documentation>
Other values of FORMAT ("shorthands") that make the service return
documents with the media type.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="ivo-id" type="xs:anyURI">
<xs:annotation>
<xs:documentation>
An optional IVOID of the output format.
</xs:documentation>
<xs:documentation>
When the media type does not uniquely define the
format (or a generic media type like application/octet-stream or
text/plain is given), the IVOID can point to a key
or StandardsRegExt document defining the format more
precisely. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with "output-".
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
Attribute Detail (all declarations; 1)
ivo-id
Type:
Use:
optional
Defined:
locally within (this) tr:OutputFormat complexType
Annotation 1 [src]:
An optional IVOID of the output format.
Annotation 2 [src]:
When the media type does not uniquely define the format (or a generic media type like application/octet-stream or text/plain is given), the IVOID can point to a key or StandardsRegExt document defining the format more precisely. To see values defined in TAPRegExt, retrieve the ivo://ivoa.net/std/TAPRegExt resource record and look for keys starting with "output-".
XML Source (see within schema source)
<xs:attribute name="ivo-id" type="xs:anyURI">
<xs:annotation>
<xs:documentation>
An optional IVOID of the output format.
</xs:documentation>
<xs:documentation>
When the media type does not uniquely define the
format (or a generic media type like application/octet-stream or
text/plain is given), the IVOID can point to a key
or StandardsRegExt document defining the format more
precisely. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with "output-".
</xs:documentation>
</xs:annotation>
</xs:attribute>
Content Element Detail (all declarations; 2)
alias
Type:
xs:token, simple content
Defined:
locally within (this) tr:OutputFormat complexType
Other values of FORMAT ("shorthands") that make the service return documents with the media type.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="alias" type="xs:token">
<xs:annotation>
<xs:documentation>
Other values of FORMAT ("shorthands") that make the service return
documents with the media type.
</xs:documentation>
</xs:annotation>
</xs:element>

mime
Type:
xs:token, simple content
Defined:
locally within (this) tr:OutputFormat complexType
Annotation 1 [src]:
The media type of this format.
Annotation 2 [src]:
The format of this string is specified by RFC 2046. The service has to accept this string as a value of the FORMAT parameter.
XML Source (see within schema source)
<xs:element name="mime" type="xs:token">
<xs:annotation>
<xs:documentation>
The media type of this format.
</xs:documentation>
<xs:documentation>
The format of this string is specified by RFC 2046.
The service has to accept this string as a
value of the FORMAT parameter.
</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/