complexType "vr:Creator"
Namespace:
Content:
complex, 1 attribute, 3 elements
Defined:
Includes:
definitions of 1 attribute, 3 elements
Used:
XML Representation Summary
<...
    ivo-id
 = 
xs:anyURI
    >
   
Content: 
name, logo?, altIdentifier*
</...>
Content Model Elements (3):
All Direct / Indirect Based Elements (1):
Known Usage Locations
Annotation
The entity (e.g. person or organisation) primarily responsible for creating something
XML Source (see within schema source)
<xs:complexType name="Creator">
<xs:annotation>
<xs:documentation>
The entity (e.g. person or organisation) primarily responsible
for creating something
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="name" type="vr:ResourceName">
<xs:annotation>
<xs:documentation>
the name or title of the creating person or organisation
</xs:documentation>
<xs:documentation>
Users of the creation should use this name in
subsequent credits and acknowledgements.

This should be exactly one name, preferably last name
first (as in "van der Waals, Johannes Diderik").
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="logo" type="xs:anyURI">
<xs:annotation>
<xs:documentation>
URL pointing to a graphical logo, which may be used to help
identify the information source
</xs:documentation>
<xs:documentation>
A logo needs only be provided for the first occurrence.
When multiple logos are supplied via multiple creator
elements, the application is free to choose which to
use.
</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. Always use a URI form including
a scheme here.
</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 creator (typically when it is
an organization).
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
Attribute Detail (all declarations; 1)
ivo-id
Type:
Use:
optional
Defined:
locally within (this) vr:Creator complexType
An IVOA identifier for the creator (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 creator (typically when it is
an organization).
</xs:documentation>
</xs:annotation>
</xs:attribute>
Content Element Detail (all declarations; 3)
altIdentifier
Type:
xs:anyURI, simple content
Defined:
locally within (this) vr:Creator complexType
A reference to this entitiy in a non-IVOA identifier scheme, e.g., orcid. Always use a URI form including a scheme here.
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. Always use a URI form including
a scheme here.
</xs:documentation>
</xs:annotation>
</xs:element>

logo
Type:
xs:anyURI, simple content
Defined:
locally within (this) vr:Creator complexType
Annotation 1 [src]:
URL pointing to a graphical logo, which may be used to help identify the information source
Annotation 2 [src]:
A logo needs only be provided for the first occurrence. When multiple logos are supplied via multiple creator elements, the application is free to choose which to use.
XML Source (see within schema source)
<xs:element minOccurs="0" name="logo" type="xs:anyURI">
<xs:annotation>
<xs:documentation>
URL pointing to a graphical logo, which may be used to help
identify the information source
</xs:documentation>
<xs:documentation>
A logo needs only be provided for the first occurrence.
When multiple logos are supplied via multiple creator
elements, the application is free to choose which to
use.
</xs:documentation>
</xs:annotation>
</xs:element>

name
Type:
vr:ResourceName, simple content
Defined:
locally within (this) vr:Creator complexType
Annotation 1 [src]:
the name or title of the creating person or organisation
Annotation 2 [src]:
Users of the creation should use this name in subsequent credits and acknowledgements. This should be exactly one name, preferably last name first (as in "van der Waals, Johannes Diderik").
XML Source (see within schema source)
<xs:element name="name" type="vr:ResourceName">
<xs:annotation>
<xs:documentation>
the name or title of the creating person or organisation
</xs:documentation>
<xs:documentation>
Users of the creation should use this name in
subsequent credits and acknowledgements.

This should be exactly one name, preferably last name
first (as in "van der Waals, Johannes Diderik").
</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/