complexType "exp:ConceptType"
Namespace:
http://cpas.fhcrc.org/exp/xml
Content:
complex, 1+any attributes, 3 elements
Defined:
globally in expTypes.xsd, see XML source
Includes:
definitions of 1+any attributes and 3 elements
Used:
never
XML Representation Summary
<...
    source
 = 
 xs:string
    {any attribute with any namespace}
    >
   
Content: 
 exp:subtree? × exp:labelColumn? × exp:importColumn?
</...>
Content Model Elements (3):
exp:importColumn (type xs:string),
exp:labelColumn (type xs:string),
exp:subtree (type xs:string)
XML Source (see within schema source)
<xs:complexType name="ConceptType">
<xs:all>
<xs:annotation>
<xs:documentation>
Only relevant to concept-valued columns (conceptURI=http://www.labkey.org/types#conceptCode).
These properties define how the column data is imported, and the target ontology.
</xs:documentation>
</xs:annotation>
<xs:element maxOccurs="1" minOccurs="0" name="subtree" type="xs:string">
<xs:annotation>
<xs:documentation>
This is a slash ('/') separated path of concepts codes. The values in this column are expected
to be children of the tree rooted at this path. This is not yet enforced, but this is used to
disambiguate synonyms on import, and to modify the display of concepts that are not in the expected tree.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="labelColumn" type="xs:string">
<xs:annotation>
<xs:documentation>
Name of column to hold the label of the resolved concept.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="importColumn" type="xs:string">
<xs:annotation>
<xs:documentation>
Name of column which holds the imported/provided/reported label for this concept. The LabKey import
code will try to use the value provided in the named column to resolve a concept code defined in the source ontology.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:all>
<xs:attribute name="source" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>
Short name of the target ontology for this column. E.g. "SNOMED_CT" or "NCI"
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType>
Attribute Detail
source
Type:
xs:string, predefined
Use:
optional
Defined:
locally, within (this) exp:ConceptType complexType
Short name of the target ontology for this column. E.g. "SNOMED_CT" or "NCI"
XML Source (see within schema source)
<xs:attribute name="source" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>
Short name of the target ontology for this column. E.g. "SNOMED_CT" or "NCI"
</xs:documentation>
</xs:annotation>
</xs:attribute>
{any attribute with any namespace}
Defined:
within (this) exp:ConceptType complexType
XML Source (see within schema source)
<xs:anyAttribute namespace="##any" processContents="lax"/>
Content Element Detail
exp:importColumn
Type:
xs:string, predefined, simple content
Defined:
locally, within (this) exp:ConceptType complexType
Name of column which holds the imported/provided/reported label for this concept. The LabKey import code will try to use the value provided in the named column to resolve a concept code defined in the source ontology.
XML Source (see within schema source)
<xs:element minOccurs="0" name="importColumn" type="xs:string">
<xs:annotation>
<xs:documentation>
Name of column which holds the imported/provided/reported label for this concept. The LabKey import
code will try to use the value provided in the named column to resolve a concept code defined in the source ontology.
</xs:documentation>
</xs:annotation>
</xs:element>
exp:labelColumn
Type:
xs:string, predefined, simple content
Defined:
locally, within (this) exp:ConceptType complexType
Name of column to hold the label of the resolved concept.
XML Source (see within schema source)
<xs:element minOccurs="0" name="labelColumn" type="xs:string">
<xs:annotation>
<xs:documentation>
Name of column to hold the label of the resolved concept.
</xs:documentation>
</xs:annotation>
</xs:element>
exp:subtree
Type:
xs:string, predefined, simple content
Defined:
locally, within (this) exp:ConceptType complexType
This is a slash ('/') separated path of concepts codes. The values in this column are expected to be children of the tree rooted at this path. This is not yet enforced, but this is used to disambiguate synonyms on import, and to modify the display of concepts that are not in the expected tree.
XML Source (see within schema source)
<xs:element maxOccurs="1" minOccurs="0" name="subtree" type="xs:string">
<xs:annotation>
<xs:documentation>
This is a slash ('/') separated path of concepts codes. The values in this column are expected
to be children of the tree rooted at this path. This is not yet enforced, but this is used to
disambiguate synonyms on import, and to modify the display of concepts that are not in the expected tree.
</xs:documentation>
</xs:annotation>
</xs:element>
This XML schema documentation has been generated with DocFlex/XML RE 1.7.2 using DocFlex/XML XSDDoc 2.1.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/