XML Schema "VORegistry-v1.0.xsd"
Target Namespace:
http://www.ivoa.net/xml/VORegistry/v1.0
Version:
1.0wd
Defined Components:
9 local elements, 7 complexTypes, 2 simpleTypes
Default Namespace-Qualified Form:
Local Elements: unqualified; Local Attributes: unqualified
Schema Location:
/home/msdemlei/gavo/trunk/gavo/resources/schemata/VORegistry-v1.0.xsd; see XML source
Imports Schema:
VOResource-v1.1.xsd [src]
Annotation
An extension to the core resource metadata (VOResource) for describing registries and authority IDs.
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://www.ivoa.net/xml/VORegistry/v1.0" version="1.0wd" xmlns:vg="http://www.ivoa.net/xml/VORegistry/v1.0" xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1" xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<vm:schemaName>VORegistry</vm:schemaName>
<vm:schemaPrefix>xs</vm:schemaPrefix>
<vm:targetPrefix>vg</vm:targetPrefix>
</xs:appinfo>
<xs:documentation>
An extension to the core resource metadata (VOResource) for
describing registries and authority IDs.
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://www.ivoa.net/xml/VOResource/v1.0" schemaLocation="http://vo.ari.uni-heidelberg.de/docs/schemata/VOResource-v1.1.xsd"/>
<xs:complexType name="Registry">
<xs:annotation>
<xs:documentation>
a service that provides access to descriptions of resources.
</xs:documentation>
<xs:documentation>
A registry is considered a publishing registry if it
contains a capability element with xsi:type="vg:Harvest".
It is considered a searchable registry if it contains a
capability element with xsi:type="vg:Search".
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vr:Service">
<xs:sequence>
<xs:element name="full" type="xs:boolean">
<xs:annotation>
<xs:documentation>
If true, this registry attempts to collect all resource
records known to the IVOA.
</xs:documentation>
<xs:documentation>
A registry typically collects everything by harvesting
from all registries listed in the IVOA Registry of
Registries.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="managedAuthority" type="vr:AuthorityID">
<xs:annotation>
<xs:documentation>
an authority identifier managed by the registry.
</xs:documentation>
<xs:documentation>
Typically, this means the AuthorityIDs that originated
(i.e. were first published by) this registry. Currently,
only one registry can lay claim to an AuthorityID via
this element at a time.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType abstract="true" name="RegCapRestriction">
<xs:annotation>
<xs:documentation>
an abstract capability that fixes the standardID to the
IVOA ID for the Registry standard.
</xs:documentation>
<xs:documentation>
See vr:Capability for documentation on inherited children.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="vr:Capability">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="validationLevel" type="vr:Validation"/>
<xs:element minOccurs="0" name="description" type="xs:token"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="interface" type="vr:Interface"/>
</xs:sequence>
<xs:attribute fixed="ivo://ivoa.net/std/Registry" name="standardID" type="vr:IdentifierURI" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Harvest">
<xs:annotation>
<xs:documentation>
The capabilities of the Registry Harvest implementation.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vg:RegCapRestriction">
<xs:sequence>
<xs:element name="maxRecords" type="xs:int">
<xs:annotation>
<xs:documentation>
The largest number of records that the registry search
method will return. A value greater than one implies
that an OAI continuation token will be provided when
the limit is reached. A value of zero or less
indicates that there is no explicit limit and
thus, continuation tokens are not supported.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Search">
<xs:annotation>
<xs:documentation>
The capabilities of the Registry Search implementation.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vg:RegCapRestriction">
<xs:sequence>
<xs:element name="maxRecords" type="xs:int">
<xs:annotation>
<xs:documentation>
The largest number of records that the registry search
method will return. A value of zero or less indicates
that there is no explicit limit.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="extensionSearchSupport" type="vg:ExtensionSearchSupport">
<xs:annotation>
<xs:documentation>
the level of support provided for searching against
metadata defined in a legal VOResource extension schema.
</xs:documentation>
<xs:documentation>
A legal VOResource extension schema is one that imports
and extends the VOResource core schema in compliance
with the VOResource standard.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="optionalProtocol" type="vg:OptionalProtocol">
<xs:annotation>
<xs:documentation>
the name of an optional advanced search protocol
supported.
</xs:documentation>
<xs:documentation>
Only one optional protocol is currently allowed
(XQuery). It is assumed that the required protocols
(simple keyword search and ADQL) are supported.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:simpleType name="ExtensionSearchSupport">
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="core">
<xs:annotation>
<xs:documentation>
Only searches against the core VOResource metadata are
supported.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="partial">
<xs:annotation>
<xs:documentation>
Searches against some VOResource extension metadata are
supported but not necessarily all that exist in the registry.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="full">
<xs:annotation>
<xs:documentation>
Searches against all VOResource extension metadata contained
in the registry are supported.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="OptionalProtocol">
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="XQuery">
<xs:annotation>
<xs:documentation>
the XQuery (http://www.w3.org/TR/xquery/) protocol as defined
in the VO Registry Interface standard.
</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="OAIHTTP">
<xs:annotation>
<xs:documentation>
a description of the standard OAI PMH interface using HTTP
(GET or POST) queries.
</xs:documentation>
<xs:documentation>
the accessURL child element is the base URL for the OAI
service as defined in section 3.1.1 of the OAI PMH
standard.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vr:Interface">
<xs:sequence/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="OAISOAP">
<xs:annotation>
<xs:documentation>
a description of the standard OAI PMH interface using a SOAP
Web Service interface.
</xs:documentation>
<xs:documentation>
the accessURL child element is the service port location URL for
the OAI SOAP Web Service.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vr:WebService">
<xs:sequence/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Authority">
<xs:annotation>
<xs:documentation>
a naming authority; an assertion of control over a
namespace represented by an authority identifier.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vr:Resource">
<xs:sequence>
<xs:element name="managingOrg" type="vr:ResourceName">
<xs:annotation>
<xs:documentation>
the organization that manages or owns this authority.
</xs:documentation>
<xs:documentation>
In most cases, this will be the same as the Publisher.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
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/