complexType "uws:Parameter"
Namespace:
http://www.ivoa.net/xml/UWS/v1.0
Content:
mixed, 3 attributes
Defined:
globally in UWS.xsd; see XML source
Includes:
definitions of 3 attributes
Used:
at 1 location
XML Representation Summary
<...
    byReference
 = 
 xs:boolean : "false"
    id
 = 
 xs:string
    isPost
 = 
 xs:boolean
    >
   
Content: 
 {text}
</...>
All Direct / Indirect Based Elements (1):
uws:parameter (in uws:parameters)
Known Usage Locations
Annotation
the list of input parameters to the job - if the job description language does not naturally have parameters, then this list should contain one element which is the content of the original POST that created the job.
XML Source (see within schema source)
<xs:complexType mixed="true" name="Parameter">
<xs:annotation>
<xs:documentation>
the list of input parameters to the job - if
the job description language does not naturally have
parameters, then this list should contain one element which
is the content of the original POST that created the job.
</xs:documentation>
</xs:annotation>
<xs:attribute default="false" name="byReference" type="xs:boolean">
<xs:annotation>
<xs:documentation>
if this attribute is true then the
content of the parameter represents a URL to retrieve the
actual parameter value.
</xs:documentation>
<xs:documentation>
It is up to the implementation to decide
if a parameter value cannot be returned directly as the
content - the basic rule is that the representation of
the parameter must allow the whole job element to be
valid XML. If this cannot be achieved then the parameter
value must be returned by reference.
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="id" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>
the identifier for the parameter
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="isPost" type="xs:boolean"/>
</xs:complexType>
Attribute Detail (all declarations; 3)
byReference
Type:
xs:boolean
Use:
optional
Default:
"false"
Defined:
locally within (this) uws:Parameter complexType
Annotation 1 [src]:
if this attribute is true then the content of the parameter represents a URL to retrieve the actual parameter value.
Annotation 2 [src]:
It is up to the implementation to decide if a parameter value cannot be returned directly as the content - the basic rule is that the representation of the parameter must allow the whole job element to be valid XML. If this cannot be achieved then the parameter value must be returned by reference.
XML Source (see within schema source)
<xs:attribute default="false" name="byReference" type="xs:boolean">
<xs:annotation>
<xs:documentation>
if this attribute is true then the
content of the parameter represents a URL to retrieve the
actual parameter value.
</xs:documentation>
<xs:documentation>
It is up to the implementation to decide
if a parameter value cannot be returned directly as the
content - the basic rule is that the representation of
the parameter must allow the whole job element to be
valid XML. If this cannot be achieved then the parameter
value must be returned by reference.
</xs:documentation>
</xs:annotation>
</xs:attribute>
id
Type:
xs:string
Use:
required
Defined:
locally within (this) uws:Parameter complexType
the identifier for the parameter
XML Source (see within schema source)
<xs:attribute name="id" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>
the identifier for the parameter
</xs:documentation>
</xs:annotation>
</xs:attribute>
isPost
Type:
xs:boolean
Use:
optional
Defined:
locally within (this) uws:Parameter complexType
XML Source (see within schema source)
<xs:attribute name="isPost" type="xs:boolean"/>
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/