| <?xml version="1.0" encoding="UTF-8"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://docs.g-vo.org/schemata/DaCHS.xsd" version="1.0" xmlns:tns="http://docs.g-vo.org/schemata/DaCHS.xsd" xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1" xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <xsd:import namespace="http://www.ivoa.net/xml/VOResource/v1.0" schemaLocation="http://docs.g-vo.org/schemata/VOResource.xsd"/> <xsd:annotation> <xsd:appinfo> <vm:schemaName>TAPRegExt</vm:schemaName> <vm:schemaPrefix>xs</vm:schemaPrefix> <vm:targetPrefix>tr</vm:targetPrefix> </xsd:appinfo> <xsd:documentation> A schema for holding schema items slated to enter VOResource while they are prototyped in DaCHS. Items here may disapprear when we believe all adopters of the previous versions should have migrated. And they may change without prior notice. In short: This is the VO's Old West. </xsd:documentation> </xsd:annotation> <!-- 2021: DALIInterface as proposed for TAPRegExt --> <xsd:annotation> <xsd:documentation> An interface for a complex, multi-endpoint interfaces as regulated by DALI. </xsd:documentation> <xsd:documentation> In addition to the standard vr:Interface elements, DALIInterfaces have endpoints, listed by name; that name doubles as a path segment to append to the interface's access URL, yielding the URI at which the endpoint is operated. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:sequence> <xsd:annotation> <xsd:documentation> An endpoint accessible through this interface. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation> An endpoint of a complex interface. </xsd:documentation> <xsd:documentation> An endpoint is characterised and addrssed by its name; they can further be defined through RDF triples. This is a generic extension mechanism for endpoint-specific metadata, primarily intended for custom, vendor-specific extensions. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation> The endpoint name, which is also the last component of the path of its URI. </xsd:documentation> <xsd:documentation> Names without dashes are reserved for IVOA use and are expected to work the same way on all services. Well-known examples for such endpoint names include sync, async, and tables. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Auxiliary information on this endpoint. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation> A container for an RDFa triple giving information related to an endpoint. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:annotation> <xsd:documentation> The subject of the statement. </xsd:documentation> <xsd:documentation> If missing, the endpoint itself is assumed as the subject. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The property of the statement. </xsd:documentation> <xsd:documentation> This is a reference to an RDF resource. IVOA standards may define semantics for scheme-less URI; non-IVOA properties must use full URIs with at least scheme and authority; in this version, no vocab attributes are supported. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The object of the statement. </xsd:documentation> <xsd:documentation> If missing, the text content of the element is used as the object. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType> </xsd: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:
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/ |