Namespace: |
|
Type: |
anonymous complexType |
Content: |
|
Defined: |
globally in cmlreact.xsd; see XML source |
Used: |
at 1 location |
XML Representation Summary |
|||||||||
<relatedEntry | |||||||||
|
|||||||||
> | |||||||||
|
|||||||||
</relatedEntry> |
<xsd:element id="el.relatedEntry" name="relatedEntry"> <xsd:annotation> <xsd:documentation> <h:div class="summary"> An entry related in some way to a dictionary entry. </h:div> <h:div class="description"> The range of relationships is not restricted but should include parents, aggregation, seeAlso and so on. DataCategories from ISO12620 can be referenced through the namespaced mechanism. </h:div> <h:div class="example" href="relatedEntry1.xml"/> </xsd:documentation> </xsd:annotation> <xsd:complexType mixed="true"> <xsd:annotation> <xsd:documentation> <h:div class="specific">The related entry.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attributeGroup> </xsd:complexType> </xsd:element> |
Type: |
xsd:anyURI, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.href" name="href" type="xsd:anyURI"> <xsd:annotation> <xsd:documentation> <h:div class="summary">address of a resource.</h:div> <h:div class="description"> Links to another element in the same or other file. For dictionary/@dictRef requires the prefix and the physical URI address to be contained within the same file. We can anticipate that better mechanisms will arise - perhaps through XMLCatalogs. At least it works at present. </h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
Derivation: |
by union |
Derivation: |
restriction of xsd:string |
Derivation: |
restriction of namespaceRefType |
<xsd:attribute id="att.relatedEntryType" name="type"> <xsd:simpleType> <xsd:annotation> <xsd:documentation> <h:div class="summary">Type of relatedEntry.</h:div> <h:div class="description"> Type represents a the type of relationship in a relatedEntry element. </h:div> </xsd:documentation> </xsd:annotation> <xsd:union> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="parent"/> <xsd:enumeration value="partitiveParent"/> <xsd:enumeration value="child"/> <xsd:enumeration value="partitiveChild"/> <xsd:enumeration value="related"/> <xsd:enumeration value="synonym"/> <xsd:enumeration value="quasi-synonym"/> <xsd:enumeration value="antonym"/> <xsd:enumeration value="homonym"/> <xsd:enumeration value="see"/> <xsd:enumeration value="seeAlso"/> <xsd:enumeration value="abbreviation"/> <xsd:enumeration value="acronym"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType> </xsd:simpleType> </xsd:union> </xsd:simpleType> </xsd:attribute> |
This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.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-quality 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 (Full Edition) 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 that 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 results of which you could enjoy later by yourself.
Every single your purchase matters and makes a difference for us! To purchase a license, please follow this link: http://www.filigris.com/shop/ |