Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I read this correctly, then what you're trying to do is not straight-forward. There is no "magic" connection between the XML document and the schema, you will have to load the schema in the stylesheet and find the documentation in it.</p> <p>Assuming that at a certain point your XSLT stylesheet is in a position where <code>typewoning</code> is under the context element (i.e. <code>value-of select="typewoning"</code> would output its value), you can do this:</p> <pre><code>&lt;xsl:variable name="schema" select="document('my-schema.xsd')/xsd:schema"/&gt; &lt;xsl:variable name="type" select="$schema//xsd:simpleType[@name = 'TypeWoningEnum']"/&gt; &lt;xsl:variable name="value" select="$type//xsd:enumeration[@value = typewoning]//xsd:documentation"/&gt; &lt;xsl:value-of select="$value"/&gt; </code></pre> <p>Some explanation:</p> <ol> <li>The first step loads the schema into a variable using the XSL document function</li> <li>The second step finds the right type (you could probably get fancier and find the type using the element's type in the document, but then schema validation would have to be on and you need a schema-compliant XSLT engine)</li> <li>The third step finds the documentation value to output, given the content of your <code>typewoning</code> element.</li> </ol> <p>Fourth step writes the result out, use as you wish.</p> <p><strong>Edit:</strong> an alternative, if you are willing to use a schema-compliant XSLT engine, such as the paid for version of <a href="http://www.saxonica.com/" rel="nofollow noreferrer">saxon</a>. Assuming all your enumerations derive from <code>integer</code>, you can try this within the context of some parent node:</p> <pre><code>&lt;xsl:variable name="schema" select="document('my-schema.xsd')/xsd:schema"/&gt; &lt;xsl:for-each select="element(*, xsd:integer)"&gt; &lt;xsl:variable name="type" select="$schema//xsd:simpleType[@name = local-name(current())]"/&gt; &lt;xsl:if test="$type"&gt; &lt;xsl:variable name="value" select="$type//xsd:enumeration[@value = current()/text()]//xsd:documentation"/&gt; &lt;xsl:text&gt;Value: &lt;/xsl:text&gt; &lt;xsl:value-of select="$value"/&gt; &lt;/xsl:if&gt; &lt;/xsl:for-each&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow can I use annotations in XSD to map XML integers to the related descriptions?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USxcut
    1. USxcut
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I use annotations in XSD to map XML integers to the related descriptions?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you kindly for elaborating. I was hoping that there might be some magic mapping tool, which would map integers as part of an enumerated type to the annotations in the XSD. I have about 20 to 30 fields where I have to perform this mapping, so your solution, although good and correct, would somewhat pollute my 'to-HTML' xsl stylesheet. I think I may use your code to first perform the mapping on the xml source, and output a 'mapped' xml source, which I would then translate to html. I am even contemplating writing an XSL to transform the XSD into an XSL which will do the mapping... Crazy.
      singulars
      1. PO
      1. USSymen Timmermans
    2. CO@Symen Timmermans: It seems that you have cross references here. This could be done in a general way without "pollute" your stylesheet. It requires the use of `xsl:key`. If you provide a reduce but full example of your two input document (data and schema) and desired output, someone could post an answer.
      singulars
      1. PO
      1. This table or related slice is empty.
    3. CO@Symon Timmermans: added a further example showing how this can be simplified if you are willing to use a schema-aware XSLT processor.
      singulars
      1. PO
      1. USxcut
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload