complexType "vr:Contact"

Namespace:	http://www.ivoa.net/xml/VOResource/v1.0
Content:	complex, 1 attribute, 5 elements
Defined:	globally in VOResource.xsd; see XML source
Includes:	definitions of 1 attribute, 5 elements
Used:	at 1 location

XML Representation Summary

<...

ivo-id

xs:anyURI

Content:

name, address?, email?, telephone?, altIdentifier*

</...>

Content Model Elements (5):

All Direct / Indirect Based Elements (1):

Known Usage Locations

As direct type of elements (1):
contact (type vr:Contact)

Information allowing establishing contact, e.g., for purposes of support.

XML Source (see within schema source)

<xs:complexType name="Contact">

<xs:annotation>

<xs:documentation>

Information allowing establishing contact, e.g., for purposes
of support.

</xs:documentation>

</xs:annotation>

<xs:sequence>

<xs:element name="name" type="vr:ResourceName">

<xs:annotation>

<xs:documentation>

the name or title of the contact person.

</xs:documentation>

<xs:documentation>

This can be a person's name, e.g. “John P. Jones” or
a group, “Archive Support Team”.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element minOccurs="0" name="address" type="xs:token">

<xs:annotation>

<xs:documentation>the contact mailing address</xs:documentation>

<xs:documentation>

All components of the mailing address are given in one
string, e.g. “3700 San Martin Drive, Baltimore, MD 21218 USA”.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element minOccurs="0" name="email" type="xs:token">

<xs:annotation>

<xs:documentation>the contact email address</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element minOccurs="0" name="telephone" type="xs:token">

<xs:annotation>

<xs:documentation>the contact telephone number</xs:documentation>

<xs:documentation>

Complete international dialing codes should be given, e.g.
“+1-410-338-1234”.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element maxOccurs="unbounded" minOccurs="0" name="altIdentifier" type="xs:anyURI">

<xs:annotation>

<xs:documentation>

A reference to this entitiy in a non-IVOA identifier
scheme, e.g., orcid. See the VOResource specification
for syntax constraints on these identifiers.

</xs:documentation>

</xs:annotation>

</xs:element>

</xs:sequence>

<xs:attribute name="ivo-id" type="vr:IdentifierURI">

<xs:annotation>

<xs:documentation>

An IVOA identifier for the contact (typically when it is
an organization).

</xs:documentation>

</xs:annotation>

</xs:attribute>

</xs:complexType>

Attribute Detail (all declarations; 1)

Type:	vr:IdentifierURI
Use:	optional
Defined:	locally within (this) vr:Contact complexType

An IVOA identifier for the contact (typically when it is an organization).

XML Source (see within schema source)

<xs:attribute name="ivo-id" type="vr:IdentifierURI">

<xs:annotation>

<xs:documentation>

An IVOA identifier for the contact (typically when it is
an organization).

</xs:documentation>

</xs:annotation>

</xs:attribute>

Content Element Detail (all declarations; 5)

Type:	xs:token, simple content
Defined:	locally within (this) vr:Contact complexType

the contact mailing address

All components of the mailing address are given in one string, e.g. “3700 San Martin Drive, Baltimore, MD 21218 USA”.

XML Source (see within schema source)

<xs:element minOccurs="0" name="address" type="xs:token">

<xs:annotation>

<xs:documentation>the contact mailing address</xs:documentation>

<xs:documentation>

All components of the mailing address are given in one
string, e.g. “3700 San Martin Drive, Baltimore, MD 21218 USA”.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:anyURI, simple content
Defined:	locally within (this) vr:Contact complexType

A reference to this entitiy in a non-IVOA identifier scheme, e.g., orcid. See the VOResource specification for syntax constraints on these identifiers.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="altIdentifier" type="xs:anyURI">

<xs:annotation>

<xs:documentation>

A reference to this entitiy in a non-IVOA identifier
scheme, e.g., orcid. See the VOResource specification
for syntax constraints on these identifiers.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within (this) vr:Contact complexType

the contact email address

XML Source (see within schema source)

<xs:element minOccurs="0" name="email" type="xs:token">

<xs:annotation>

<xs:documentation>the contact email address</xs:documentation>

</xs:annotation>

</xs:element>

Type:	vr:ResourceName, simple content
Defined:	locally within (this) vr:Contact complexType

the name or title of the contact person.

This can be a person's name, e.g. “John P. Jones” or a group, “Archive Support Team”.

XML Source (see within schema source)

<xs:element name="name" type="vr:ResourceName">

<xs:annotation>

<xs:documentation>

the name or title of the contact person.

</xs:documentation>

<xs:documentation>

This can be a person's name, e.g. “John P. Jones” or
a group, “Archive Support Team”.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within (this) vr:Contact complexType

the contact telephone number

Complete international dialing codes should be given, e.g. “+1-410-338-1234”.

XML Source (see within schema source)

<xs:element minOccurs="0" name="telephone" type="xs:token">

<xs:annotation>

<xs:documentation>the contact telephone number</xs:documentation>

<xs:documentation>

Complete international dialing codes should be given, e.g.
“+1-410-338-1234”.

</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/