root/Xml/Working/AnalysisModule.xsd
| Revision 195, 19.7 kB (checked in by andrew, 4 months ago) |
|---|
| Line | |
|---|---|
| 1 | <?xml version = "1.0" encoding = "UTF-8"?> |
| 2 | <!-- |
| 3 | #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 4 | # |
| 5 | # Copyright (C) 2003-2008 Open Microscopy Environment |
| 6 | # Massachusetts Institute of Technology, |
| 7 | # National Institutes of Health, |
| 8 | # University of Dundee, |
| 9 | # University of Wisconsin at Madison |
| 10 | # |
| 11 | #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 12 | --> |
| 13 | <!-- |
| 14 | #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 15 | # Written by: Josiah Johnston <siah@nih.gov>, Andrew J Patterson |
| 16 | #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 17 | --> |
| 18 | <xsd:schema |
| 19 | targetNamespace = "http://www.openmicroscopy.org/Schemas/AnalysisModule/2008-02" |
| 20 | xmlns:AML = "http://www.openmicroscopy.org/Schemas/AnalysisModule/2008-02" |
| 21 | xmlns:CLI = "http://www.openmicroscopy.org/Schemas/CLI/2008-02" |
| 22 | xmlns:Bin = "http://www.openmicroscopy.org/Schemas/BinaryFile/2008-02" |
| 23 | xmlns:MLI = "http://www.openmicroscopy.org/Schemas/MLI/2008-02" |
| 24 | xmlns:OME = "http://www.openmicroscopy.org/Schemas/OME/2008-02" |
| 25 | xmlns:xsd = "http://www.w3.org/2001/XMLSchema" |
| 26 | xmlns:xml="http://www.w3.org/XML/1998/namespace" |
| 27 | version = "1" |
| 28 | elementFormDefault = "qualified"> |
| 29 | <xsd:import namespace = "http://www.openmicroscopy.org/Schemas/CLI/2008-02" schemaLocation = "http://www.openmicroscopy.org/Schemas/CLI/2008-02/CLI.xsd"/> |
| 30 | <xsd:import namespace = "http://www.openmicroscopy.org/Schemas/BinaryFile/2008-02" schemaLocation = "http://www.openmicroscopy.org/Schemas/BinaryFile/2008-02/BinaryFile.xsd"/> |
| 31 | <xsd:import namespace = "http://www.openmicroscopy.org/Schemas/MLI/2008-02" schemaLocation = "http://www.openmicroscopy.org/Schemas/MLI/2008-02/MLI.xsd"/> |
| 32 | <xsd:import namespace = "http://www.openmicroscopy.org/Schemas/OME/2008-02" schemaLocation = "http://www.openmicroscopy.org/Schemas/OME/2008-02/ome.xsd"/> |
| 33 | <xsd:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> |
| 34 | <xsd:element name = "Entry"> <!-- top level definition --> |
| 35 | <xsd:complexType> |
| 36 | <xsd:attribute name = "Value" use = "required"> |
| 37 | <xsd:annotation> |
| 38 | <xsd:documentation>Tied to DB. LOOKUP_TABLE_ENTRIES.VALUE</xsd:documentation> |
| 39 | </xsd:annotation> |
| 40 | <xsd:simpleType> |
| 41 | <xsd:restriction base = "xsd:string"> |
| 42 | <xsd:maxLength value = "256"/> |
| 43 | </xsd:restriction> |
| 44 | </xsd:simpleType> |
| 45 | </xsd:attribute> |
| 46 | <xsd:attribute name = "Label" use="optional"> |
| 47 | <xsd:annotation> |
| 48 | <xsd:documentation>Tied to DB. LOOKUP_TABLE_ENTRIES.LABEL</xsd:documentation> |
| 49 | </xsd:annotation> |
| 50 | <xsd:simpleType> |
| 51 | <xsd:restriction base = "xsd:string"> |
| 52 | <xsd:maxLength value = "256"/> |
| 53 | </xsd:restriction> |
| 54 | </xsd:simpleType> |
| 55 | </xsd:attribute> |
| 56 | </xsd:complexType> |
| 57 | </xsd:element> |
| 58 | <xsd:element name = "LookupTable"> <!-- top level definition --> |
| 59 | <xsd:annotation> |
| 60 | <xsd:documentation>Describes valid values for an input. Think enumerations, (a list of valid values).</xsd:documentation> |
| 61 | </xsd:annotation> |
| 62 | <xsd:complexType> |
| 63 | <xsd:sequence> |
| 64 | <xsd:element ref = "AML:Entry" minOccurs="1" maxOccurs = "unbounded"/> |
| 65 | <xsd:element ref = "OME:Description" minOccurs = "0" maxOccurs="1"/> |
| 66 | </xsd:sequence> |
| 67 | <xsd:attribute name = "Name" use = "required"> |
| 68 | <xsd:annotation> |
| 69 | <xsd:documentation>Tied to DB. LOOKUP_TABLES.NAME</xsd:documentation> |
| 70 | </xsd:annotation> |
| 71 | <xsd:simpleType> |
| 72 | <xsd:restriction base = "xsd:string"> |
| 73 | <xsd:maxLength value = "64"/> |
| 74 | </xsd:restriction> |
| 75 | </xsd:simpleType> |
| 76 | </xsd:attribute> |
| 77 | </xsd:complexType> |
| 78 | </xsd:element> |
| 79 | <xsd:element name = "FormalInput"> <!-- top level definition --> |
| 80 | <xsd:annotation> |
| 81 | <xsd:documentation>Specifies an input requirement for a module. Image dimensions and image file locations (repository or other format) should not be specified with this. Image dimensions are intrinsic to an image. They do not represent a special requirement. Image file locations and contents are specified by other elements. Specifically, RawImageFile, RawImageFilePath, XYPlaneFile, and XYPlaneFilePath. |
| 82 | </xsd:documentation> |
| 83 | </xsd:annotation> |
| 84 | <xsd:complexType> |
| 85 | <xsd:sequence> |
| 86 | <xsd:element ref = "AML:LookupTable" minOccurs = "0" maxOccurs="1"/> |
| 87 | <xsd:element ref = "OME:Description" minOccurs = "0" maxOccurs="1"/> |
| 88 | </xsd:sequence> |
| 89 | <xsd:attribute name = "UserDefined" default = "false" use="optional" type = "xsd:boolean"> |
| 90 | <xsd:annotation> |
| 91 | <xsd:documentation>OME interprets this as a recommendation rather than a requirement. |
| 92 | Tied to DB. Table FORMAL_INPUTS Column USER_DEFINED |
| 93 | </xsd:documentation> |
| 94 | </xsd:annotation> |
| 95 | </xsd:attribute> |
| 96 | <xsd:attribute name = "Count" default = "+" use="optional"> |
| 97 | <xsd:annotation> |
| 98 | <xsd:documentation>Specifies how many counts of this formal input are expected. Meanings are specified below |
| 99 | ! = exactly one |
| 100 | ? = zero or one |
| 101 | + = one or more |
| 102 | * = zero or more |
| 103 | </xsd:documentation> |
| 104 | </xsd:annotation> |
| 105 | <xsd:simpleType> |
| 106 | <xsd:restriction base = "xsd:string"> |
| 107 | <xsd:enumeration value = "!"/> |
| 108 | <xsd:enumeration value = "?"/> |
| 109 | <xsd:enumeration value = "+"/> |
| 110 | <xsd:enumeration value = "*"/> |
| 111 | </xsd:restriction> |
| 112 | </xsd:simpleType> |
| 113 | </xsd:attribute> |
| 114 | <xsd:attribute name = "Name" use = "required"> |
| 115 | <xsd:annotation> |
| 116 | <xsd:documentation>Valid characters are alphanumeric and spaces.</xsd:documentation> |
| 117 | </xsd:annotation> |
| 118 | <xsd:simpleType> |
| 119 | <xsd:restriction base = "xsd:string"> |
| 120 | <xsd:pattern value = "[A-Za-z0-9\-\^\(\)_ ]+"/> |
| 121 | </xsd:restriction> |
| 122 | </xsd:simpleType> |
| 123 | </xsd:attribute> |
| 124 | <xsd:attribute name = "SemanticTypeName" use = "required" type = "xsd:string"/> |
| 125 | </xsd:complexType> |
| 126 | </xsd:element> |
| 127 | <xsd:element name = "FormalOutput"> <!-- top level definition --> |
| 128 | <xsd:annotation> |
| 129 | <xsd:documentation>Specifies an output element of a module.</xsd:documentation> |
| 130 | </xsd:annotation> |
| 131 | <xsd:complexType> |
| 132 | <xsd:sequence> |
| 133 | <xsd:element ref = "OME:Description" minOccurs = "0" maxOccurs="1"/> |
| 134 | </xsd:sequence> |
| 135 | <xsd:attribute name = "IBelongTo" use="optional"> |
| 136 | <xsd:annotation> |
| 137 | <xsd:documentation>Concerning MakeNewRegion attribute of ExecutionInstructions, if a new region type is made, then there are two possible places a formal output attribute can be stored: It can be stored as an attribute of the RegionIterator, or it can be stored as an attribute of the new Region. |
| 138 | This tag is supposed to specify which. Can be left blank if module does not make new iterator. |
| 139 | Tied to DB. FORMAL_OUTPUTS.FEATURE_TAG |
| 140 | Processed before storage to DB |
| 141 | </xsd:documentation> |
| 142 | </xsd:annotation> |
| 143 | <xsd:simpleType> |
| 144 | <xsd:restriction base = "xsd:string"> |
| 145 | <xsd:enumeration value = "[Region]"/> |
| 146 | <xsd:enumeration value = "[Iterator]"/> |
| 147 | </xsd:restriction> |
| 148 | </xsd:simpleType> |
| 149 | </xsd:attribute> |
| 150 | <xsd:attribute name = "Count" default = "+" use="optional"> |
| 151 | <xsd:annotation> |
| 152 | <xsd:documentation>Specifies how many counts of this formal output will be produced. Meanings are specified below |
| 153 | ! = exactly one |
| 154 | ? = zero or one |
| 155 | + = one or more |
| 156 | * = zero or more |
| 157 | </xsd:documentation> |
| 158 | </xsd:annotation> |
| 159 | <xsd:simpleType> |
| 160 | <xsd:restriction base = "xsd:string"> |
| 161 | <xsd:enumeration value = "!"/> |
| 162 | <xsd:enumeration value = "?"/> |
| 163 | <xsd:enumeration value = "+"/> |
| 164 | <xsd:enumeration value = "*"/> |
| 165 | </xsd:restriction> |
| 166 | </xsd:simpleType> |
| 167 | </xsd:attribute> |
| 168 | <xsd:attribute name = "Name" use = "required"> |
| 169 | <xsd:simpleType> |
| 170 | <xsd:restriction base = "xsd:string"> |
| 171 | <xsd:pattern value = "[A-Za-z0-9\-\^\(\)_ ]+"/> |
| 172 | </xsd:restriction> |
| 173 | </xsd:simpleType> |
| 174 | </xsd:attribute> |
| 175 | <xsd:attribute name = "SemanticTypeName" use="optional" type = "xsd:string"> |
| 176 | <xsd:annotation> |
| 177 | <xsd:documentation>THIS IS REQUIRED for every formal output outside of the importer. The importer doesn't know what it will run into before it executes, so it can't declare the semantic type of its outputs. If you are writing a module, I HIGHLY HIGHLY recommend that you type your formal outputs.</xsd:documentation> |
| 178 | </xsd:annotation> |
| 179 | </xsd:attribute> |
| 180 | </xsd:complexType> |
| 181 | </xsd:element> |
| 182 | <xsd:element name = "Declaration"> <!-- top level definition --> |
| 183 | <xsd:annotation> |
| 184 | <xsd:documentation>States module requirements. |
| 185 | Formal Inputs are optional because input requirements may be specified by guaranteed image attributes. For example, OME_Image_XYZ_stats requires a path to the OME repository file, and Dimensions. |
| 186 | These are given by <RawImageFilePath>, <sizeX>, <sizeY>, <sizeZ>, <sizeT>, and <sizeW>. |
| 187 | </xsd:documentation> |
| 188 | </xsd:annotation> |
| 189 | <xsd:complexType> |
| 190 | <xsd:sequence> |
| 191 | <xsd:element ref = "AML:FormalInput" minOccurs = "0" maxOccurs = "unbounded"/> |
| 192 | <xsd:element ref = "AML:FormalOutput" minOccurs = "0" maxOccurs = "unbounded"/> |
| 193 | </xsd:sequence> |
| 194 | </xsd:complexType> |
| 195 | </xsd:element> |
| 196 | <xsd:element name = "AnalysisModule"> <!-- top level definition --> |
| 197 | <xsd:annotation> |
| 198 | <xsd:documentation>Describes an interface to use with a program.</xsd:documentation> |
| 199 | </xsd:annotation> |
| 200 | <xsd:complexType> |
| 201 | <xsd:sequence> |
| 202 | <xsd:element ref = "OME:Description" minOccurs = "0" maxOccurs="1"/> |
| 203 | <xsd:element ref = "AML:Declaration" minOccurs="1" maxOccurs="1"/> |
| 204 | <xsd:choice minOccurs = "0" maxOccurs="1"> |
| 205 | <xsd:element ref = "CLI:ExecutionInstructions" minOccurs="1" maxOccurs="1"/> |
| 206 | <xsd:element ref = "MLI:ExecutionInstructions" minOccurs="1" maxOccurs="1"/> |
| 207 | </xsd:choice> |
| 208 | </xsd:sequence> |
| 209 | <xsd:attribute name = "isStreamAlgorithm" default = "false" use="optional" type = "xsd:boolean"> |
| 210 | <xsd:annotation> |
| 211 | <xsd:documentation>This is a stub for future development. The database location doesn't even exist yet. |
| 212 | If the output of the analysis will be the same when pixel positions are scrambled, the analysis is a stream algorithm. |
| 213 | Examples of stream algorithms are: |
| 214 | A statistics module that produces mean, geometric mean, standard deviation, etc. for pixel intensities. |
| 215 | A module to cross correlate pixel intensities across wavelengths. |
| 216 | Example of an algorithms that is not a stream algorithm is: |
| 217 | FindSpots. (It's a module to find blobs in an image.) |
| 218 | If a module is a stream algorithm, it can function across the x, y, z, and time dimensions. |
| 219 | Tied to DB. Table PROGRAMS Column IS_STREAM_ALGORITHM |
| 220 | </xsd:documentation> |
| 221 | </xsd:annotation> |
| 222 | </xsd:attribute> |
| 223 | <xsd:attribute name = "ModuleType" use = "required"> |
| 224 | <xsd:annotation> |
| 225 | <xsd:documentation>As more handlers, are added, this part of the schema needs to be changed |
| 226 | Tied to DB. Table PROGRAMS Column MODULE_TYPE |
| 227 | </xsd:documentation> |
| 228 | </xsd:annotation> |
| 229 | <xsd:simpleType> |
| 230 | <xsd:restriction base = "xsd:string"> |
| 231 | <xsd:pattern value = "OME::Analysis::.+"/> |
| 232 | </xsd:restriction> |
| 233 | </xsd:simpleType> |
| 234 | </xsd:attribute> |
| 235 | <xsd:attribute name = "RegionIterator" use="optional"> |
| 236 | <xsd:annotation> |
| 237 | <xsd:documentation>If the module iterates over a region, specify the iterator here. It will reference a region via the TAG column of the REGIONS table. |
| 238 | An example of a module that does not iterate over a region is Find Cells. It examines one image at a time, hence it iterates over an image, not a region. It produces zero or more regions (Ãell) per image. These Cell regions belong to an image. |
| 239 | This module would not get a RegionIterator attribute. |
| 240 | An example of a module that iterates over a region is Find Golgi. It examines one CELL at a time. A cell is a region, hence the module iterates over regions, not images or datasets. It produces zero or more Golgi regions per Cell region. These Golgi regions belong to a Cell region. |
| 241 | This module would get a RegionIterator attribute of "CELL". |
| 242 | Tied to DB. Table PROGRAMS Column DEFAULT_ITERATOR |
| 243 | </xsd:documentation> |
| 244 | </xsd:annotation> |
| 245 | <xsd:simpleType> |
| 246 | <xsd:restriction base = "xsd:string"> |
| 247 | <xsd:maxLength value = "128"/> |
| 248 | </xsd:restriction> |
| 249 | </xsd:simpleType> |
| 250 | </xsd:attribute> |
| 251 | <xsd:attribute name = "NewRegionName" use="optional"> |
| 252 | <xsd:annotation> |
| 253 | <xsd:documentation>If this module makes new regions, then the new Region's name needs to be specified here. |
| 254 | If the module does not make new regions, do not specify a value for this attribute. |
| 255 | Tied to DB. PROGRAMS.NEW_FEATURE_TAG |
| 256 | </xsd:documentation> |
| 257 | </xsd:annotation> |
| 258 | <xsd:simpleType> |
| 259 | <xsd:restriction base = "xsd:string"> |
| 260 | <xsd:maxLength value = "128"/> |
| 261 | </xsd:restriction> |
| 262 | </xsd:simpleType> |
| 263 | </xsd:attribute> |
| 264 | <xsd:attribute name = "Category" use="optional"> |
| 265 | <xsd:annotation> |
| 266 | <xsd:documentation>References a Category.</xsd:documentation> |
| 267 | </xsd:annotation> |
| 268 | <xsd:simpleType> |
| 269 | <xsd:restriction base = "xsd:string"> |
| 270 | <xsd:maxLength value = "32"/> |
| 271 | </xsd:restriction> |
| 272 | </xsd:simpleType> |
| 273 | </xsd:attribute> |
| 274 | <xsd:attribute name = "ProgramID" use = "required" type = "xsd:string"> |
| 275 | <xsd:annotation> |
| 276 | <xsd:documentation>Eventually will refer to a program. Currently program installation is NOT implemented. So this value is the path to the installed binary file. </xsd:documentation> |
| 277 | </xsd:annotation> |
| 278 | </xsd:attribute> |
| 279 | <xsd:attribute name = "ModuleName" use="optional"> |
| 280 | <xsd:simpleType> |
| 281 | <xsd:restriction base = "xsd:string"> |
| 282 | <xsd:maxLength value = "64"/> |
| 283 | </xsd:restriction> |
| 284 | </xsd:simpleType> |
| 285 | </xsd:attribute> |
| 286 | <xsd:attribute name = "ID" use = "required" type = "AML:ModuleID"/> |
| 287 | </xsd:complexType> |
| 288 | <xsd:unique name = "FormalInput"> |
| 289 | <xsd:selector xpath = "AML:Declaration/AML:FormalInput"/> |
| 290 | <xsd:field xpath = "@Name"/> |
| 291 | </xsd:unique> |
| 292 | <xsd:unique name = "FormalOutput"> |
| 293 | <xsd:selector xpath = "AML:Declaration/AML:FormalOutput"/> |
| 294 | <xsd:field xpath = "@Name"/> |
| 295 | </xsd:unique> |
| 296 | </xsd:element> |
| 297 | <xsd:element name = "InstallationScript"> <!-- top level definition --> |
| 298 | <xsd:annotation> |
| 299 | <xsd:documentation>The script should interface with the OME API to find all information it needs. (i.e. installation path) It also needs to set the location of the program after the program is installed. The location should be set through the API, but it will propagate to the LOCATION column of the PROGRAMS table.</xsd:documentation> |
| 300 | </xsd:annotation> |
| 301 | <xsd:complexType> |
| 302 | <xsd:sequence> |
| 303 | <xsd:element ref = "Bin:BinaryFile" minOccurs="1" maxOccurs="1"/> |
| 304 | </xsd:sequence> |
| 305 | </xsd:complexType> |
| 306 | </xsd:element> |
| 307 | <xsd:element name = "InstallationFile"> <!-- top level definition --> |
| 308 | <xsd:annotation> |
| 309 | <xsd:documentation>Contains a packaged or zipped installation files (binaries or source code).</xsd:documentation> |
| 310 | </xsd:annotation> |
| 311 | <xsd:complexType> |
| 312 | <xsd:sequence> |
| 313 | <xsd:element ref = "Bin:BinaryFile" minOccurs="1" maxOccurs="1"/> |
| 314 | </xsd:sequence> |
| 315 | <xsd:attribute name = "Format" use="optional" type = "xsd:string"> |
| 316 | <xsd:annotation> |
| 317 | <xsd:documentation>This is a stub for future development. Don't bother with it unless you know more about it. |
| 318 | Specifies the packaging and/or compression format of the Installation file. |
| 319 | </xsd:documentation> |
| 320 | </xsd:annotation> |
| 321 | </xsd:attribute> |
| 322 | </xsd:complexType> |
| 323 | </xsd:element> |
| 324 | <xsd:element name = "Installed"> <!-- top level definition --> |
| 325 | <xsd:complexType> |
| 326 | <xsd:attribute name = "location" use = "required" type = "xsd:string"/> |
| 327 | </xsd:complexType> |
| 328 | </xsd:element> |
| 329 | <xsd:element name = "Program"> <!-- top level definition --> |
| 330 | <xsd:annotation> |
| 331 | <xsd:documentation>Stores an installation package and installation script for a program. |
| 332 | This currently is NOT implemented. |
| 333 | </xsd:documentation> |
| 334 | </xsd:annotation> |
| 335 | <xsd:complexType> |
| 336 | <xsd:choice minOccurs="1" maxOccurs="1"> |
| 337 | <xsd:sequence> |
| 338 | <xsd:element ref = "AML:InstallationScript" minOccurs="1" maxOccurs="1"/> |
| 339 | <xsd:element ref = "AML:InstallationFile" minOccurs="1" maxOccurs="1"/> |
| 340 | </xsd:sequence> |
| 341 | <xsd:element ref = "AML:Installed" minOccurs="1" maxOccurs="1"/> |
| 342 | </xsd:choice> |
| 343 | <xsd:attribute name = "Name" use="optional"> |
| 344 | <xsd:annotation> |
| 345 | <xsd:documentation>Program name. |
| 346 | Unclear how this would be used. DB location PROGRAMS.PROGRAM_NAME is populated by XML attribute AnalysisModule.Name. |
| 347 | </xsd:documentation> |
| 348 | </xsd:annotation> |
| 349 | <xsd:simpleType> |
| 350 | <xsd:restriction base = "xsd:string"> |
| 351 | <xsd:maxLength value = "64"/> |
| 352 | </xsd:restriction> |
| 353 | </xsd:simpleType> |
| 354 | </xsd:attribute> |
| 355 | <xsd:attribute name = "Version" use="optional" type = "xsd:string"> |
| 356 | <xsd:annotation> |
| 357 | <xsd:documentation>Currently unused</xsd:documentation> |
| 358 | </xsd:annotation> |
| 359 | </xsd:attribute> |
| 360 | <xsd:attribute name = "ProgramID" use = "required" type = "xsd:string"/> |
| 361 | </xsd:complexType> |
| 362 | </xsd:element> |
| 363 | <xsd:element name = "AnalysisModuleLibrary"> <!-- top level definition --> |
| 364 | <xsd:annotation> |
| 365 | <xsd:documentation>An analysis module is defined by two things: |
| 366 | 1) A program |
| 367 | 2) An interface |
| 368 | A single program may have multiple interfaces. Why do you need multiple interfaces? |
| 369 | Pretend you have a program that calculates simple statistics on the pixels of an image. You can specify which statistics you want via parameters. |
| 370 | Typing |
| 371 | ./stats -mean -sigma image1 |
| 372 | will output |
| 373 | Image | mean | sigma |
| 374 | image1 12.4 1 |
| 375 | Typing |
| 376 | ./stats -geomean -mean image1 |
| 377 | will output |
| 378 | Image | geomean | mean |
| 379 | image1 12.2 12.4 |
| 380 | The outputs are completely different. You need to specify an interface for each of these behaviors. |
| 381 | Or pretend you have a powerful program that can do 10 unrelated tasks, each of which outputs an image. While the outputs are the same type and format, they represent 10 completely different things. In this case, it might make sense to define 10 corresponding AnalysisModule to represent the 10 logical functions. |
| 382 | In any case, use AnalysisModule to define an interface and Program to store installation software for a program. |
| 383 | </xsd:documentation> |
| 384 | </xsd:annotation> |
| 385 | <!-- |
| 386 | This was commented out by Josiah <siah@nih.gov> on July 3, 2003. |
| 387 | We don't support Program installation yet, and are using the value of ProgramID |
| 388 | in <AnalysisModule> to refer to the location of the installed program. |
| 389 | A temporary hack to be sure, but that's the way it works for now. |
| 390 | <keyref name = "ProgramRef" refer = "AML:Program"> |
| 391 | <selector xpath = "AML:AnalysisModule"/> |
| 392 | <field xpath = "@ProgramID"/> |
| 393 | </keyref> |
| 394 | <unique name = "Program"> |
| 395 | <selector xpath = "AML:Program"/> |
| 396 | <field xpath = "@ProgramID"/> |
| 397 | </unique> |
| 398 | --> |
| 399 | <xsd:complexType> |
| 400 | <xsd:sequence> |
| 401 | <xsd:element ref = "AML:AnalysisModule" minOccurs="1" maxOccurs = "unbounded"/> |
| 402 | <xsd:element ref = "AML:Category" minOccurs = "0" maxOccurs = "unbounded"/> |
| 403 | <xsd:element ref = "AML:Program" minOccurs = "0" maxOccurs = "unbounded"/> |
| 404 | </xsd:sequence> |
| 405 | </xsd:complexType> |
| 406 | <xsd:unique name = "AnalysisModule"> |
| 407 | <xsd:selector xpath = "AML:AnalysisModule"/> |
| 408 | <xsd:field xpath = "@AML:ModuleName"/> |
| 409 | </xsd:unique> |
| 410 | </xsd:element> |
| 411 | <xsd:simpleType name = "Hex40"> |
| 412 | <xsd:restriction base = "xsd:hexBinary"> |
| 413 | <xsd:length value = "20"/> |
| 414 | </xsd:restriction> |
| 415 | </xsd:simpleType> |
| 416 | <xsd:simpleType name = "ModuleID"> |
| 417 | <xsd:restriction base = "OME:LSID"> |
| 418 | <xsd:pattern value = "(urn:lsid:([\w\-\.]+\.[\w\-\.]+)+:Module:\S+)|(Module:\S+)"/> |
| 419 | </xsd:restriction> |
| 420 | </xsd:simpleType> |
| 421 | <xsd:element name = "Category"> <!-- top level definition --> |
| 422 | <xsd:complexType> |
| 423 | <xsd:sequence> |
| 424 | <xsd:element ref = "OME:Description" minOccurs="1" maxOccurs="1"/> |
| 425 | </xsd:sequence> |
| 426 | <xsd:attribute name = "Path" use = "required"> |
| 427 | <xsd:annotation> |
| 428 | <xsd:documentation>Categories are organized into hierarchical structures. This specifies the full path of this category in the following format. |
| 429 | Path = "GrandParent name.Parent name.Category name" |
| 430 | If you defined a sub category, we Strongly encourage you to also define all ancestor categories that are not part of the core OME specification. |
| 431 | </xsd:documentation> |
| 432 | </xsd:annotation> |
| 433 | <xsd:simpleType> |
| 434 | <xsd:restriction base = "xsd:string"> |
| 435 | <xsd:pattern value = "^[A-Za-z0-9 ]+(\.[A-Za-z0-9 ]+)*$"/> |
| 436 | </xsd:restriction> |
| 437 | </xsd:simpleType> |
| 438 | </xsd:attribute> |
| 439 | </xsd:complexType> |
| 440 | </xsd:element> |
| 441 | </xsd:schema> |
Note: See TracBrowser
for help on using the browser.
