Namespace "http://labkey.org/study/assay/xml"
Targeting Schemas (1):
assayProvider.xsd
Targeting Components:
2 global elements, 19 local elements, 2 complexTypes
Schema Summary
assayProvider.xsd Target Namespace:
Defined Components:
2 global elements, 19 local elements, 2 complexTypes
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\dev\labkey\labkeyHome\server\modules\platform\assay\schemas\assayProvider.xsd, see XML source
Imports Schema:
All Element Summary
ap:date (in ap:fieldKeys) Field key relative to the data/results table that gives the date for a given row of data
Type:
xs:string
Content:
simple
Defined:
locally within element ap:fieldKeys in assayProvider.xsd, see XML source
ap:description (in ap:provider)
Type:
xs:string
Content:
simple
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
ap:domain
Type:
exp:DomainDescriptorType
Content:
complex, 4 elements
Defined:
globally in assayProvider.xsd, see XML source
Used:
never
ap:fieldKeys (in ap:provider) Contains field keys (column names, potentially with lookups) used to resolve various values
Type:
anonymous complexType
Content:
complex, 4 elements
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
Includes:
definitions of 4 elements
ap:fileName (in ap:transformScript) Simple file name (no path) of the script.
Type:
xs:string
Content:
simple
Defined:
locally within element ap:transformScript in assayProvider.xsd, see XML source
ap:fileSuffix (type extension of xs:string)
Type:
anonymous (extension of xs:string)
Content:
simple, 1 attribute
Defined:
locally within complexType ap:AssayDataType in assayProvider.xsd, see XML source
Includes:
definition of 1 attribute
ap:inputDataFileSuffix (in ap:provider) Deprecated (use inputDataFile/fileSuffixes instead).
Type:
xs:string
Content:
simple
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
ap:moduleName (in ap:requiredModules)
Type:
xs:string
Content:
simple
Defined:
locally within element ap:requiredModules in assayProvider.xsd, see XML source
ap:name (in ap:provider)
Type:
xs:string
Content:
simple
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
ap:namespacePrefix (type xs:string) Namespace prefix to be used when creating the LSID for the input data file
Type:
xs:string
Content:
simple
Defined:
locally within complexType ap:AssayDataType in assayProvider.xsd, see XML source
ap:participantId (in ap:fieldKeys) Field key relative to the data/results table that gives the ParticipantID for a given row of data
Type:
xs:string
Content:
simple
Defined:
locally within element ap:fieldKeys in assayProvider.xsd, see XML source
ap:primaryDataFileType (in ap:provider) Information about the files to be used as inputs to this assay.
Type:
ap:AssayDataType
Content:
complex, 3 elements
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
ap:provider
Type:
ap:ProviderType
Content:
complex, 2 attributes, 9 elements
Defined:
globally in assayProvider.xsd, see XML source
Used:
never
ap:relatedDataFileType (in ap:provider) If there are related data files available on the server's file system (ones that share the same base file name, with different suffixes/file extensions), they are attached to the run at import time.
Type:
ap:AssayDataType
Content:
complex, 3 elements
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
ap:requiredModules (in ap:provider) If provided, this set of modules will always be active in a given folder when an instance of this assay is present.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
Includes:
definition of 1 element
ap:role (type xs:string) The role name to be used for the file when it is used as the input to an assay run
Type:
xs:string
Content:
simple
Defined:
locally within complexType ap:AssayDataType in assayProvider.xsd, see XML source
ap:saveHandler (in ap:provider) Class name of the custom save handler for this assay type.
Type:
xs:string
Content:
simple
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
ap:specimenId (in ap:fieldKeys) Field key relative to the data/results table that gives the SpecimenID for a given row of data
Type:
xs:string
Content:
simple
Defined:
locally within element ap:fieldKeys in assayProvider.xsd, see XML source
ap:transformScript (in ap:transformScripts)
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within element ap:transformScripts in assayProvider.xsd, see XML source
Includes:
definition of 1 element
ap:transformScripts (in ap:provider) Ordered list of transformation/validation scripts that must be run as data is imported.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
locally within complexType ap:ProviderType in assayProvider.xsd, see XML source
Includes:
definition of 1 element
ap:visitId (in ap:fieldKeys) Field key relative to the data/results table that gives the VisitID for a given row of data
Type:
xs:string
Content:
simple
Defined:
locally within element ap:fieldKeys in assayProvider.xsd, see XML source
Complex Type Summary
ap:AssayDataType
Content:
complex, 3 elements
Defined:
globally in assayProvider.xsd, see XML source
Includes:
definitions of 3 elements
Used:
at 2 locations
ap:ProviderType
Content:
complex, 2 attributes, 9 elements
Defined:
globally in assayProvider.xsd, see XML source
Includes:
definitions of 2 attributes and 9 elements
Used:
at 1 location
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/