Namespace:	{global namespace}
Type:	vr:Content
Content:	complex, 7 elements
Defined:	locally at 3 locations in VOResource.xsd

XML Representation Summary

Content:

subject+, description, source?, referenceURL, type*, contentLevel*, relationship*

</content>

Content model elements (7):

Included in content model of elements (1):

Definition Locations

Within global complexTypes (3):
vr:Resource [def], vr:Resource [def], vr:Resource [def]

Annotations (1) (by all definition locations)

within vr:Resource complexType [def], within vr:Resource complexType [def], within vr:Resource complexType [def]

Information regarding the general content of the resource

Content Element Detail (all declarations; 7)

Type:	xs:token, simple content
Defined:	locally within vr:Content complexType

Description of the content level or intended audience. Values for contentLevel should be taken from the controlled vocabulary http://www.ivoa.net/rdf/voresource/content_level.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="contentLevel" type="xs:token">

<xs:annotation>

<xs:appinfo>

<vm:dcterm>Subject</vm:dcterm>

<vm:dcterm>Subject.ContentLevel</vm:dcterm>

</xs:appinfo>

<xs:documentation>

Description of the content level or intended audience.
Values for contentLevel should be taken from the controlled
vocabulary
http://www.ivoa.net/rdf/voresource/content_level.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:string, simple content
Defined:	locally within vr:Content complexType

An account of the nature of the resource

The description may include but is not limited to an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. Note that description is xs:string-typed, which means that whitespace is considered significant. Clients should render empty lines as paragraph boundaries and ideally refrain from reflowing material that looks formatted (i.e., is broken to about 80-character lines).

XML Source (see within schema source)

<xs:element name="description" type="xs:string">

<xs:annotation>

<xs:appinfo>

<vm:dcterm>Description</vm:dcterm>

</xs:appinfo>

<xs:documentation>

An account of the nature of the resource

</xs:documentation>

<xs:documentation>

The description may include but is not limited to an abstract,
table of contents, reference to a graphical representation of
content or a free-text account of the content.

Note that description is xs:string-typed, which means that
whitespace is considered significant. Clients should
render empty lines as paragraph boundaries and ideally
refrain from reflowing material that looks formatted (i.e.,
is broken to about 80-character lines).

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	anonymous (restriction of xs:anyURI), simple content
Defined:	locally within vr:Content complexType

URL pointing to a human-readable document describing this resource.

In order to ensure that users can actually retrieve the content, the schema enforces that this is an http or https URI.

XML Source (see within schema source)

<xs:element name="referenceURL">

<xs:annotation>

<xs:documentation>

URL pointing to a human-readable document describing this
resource.

</xs:documentation>

<xs:documentation>

In order to ensure that users can actually retrieve the
content, the schema enforces that this is an http or https
URI.

</xs:documentation>

</xs:annotation>

<xs:simpleType>

<xs:restriction base="xs:anyURI">

<xs:pattern value="https?://.*"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

Type:	vr:Relationship, complex content
Defined:	locally within vr:Content complexType

a description of a relationship to another resource.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="relationship" type="vr:Relationship">

<xs:annotation>

<xs:documentation>

a description of a relationship to another resource.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	vr:Source, simple content
Defined:	locally within vr:Content complexType

a bibliographic reference from which the present resource is derived or extracted.

This is intended to point to an article in the published literature. An ADS Bibcode is recommended as a value when available.

XML Source (see within schema source)

<xs:element minOccurs="0" name="source" type="vr:Source">

<xs:annotation>

<xs:appinfo>

<vm:dcterm>Source</vm:dcterm>

</xs:appinfo>

<xs:documentation>

a bibliographic reference from which the present resource is
derived or extracted.

</xs:documentation>

<xs:documentation>

This is intended to point to an article in the published
literature. An ADS Bibcode is recommended as a value when
available.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within vr:Content complexType

a topic, object type, or other descriptive keywords about the resource.

The content of subject SHOULD be the fragment identifier of the URI of a concept in the IVOA UAT (http://www.ivoa.net/rdf/uat/), that is, a string like “virtual-observatories”.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" name="subject" type="xs:token">

<xs:annotation>

<xs:appinfo>

<vm:dcterm>Subject</vm:dcterm>

</xs:appinfo>

<xs:documentation>

a topic, object type, or other descriptive keywords
about the resource.

</xs:documentation>

<xs:documentation>

The content of subject SHOULD be the fragment identifier of
the URI of a concept in the IVOA UAT
(http://www.ivoa.net/rdf/uat/), that is, a string like
“virtual-observatories”.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within vr:Content complexType

Nature or genre of the content of the resource. Values for type should be taken from the controlled vocabulary http://www.ivoa.net/rdf/voresource/content_type

XML Source (see within schema source)

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

<xs:annotation>

<xs:appinfo>

<vm:dcterm>Type</vm:dcterm>

</xs:appinfo>

<xs:documentation>

Nature or genre of the content of the resource. Values for
type should be taken from the controlled vocabulary
http://www.ivoa.net/rdf/voresource/content_type

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