diff --git a/specification/samples/2013-06/transformations-downgrade.ome.xml b/specification/samples/2013-06/transformations-downgrade.ome.xml index a9bdb5ea3..70dc72e47 100644 --- a/specification/samples/2013-06/transformations-downgrade.ome.xml +++ b/specification/samples/2013-06/transformations-downgrade.ome.xml @@ -26,7 +26,7 @@ A description for my group. - Complete with basic formating, like new lines. + Complete with basic formatting, like new lines. diff --git a/specification/samples/2015-01/transformations-downgrade.ome.xml b/specification/samples/2015-01/transformations-downgrade.ome.xml index 8ed7438a7..d583c6053 100644 --- a/specification/samples/2015-01/transformations-downgrade.ome.xml +++ b/specification/samples/2015-01/transformations-downgrade.ome.xml @@ -26,7 +26,7 @@ - A description for my group. Complete with basic formating, like new + A description for my group. Complete with basic formatting, like new lines. diff --git a/specification/samples/2016-06/transformations-downgrade.ome.xml b/specification/samples/2016-06/transformations-downgrade.ome.xml index 5693bd2fa..85300505b 100644 --- a/specification/samples/2016-06/transformations-downgrade.ome.xml +++ b/specification/samples/2016-06/transformations-downgrade.ome.xml @@ -21,7 +21,7 @@ - A description for my group. Complete with basic formating, like new + A description for my group. Complete with basic formatting, like new lines. diff --git a/specification/src/main/java/ome/specification/SchemaResolver.java b/specification/src/main/java/ome/specification/SchemaResolver.java index f3ebfd95a..6bbb91902 100644 --- a/specification/src/main/java/ome/specification/SchemaResolver.java +++ b/specification/src/main/java/ome/specification/SchemaResolver.java @@ -96,7 +96,7 @@ public SchemaResolver() throws InstantiationException } } - // if verson 4 & 5 ? + // if version 4 & 5 ? if (theDOMImplementationLS == null) { try { System.setProperty( diff --git a/specification/src/main/resources/released-schema/2003-FC/AnalysisModule.xsd b/specification/src/main/resources/released-schema/2003-FC/AnalysisModule.xsd index 8259d2354..d3c893bfe 100644 --- a/specification/src/main/resources/released-schema/2003-FC/AnalysisModule.xsd +++ b/specification/src/main/resources/released-schema/2003-FC/AnalysisModule.xsd @@ -85,7 +85,7 @@ - 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 intrisic 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. + 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. @@ -303,7 +303,7 @@ Tied to DB. PROGRAMS.NEW_FEATURE_TAG - 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 propogate to the LOCATION column of the PROGRAMS table. + 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. @@ -376,7 +376,7 @@ A single program may have multiple interfaces. Why do you need multiple interfac Pretend you have a program that calculates simple statistics on the pixels of an image. You can specify which statistics you want via parameters. Typing ./stats -mean -sigma image1 -will ouput +will output Image | mean | sigma image1 12.4 1 Typing @@ -385,7 +385,7 @@ will output Image | geomean | mean image1 12.2 12.4 The outputs are completely different. You need to specify an interface for each of these behaviors. -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 corrosponding AnalysisModule to represent the 10 logical functions. +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. In any case, use AnalysisModule to define an interface and Program to store installation software for a program. @@ -445,7 +445,7 @@ A temporary hack to be sure, but that's the way it works for now. - Categories are organized into heirarchical structures. This specifies the full path of this category in the following format. + Categories are organized into hierarchical structures. This specifies the full path of this category in the following format. Path = "GrandParent name.Parent name.Category name" 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. diff --git a/specification/src/main/resources/released-schema/2003-FC/BinaryFile.xsd b/specification/src/main/resources/released-schema/2003-FC/BinaryFile.xsd index d8b918a10..83814d2db 100644 --- a/specification/src/main/resources/released-schema/2003-FC/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2003-FC/BinaryFile.xsd @@ -34,7 +34,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2003-FC/CLI.xsd b/specification/src/main/resources/released-schema/2003-FC/CLI.xsd index ea36bdf44..4a2ebcee9 100644 --- a/specification/src/main/resources/released-schema/2003-FC/CLI.xsd +++ b/specification/src/main/resources/released-schema/2003-FC/CLI.xsd @@ -229,8 +229,8 @@ Currently, only native image pixels are supported. Specifies the expected format of the plane. -RAW corrosponds to OME repository format of pixel dump. -TIFF corrosponds to TIFF files. +RAW corresponds to OME repository format of pixel dump. +TIFF corresponds to TIFF files. Currently only TIFF is supported. @@ -308,14 +308,14 @@ e.g. /OME/repository/1-tinyTest.ori RepeatCount specifies how many times to read a record. If it is not specified, reading will continue until it reaches the end of the output stream. -If used in conjuction with TerminateAt, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with TerminateAt, reading will stop after RepeatCount or TerminateAt, whichever comes first. TerminateAt specifies a regular expression. When a match to this is found, reading will stop. -If used in conjuction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. @@ -422,7 +422,7 @@ This means a stack statistics record that specifies theC as an index before theT - Use this to construct a Delimited Record. (i.e. tab delimitted, comma delimitted, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. + Use this to construct a Delimited Record. (i.e. tab delimited, comma delimited, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. @@ -435,7 +435,7 @@ This means a stack statistics record that specifies theC as an index before theT - This will be used to separate Records. Defaults to a newline (a newline as interpretted by perl). + This will be used to separate Records. Defaults to a newline (a newline as interpreted by perl). @@ -484,7 +484,7 @@ This means a stack statistics record that specifies theC as an index before theT Allows SemanticTypes Pixels and PixelsPlane to be outputs. The subelements specify locations for the population of data. This data population is useful for a Plane projection algorithm that has the same X and Y dimensions as the Pixels it is operating on. -Alternately, these fields may be filled by ouput from STDOUT. +Alternately, these fields may be filled by output from STDOUT. The FileSHA1 subelement is automatically calculated for the pixel dump file. diff --git a/specification/src/main/resources/released-schema/2003-FC/MLI.xsd b/specification/src/main/resources/released-schema/2003-FC/MLI.xsd index eeff890d9..5bb4e29eb 100644 --- a/specification/src/main/resources/released-schema/2003-FC/MLI.xsd +++ b/specification/src/main/resources/released-schema/2003-FC/MLI.xsd @@ -82,7 +82,7 @@ Will pass a numeric matrix into the function. -Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. +Translates a module input of Semantic Type Pixels (or any pseudo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. @@ -126,7 +126,7 @@ In the future, can be used to establish references. - Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value" + Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic element name. i.e. "Texture Direction.Direction_Value" @@ -139,7 +139,7 @@ In the future, can be used to establish references. - Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. + Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any pseudo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. @@ -157,7 +157,7 @@ In the future, can be used to stitch together data from different function outpu Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME Type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME Type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -183,7 +183,7 @@ Note to perl developers: This list should stay syncronized with the Matlab Class - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" @@ -237,12 +237,12 @@ The contents of this element should follow CustomAttribute syntax and convention - Maps a location on the Vector to an output data location. Can be used in conjuction with Templates. + Maps a location on the Vector to an output data location. Can be used in conjunction with Templates. - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" diff --git a/specification/src/main/resources/released-schema/2003-FC/STD.xsd b/specification/src/main/resources/released-schema/2003-FC/STD.xsd index b5bf512b7..187458eda 100644 --- a/specification/src/main/resources/released-schema/2003-FC/STD.xsd +++ b/specification/src/main/resources/released-schema/2003-FC/STD.xsd @@ -82,7 +82,7 @@ to RC4 to reflect these changes. Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2003-FC/ome.xsd b/specification/src/main/resources/released-schema/2003-FC/ome.xsd index 885181b9d..321eababd 100644 --- a/specification/src/main/resources/released-schema/2003-FC/ome.xsd +++ b/specification/src/main/resources/released-schema/2003-FC/ome.xsd @@ -59,7 +59,7 @@ - The OME element is a container for all information objects acessible by OME. These information objects include descriptions of the imaging experiments + The OME element is a container for all information objects accessible by OME. These information objects include descriptions of the imaging experiments and the people who perform them, descriptions of the microscope, the resulting images and how they were acquired, the analyses performed on those images, and the analysis results themselves. An OME file may contain any or all of this information. @@ -288,7 +288,7 @@ is not specified, then the FIRST <Pixels> element under <Image> will be as This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. @@ -1293,7 +1293,7 @@ is not specified, then the FIRST <Pixels> element under <Image> will be as The optical transfer function. Filter ID refers to the set of filters used in computing the OTF. BitsPerPixel is an integer '1', '8', '16'. - The OpticalAxisAvg is a boolean specifying wether or not optical axis averaging was done. + The OpticalAxisAvg is a boolean specifying whether or not optical axis averaging was done. SizeX, SizeY specify the width and height of the OTF. This element must contain a BinData element containing the Base64-encoded OTF. Both of these work the same way as they do for the Data element within Image. @@ -1319,7 +1319,7 @@ is not specified, then the FIRST <Pixels> element under <Image> will be as Images can belong to more than one Dataset, and a Dataset may contain more than one Image. Images contain one or more DatasetRef elements to specify what datasets they belong to. Once a Dataset has been processed in any way, its collection of images cannot be altered. - Wether or not the list of Images in this dataset can be altered is specified by the Locked attribute. + Whether or not the list of Images in this dataset can be altered is specified by the Locked attribute. The ExperimenterRef and GroupRef elements specify the person and group this Dataset belongs to. Projects may contain one or more Datasets, and Datasets may belong to one or more Projects. This relationship is specified by listing ProjectRef elements within the Dataset element. @@ -1404,7 +1404,7 @@ is not specified, then the FIRST <Pixels> element under <Image> will be as Laser types are specified using two attributes - the Type and the lasing medium (Medium). Type is a string which may be set to: 'Excimer','Gas','Metal Vapor','Solid State','Dye','Semiconductor', or 'Free Electron'. The Medium attribute specifies the actual lasing medium - for a given laser type (for example, 'Nd-YAG'). Additionally, the Wavelength (in nm), wether or not the laser is FrequencyDoubled or Tunable may be specified. + for a given laser type (for example, 'Nd-YAG'). Additionally, the Wavelength (in nm), whether or not the laser is FrequencyDoubled or Tunable may be specified. The Pulse attribute can be set to 'CW' (Continuous Wave),','Single','Q-Switched','Repetitive','Mode-Locked'. The Power attribute specifies the nominal laser power in watts. The Laser element may contain a Pump sub-element which refers to a LightSource used as a laser pump. diff --git a/specification/src/main/resources/released-schema/2003-IR2/MLI.xsd b/specification/src/main/resources/released-schema/2003-IR2/MLI.xsd index eeff890d9..5bb4e29eb 100644 --- a/specification/src/main/resources/released-schema/2003-IR2/MLI.xsd +++ b/specification/src/main/resources/released-schema/2003-IR2/MLI.xsd @@ -82,7 +82,7 @@ Will pass a numeric matrix into the function. -Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. +Translates a module input of Semantic Type Pixels (or any pseudo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. @@ -126,7 +126,7 @@ In the future, can be used to establish references. - Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value" + Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic element name. i.e. "Texture Direction.Direction_Value" @@ -139,7 +139,7 @@ In the future, can be used to establish references. - Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. + Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any pseudo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. @@ -157,7 +157,7 @@ In the future, can be used to stitch together data from different function outpu Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME Type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME Type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -183,7 +183,7 @@ Note to perl developers: This list should stay syncronized with the Matlab Class - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" @@ -237,12 +237,12 @@ The contents of this element should follow CustomAttribute syntax and convention - Maps a location on the Vector to an output data location. Can be used in conjuction with Templates. + Maps a location on the Vector to an output data location. Can be used in conjunction with Templates. - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" diff --git a/specification/src/main/resources/released-schema/2003-IR3/AnalysisModule.xsd b/specification/src/main/resources/released-schema/2003-IR3/AnalysisModule.xsd index cef46e0e1..93e1abaea 100644 --- a/specification/src/main/resources/released-schema/2003-IR3/AnalysisModule.xsd +++ b/specification/src/main/resources/released-schema/2003-IR3/AnalysisModule.xsd @@ -39,7 +39,7 @@ These are given by <RawImageFilePath>, <sizeX>, <sizeY>, <sizeZ>, &l - 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 intrisic 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. + 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. @@ -233,7 +233,7 @@ Pretend you have a program that calculates simple statistics on the pixels of an Typing ./stats -mean -sigma image1 -will ouput +will output Image | mean | sigma image1 12.4 1 @@ -245,7 +245,7 @@ Image | geomean | mean image1 12.2 12.4 The outputs are completely different. You need to specify an interface for each of these behaviors. -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 corrosponding AnalysisModule to represent the 10 logical functions. +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. In any case, use AnalysisModule to define an interface and Program to store installation software for a program. @@ -336,7 +336,7 @@ Tied to DB. Table PROGRAMS Column MODULE_TYPE - Used to reference a Program Element. It should corrospond to a ProgramID specified in a Program Element. + Used to reference a Program Element. It should correspond to a ProgramID specified in a Program Element. Referential integrity is not enforced by this schema. That is, verification against the schema will not detect an error here if you make a typo. @@ -466,7 +466,7 @@ Unclear how this would be used. DB location PROGRAMS.PROGRAM_NAME is populated b - 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 propogate to the LOCATION column of the PROGRAMS table. + 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. @@ -553,7 +553,7 @@ Restrictions: Every SemanticElement must be in the same table. Notes: -Granularity is infered from granularity of table. +Granularity is inferred from granularity of table. diff --git a/specification/src/main/resources/released-schema/2003-RC1/AnalysisModule.xsd b/specification/src/main/resources/released-schema/2003-RC1/AnalysisModule.xsd index 25cb7d705..c39b32f5d 100644 --- a/specification/src/main/resources/released-schema/2003-RC1/AnalysisModule.xsd +++ b/specification/src/main/resources/released-schema/2003-RC1/AnalysisModule.xsd @@ -85,7 +85,7 @@ - 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 intrisic 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. + 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. @@ -303,7 +303,7 @@ Tied to DB. PROGRAMS.NEW_FEATURE_TAG - 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 propogate to the LOCATION column of the PROGRAMS table. + 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. @@ -376,7 +376,7 @@ A single program may have multiple interfaces. Why do you need multiple interfac Pretend you have a program that calculates simple statistics on the pixels of an image. You can specify which statistics you want via parameters. Typing ./stats -mean -sigma image1 -will ouput +will output Image | mean | sigma image1 12.4 1 Typing @@ -385,7 +385,7 @@ will output Image | geomean | mean image1 12.2 12.4 The outputs are completely different. You need to specify an interface for each of these behaviors. -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 corrosponding AnalysisModule to represent the 10 logical functions. +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. In any case, use AnalysisModule to define an interface and Program to store installation software for a program. @@ -445,7 +445,7 @@ A temporary hack to be sure, but that's the way it works for now. - Categories are organized into heirarchical structures. This specifies the full path of this category in the following format. + Categories are organized into hierarchical structures. This specifies the full path of this category in the following format. Path = "GrandParent name.Parent name.Category name" 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. diff --git a/specification/src/main/resources/released-schema/2003-RC1/BinaryFile.xsd b/specification/src/main/resources/released-schema/2003-RC1/BinaryFile.xsd index e1d21ab82..79c204beb 100644 --- a/specification/src/main/resources/released-schema/2003-RC1/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2003-RC1/BinaryFile.xsd @@ -34,7 +34,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2003-RC1/CLI.xsd b/specification/src/main/resources/released-schema/2003-RC1/CLI.xsd index ea36bdf44..4a2ebcee9 100644 --- a/specification/src/main/resources/released-schema/2003-RC1/CLI.xsd +++ b/specification/src/main/resources/released-schema/2003-RC1/CLI.xsd @@ -229,8 +229,8 @@ Currently, only native image pixels are supported. Specifies the expected format of the plane. -RAW corrosponds to OME repository format of pixel dump. -TIFF corrosponds to TIFF files. +RAW corresponds to OME repository format of pixel dump. +TIFF corresponds to TIFF files. Currently only TIFF is supported. @@ -308,14 +308,14 @@ e.g. /OME/repository/1-tinyTest.ori RepeatCount specifies how many times to read a record. If it is not specified, reading will continue until it reaches the end of the output stream. -If used in conjuction with TerminateAt, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with TerminateAt, reading will stop after RepeatCount or TerminateAt, whichever comes first. TerminateAt specifies a regular expression. When a match to this is found, reading will stop. -If used in conjuction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. @@ -422,7 +422,7 @@ This means a stack statistics record that specifies theC as an index before theT - Use this to construct a Delimited Record. (i.e. tab delimitted, comma delimitted, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. + Use this to construct a Delimited Record. (i.e. tab delimited, comma delimited, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. @@ -435,7 +435,7 @@ This means a stack statistics record that specifies theC as an index before theT - This will be used to separate Records. Defaults to a newline (a newline as interpretted by perl). + This will be used to separate Records. Defaults to a newline (a newline as interpreted by perl). @@ -484,7 +484,7 @@ This means a stack statistics record that specifies theC as an index before theT Allows SemanticTypes Pixels and PixelsPlane to be outputs. The subelements specify locations for the population of data. This data population is useful for a Plane projection algorithm that has the same X and Y dimensions as the Pixels it is operating on. -Alternately, these fields may be filled by ouput from STDOUT. +Alternately, these fields may be filled by output from STDOUT. The FileSHA1 subelement is automatically calculated for the pixel dump file. diff --git a/specification/src/main/resources/released-schema/2003-RC1/STD.xsd b/specification/src/main/resources/released-schema/2003-RC1/STD.xsd index f64e314fc..e5978bc30 100644 --- a/specification/src/main/resources/released-schema/2003-RC1/STD.xsd +++ b/specification/src/main/resources/released-schema/2003-RC1/STD.xsd @@ -125,7 +125,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2003-RC2/STD.xsd b/specification/src/main/resources/released-schema/2003-RC2/STD.xsd index b5bf512b7..187458eda 100644 --- a/specification/src/main/resources/released-schema/2003-RC2/STD.xsd +++ b/specification/src/main/resources/released-schema/2003-RC2/STD.xsd @@ -82,7 +82,7 @@ to RC4 to reflect these changes. Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2003-RC2/ome.xsd b/specification/src/main/resources/released-schema/2003-RC2/ome.xsd index dde30b49b..c97084c55 100644 --- a/specification/src/main/resources/released-schema/2003-RC2/ome.xsd +++ b/specification/src/main/resources/released-schema/2003-RC2/ome.xsd @@ -283,7 +283,7 @@ This is also not correctly specified in the schema (FIXME?) This specifies mapping of pixels to RGB or greyscale colorspace with one byte per pixel per channel. Elements of type WaveScaleType specify the scaling of pixel values to colorspace values. These elements are empty, and have 3-4 attributes: WaveNumber, Threshold, Clip and optional Scale. -The WaveNumber specifies the wavenumber of the color chanel. Pixel values between Threshold and Clip will be assigned values 0-255, respectively. +The WaveNumber specifies the wavenumber of the color channel. Pixel values between Threshold and Clip will be assigned values 0-255, respectively. Values below Threshold or above Clip will be assigned 0 and 255 respectively. Either the GreyWave or one or more of RedWave, GreenWave, BlueWave must be specified. The Projection element specifies that the display is a maximum intensity projection. @@ -384,7 +384,7 @@ The Filters element is composed either of separate excitation and emission filte The StageLabel is simply a string to describe a particular stage position. -This is usefull for experiments involving visiting several points on a slide over a timecourse. +This is useful for experiments involving visiting several points on a slide over a timecourse. @@ -518,7 +518,7 @@ a filter set specified by FilterSet. All elements are ManufactSpec type, so the - The numerical apperture of the lens. + The numerical aperture of the lens. diff --git a/specification/src/main/resources/released-schema/2003-RC3/STD.xsd b/specification/src/main/resources/released-schema/2003-RC3/STD.xsd index 2dfe8db69..6a3474ce4 100644 --- a/specification/src/main/resources/released-schema/2003-RC3/STD.xsd +++ b/specification/src/main/resources/released-schema/2003-RC3/STD.xsd @@ -70,7 +70,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2003-RC3/ome.xsd b/specification/src/main/resources/released-schema/2003-RC3/ome.xsd index 5111518ec..f95bdf6d4 100644 --- a/specification/src/main/resources/released-schema/2003-RC3/ome.xsd +++ b/specification/src/main/resources/released-schema/2003-RC3/ome.xsd @@ -455,7 +455,7 @@ The OTF element contains an optical transfer function. The same OTF can be used for all wavelengths, or there may be one per wavelength. There may be multiple light sources, cameras and filters on a microscope. - Each of these has their own ID attribute, which can be refered to from WavelengthInfo. + Each of these has their own ID attribute, which can be referred to from WavelengthInfo. It is understood that the light path configuration can be different for each wavelength, but cannot be different for each timepoint or each plane of an XYZ stack. @@ -476,7 +476,7 @@ The StageLabel is simply a string to describe a particular stage position. - This is usefull for experiments involving visiting several points on a slide over a timecourse. + This is useful for experiments involving visiting several points on a slide over a timecourse. @@ -537,7 +537,7 @@ The Screen element may contain an ExternalRef attribute that refers to an external database. A description of the screen may be specified in the Description element. Screens may contain overlapping sets of Plates i.e. Screens and Plates have a many-to-many relationship. - Plates contain one or more ScreenRef elemnts to specify what screens they belong to. + Plates contain one or more ScreenRef elements to specify what screens they belong to. @@ -969,7 +969,7 @@ The lightsource for the instrument. An instrument may have several light sources. The type of lightsource is specified by the Type attribute, which is currently unrestricted. If several lightsources are specified for an instrument, the LightSourceID must be specified for each, - and the individual lightsources can be refered to through their LightSourceIDs. + and the individual lightsources can be referred to through their LightSourceIDs. @@ -986,7 +986,7 @@ The optical transfer function. FilterID refers to the set of filters used in computing the OTF. BitsPerPixel is an integer '1', '8', '16'. - The OpticalAxisAvg is a boolean specifying wether or not optical axis averaging was done. + The OpticalAxisAvg is a boolean specifying whether or not optical axis averaging was done. SizeX, SizeY specify the width and height of the OTF. This element must contain either an External element or a BinData element. Both of these work the same way as they do for the Data element within Image. @@ -1020,7 +1020,7 @@ Images can belong to more than one Dataset, and a Dataset may contain more than one Image. Images contain one or more DatasetRef elements to specify what datasets they belong to. Once a Dataset has been processed in any way, its collection of images cannot be altered. - Wether or not the list of Images in this dataset can be altered is specified by the Locked attribute. + Whether or not the list of Images in this dataset can be altered is specified by the Locked attribute. The ExperimenterRef and GroupRef elements specify the person and group this Dataset belongs to. Projects may contain one or more Datasets, and Datasets may belong to one or more Projects. This relationship is specified by listing ProjectRef elements within the Dataset element. @@ -1072,7 +1072,7 @@ - The DocumentRef element referes to an external OME XML document using the href and SHA1 attributes. + The DocumentRef element refers to an external OME XML document using the href and SHA1 attributes. diff --git a/specification/src/main/resources/released-schema/2003-RC4/STD.xsd b/specification/src/main/resources/released-schema/2003-RC4/STD.xsd index b5bf512b7..187458eda 100644 --- a/specification/src/main/resources/released-schema/2003-RC4/STD.xsd +++ b/specification/src/main/resources/released-schema/2003-RC4/STD.xsd @@ -82,7 +82,7 @@ to RC4 to reflect these changes. Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2003-RC4/ome.xsd b/specification/src/main/resources/released-schema/2003-RC4/ome.xsd index df60fab81..a195c69a8 100644 --- a/specification/src/main/resources/released-schema/2003-RC4/ome.xsd +++ b/specification/src/main/resources/released-schema/2003-RC4/ome.xsd @@ -381,7 +381,7 @@ The OTF element contains an optical transfer function. The same OTF can be used for all wavelengths, or there may be one per wavelength. There may be multiple light sources, cameras and filters on a microscope. - Each of these has their own ID attribute, which can be refered to from WavelengthInfo. + Each of these has their own ID attribute, which can be referred to from WavelengthInfo. It is understood that the light path configuration can be different for each wavelength, but cannot be different for each timepoint or each plane of an XYZ stack. @@ -402,7 +402,7 @@ The StageLabel is simply a string to describe a particular stage position. - This is usefull for experiments involving visiting several points on a slide over a timecourse. + This is useful for experiments involving visiting several points on a slide over a timecourse. @@ -463,7 +463,7 @@ The Screen element may contain an ExternalRef attribute that refers to an external database. A description of the screen may be specified in the Description element. Screens may contain overlapping sets of Plates i.e. Screens and Plates have a many-to-many relationship. - Plates contain one or more ScreenRef elemnts to specify what screens they belong to. + Plates contain one or more ScreenRef elements to specify what screens they belong to. @@ -892,7 +892,7 @@ An element type specifying a filter specification. - Unlike the ManufactSpec, filters are refered to by lot number rather than serial number. + Unlike the ManufactSpec, filters are referred to by lot number rather than serial number. @@ -905,7 +905,7 @@ The lightsource for the instrument. An instrument may have several light sources. The type of lightsource is specified by the Type attribute, which is currently unrestricted. If several lightsources are specified for an instrument, the LightSourceID must be specified for each, - and the individual lightsources can be refered to through their LightSourceIDs. + and the individual lightsources can be referred to through their LightSourceIDs. @@ -922,7 +922,7 @@ The optical transfer function. FilterID refers to the set of filters used in computing the OTF. BitsPerPixel is an integer '1', '8', '16'. - The OpticalAxisAvg is a boolean specifying wether or not optical axis averaging was done. + The OpticalAxisAvg is a boolean specifying whether or not optical axis averaging was done. SizeX, SizeY specify the width and height of the OTF. This element must contain either an External element or a BinData element. Both of these work the same way as they do for the Data element within Image. @@ -957,7 +957,7 @@ Images can belong to more than one Dataset, and a Dataset may contain more than one Image. Images contain one or more DatasetRef elements to specify what datasets they belong to. Once a Dataset has been processed in any way, its collection of images cannot be altered. - Wether or not the list of Images in this dataset can be altered is specified by the Locked attribute. + Whether or not the list of Images in this dataset can be altered is specified by the Locked attribute. The ExperimenterRef and GroupRef elements specify the person and group this Dataset belongs to. Projects may contain one or more Datasets, and Datasets may belong to one or more Projects. This relationship is specified by listing ProjectRef elements within the Dataset element. @@ -1010,7 +1010,7 @@ - The DocumentRef element referes to an external OME XML document using the href and SHA1 attributes. + The DocumentRef element refers to an external OME XML document using the href and SHA1 attributes. @@ -1032,7 +1032,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from granularity of record derives from. + Granularity of SemanticType is inferred from granularity of record derives from. @@ -1158,7 +1158,7 @@ - Any custom image attributes belong here. Data definitions for these attributes belong in DataDefinitions. Custom Attributes are stored in a record based format where one element corrosponds to one record. Attributes of an element corrospond to fields of the record. + Any custom image attributes belong here. Data definitions for these attributes belong in DataDefinitions. Custom Attributes are stored in a record based format where one element corresponds to one record. Attributes of an element correspond to fields of the record. diff --git a/specification/src/main/resources/released-schema/2003-RC5/ome.xsd b/specification/src/main/resources/released-schema/2003-RC5/ome.xsd index ebe282521..0902e3bd1 100644 --- a/specification/src/main/resources/released-schema/2003-RC5/ome.xsd +++ b/specification/src/main/resources/released-schema/2003-RC5/ome.xsd @@ -188,7 +188,7 @@ This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. @@ -1146,7 +1146,7 @@ The optical transfer function. FilterID refers to the set of filters used in computing the OTF. BitsPerPixel is an integer '1', '8', '16'. - The OpticalAxisAvg is a boolean specifying wether or not optical axis averaging was done. + The OpticalAxisAvg is a boolean specifying whether or not optical axis averaging was done. SizeX, SizeY specify the width and height of the OTF. This element must contain either an External element or a BinData element. Both of these work the same way as they do for the Data element within Image. @@ -1186,7 +1186,7 @@ Images can belong to more than one Dataset, and a Dataset may contain more than one Image. Images contain one or more DatasetRef elements to specify what datasets they belong to. Once a Dataset has been processed in any way, its collection of images cannot be altered. - Wether or not the list of Images in this dataset can be altered is specified by the Locked attribute. + Whether or not the list of Images in this dataset can be altered is specified by the Locked attribute. The ExperimenterRef and GroupRef elements specify the person and group this Dataset belongs to. Projects may contain one or more Datasets, and Datasets may belong to one or more Projects. This relationship is specified by listing ProjectRef elements within the Dataset element. diff --git a/specification/src/main/resources/released-schema/2003-RC6/ome.xsd b/specification/src/main/resources/released-schema/2003-RC6/ome.xsd index 1227e8509..334370605 100644 --- a/specification/src/main/resources/released-schema/2003-RC6/ome.xsd +++ b/specification/src/main/resources/released-schema/2003-RC6/ome.xsd @@ -42,7 +42,7 @@ - The OME element is a container for all information objects acessible by OME. These information objects include descriptions of the imaging experiments + The OME element is a container for all information objects accessible by OME. These information objects include descriptions of the imaging experiments and the people who perform them, descriptions of the microscope, the resulting images and how they were acquired, the analyses performed on those images, and the analysis results themselves. An OME file may contain any or all of this information, and this information may be distributed among several OME documents. @@ -180,7 +180,7 @@ This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. @@ -1178,7 +1178,7 @@ The optical transfer function. FilterID refers to the set of filters used in computing the OTF. BitsPerPixel is an integer '1', '8', '16'. - The OpticalAxisAvg is a boolean specifying wether or not optical axis averaging was done. + The OpticalAxisAvg is a boolean specifying whether or not optical axis averaging was done. SizeX, SizeY specify the width and height of the OTF. This element must contain either an External element or a BinData element. Both of these work the same way as they do for the Data element within Image. @@ -1207,7 +1207,7 @@ Images can belong to more than one Dataset, and a Dataset may contain more than one Image. Images contain one or more DatasetRef elements to specify what datasets they belong to. Once a Dataset has been processed in any way, its collection of images cannot be altered. - Wether or not the list of Images in this dataset can be altered is specified by the Locked attribute. + Whether or not the list of Images in this dataset can be altered is specified by the Locked attribute. The ExperimenterRef and GroupRef elements specify the person and group this Dataset belongs to. Projects may contain one or more Datasets, and Datasets may belong to one or more Projects. This relationship is specified by listing ProjectRef elements within the Dataset element. @@ -1326,7 +1326,7 @@ This can be null if a channel maps to a logical channel but is not included in t Laser types are specified using two attributes - the Type and the lasing medium (Medium). Type is a string which may be set to: 'Excimer','Gas','Metal Vapor','Solid State','Dye','Semiconductor', or 'Free Electron'. The Medium attribute specifies the actual lasing medium - for a given laser type (for example, 'Nd-YAG'). Additionally, the Wavelength (in nm), wether or not the laser is FrequencyDoubled or Tunable may be specified. + for a given laser type (for example, 'Nd-YAG'). Additionally, the Wavelength (in nm), whether or not the laser is FrequencyDoubled or Tunable may be specified. The Pulse attribute can be set to 'CW' (Continuous Wave),','Single','Q-Switched','Repetitive','Mode-Locked'. The Power attribute specifies the nominal laser power in watts. The Laser element may contain Pump sub-elements which refer to a LightSource used as a laser pump. diff --git a/specification/src/main/resources/released-schema/2007-06/BinaryFile.xsd b/specification/src/main/resources/released-schema/2007-06/BinaryFile.xsd index fccae2106..06b2581c8 100644 --- a/specification/src/main/resources/released-schema/2007-06/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2007-06/BinaryFile.xsd @@ -39,7 +39,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2007-06/CLI.xsd b/specification/src/main/resources/released-schema/2007-06/CLI.xsd index 59fa12721..1220d73a2 100644 --- a/specification/src/main/resources/released-schema/2007-06/CLI.xsd +++ b/specification/src/main/resources/released-schema/2007-06/CLI.xsd @@ -305,7 +305,7 @@ If used in conjunction with TerminateAt, reading will stop after RepeatCount or TerminateAt specifies a regular expression. When a match to this is found, reading will stop. -If used in conjuction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. @@ -412,7 +412,7 @@ This means a stack statistics record that specifies theC as an index before theT - Use this to construct a Delimited Record. (i.e. tab delimitted, comma delimitted, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. + Use this to construct a Delimited Record. (i.e. tab delimited, comma delimited, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. @@ -425,7 +425,7 @@ This means a stack statistics record that specifies theC as an index before theT - This will be used to separate Records. Defaults to a newline (a newline as interpretted by perl). + This will be used to separate Records. Defaults to a newline (a newline as interpreted by perl). @@ -474,7 +474,7 @@ This means a stack statistics record that specifies theC as an index before theT Allows SemanticTypes Pixels and PixelsPlane to be outputs. The subelements specify locations for the population of data. This data population is useful for a Plane projection algorithm that has the same X and Y dimensions as the Pixels it is operating on. -Alternately, these fields may be filled by ouput from STDOUT. +Alternately, these fields may be filled by output from STDOUT. The FileSHA1 subelement is automatically calculated for the pixel dump file. diff --git a/specification/src/main/resources/released-schema/2007-06/MLI.xsd b/specification/src/main/resources/released-schema/2007-06/MLI.xsd index 6befa5d11..248216a27 100644 --- a/specification/src/main/resources/released-schema/2007-06/MLI.xsd +++ b/specification/src/main/resources/released-schema/2007-06/MLI.xsd @@ -84,7 +84,7 @@ Will pass a numeric matrix into the function. -Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. +Translates a module input of Semantic Type Pixels (or any pseudo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. @@ -129,7 +129,7 @@ In the future, can be used to establish references. - Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value" + Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic element name. i.e. "Texture Direction.Direction_Value" @@ -171,7 +171,7 @@ In the future, can be used to establish references. - Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. + Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any pseudo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. @@ -189,7 +189,7 @@ In the future, can be used to stitch together data from different function outpu Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -218,13 +218,13 @@ Note to perl developers: This list should stay syncronized with the Matlab Class - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" The MATLAB scalar will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -294,12 +294,12 @@ The contents of this element should follow CustomAttribute syntax and convention - Maps a location on the Vector to an output data location. Can be used in conjuction with Templates. + Maps a location on the Vector to an output data location. Can be used in conjunction with Templates. - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" @@ -322,7 +322,7 @@ In the future, can be used to stitch together data from different function outpu The MATLAB scalar that is part of a MATLAB vector will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() diff --git a/specification/src/main/resources/released-schema/2007-06/STD.xsd b/specification/src/main/resources/released-schema/2007-06/STD.xsd index 9e68c9ae8..803248f11 100644 --- a/specification/src/main/resources/released-schema/2007-06/STD.xsd +++ b/specification/src/main/resources/released-schema/2007-06/STD.xsd @@ -70,7 +70,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2007-06/ome.xsd b/specification/src/main/resources/released-schema/2007-06/ome.xsd index 802af6460..13940ee67 100644 --- a/specification/src/main/resources/released-schema/2007-06/ome.xsd +++ b/specification/src/main/resources/released-schema/2007-06/ome.xsd @@ -50,7 +50,7 @@ - The OME element is a container for all information objects acessible by OME. These information objects include descriptions of the imaging experiments + The OME element is a container for all information objects accessible by OME. These information objects include descriptions of the imaging experiments and the people who perform them, descriptions of the microscope, the resulting images and how they were acquired, the analyses performed on those images, and the analysis results themselves. An OME file may contain any or all of this information. @@ -337,7 +337,7 @@ is not specified, then the FIRST <Pixels> element under <Image> will be as This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. Added Type Photobleaching - ajp diff --git a/specification/src/main/resources/released-schema/2008-02/BinaryFile.xsd b/specification/src/main/resources/released-schema/2008-02/BinaryFile.xsd index 2d8602da6..86822818e 100644 --- a/specification/src/main/resources/released-schema/2008-02/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2008-02/BinaryFile.xsd @@ -39,7 +39,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2008-02/CLI.xsd b/specification/src/main/resources/released-schema/2008-02/CLI.xsd index 68a6c33f4..d3ed53363 100644 --- a/specification/src/main/resources/released-schema/2008-02/CLI.xsd +++ b/specification/src/main/resources/released-schema/2008-02/CLI.xsd @@ -305,7 +305,7 @@ If used in conjunction with TerminateAt, reading will stop after RepeatCount or TerminateAt specifies a regular expression. When a match to this is found, reading will stop. -If used in conjuction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. @@ -412,7 +412,7 @@ This means a stack statistics record that specifies theC as an index before theT - Use this to construct a Delimited Record. (i.e. tab delimitted, comma delimitted, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. + Use this to construct a Delimited Record. (i.e. tab delimited, comma delimited, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. @@ -425,7 +425,7 @@ This means a stack statistics record that specifies theC as an index before theT - This will be used to separate Records. Defaults to a newline (a newline as interpretted by perl). + This will be used to separate Records. Defaults to a newline (a newline as interpreted by perl). @@ -474,7 +474,7 @@ This means a stack statistics record that specifies theC as an index before theT Allows SemanticTypes Pixels and PixelsPlane to be outputs. The subelements specify locations for the population of data. This data population is useful for a Plane projection algorithm that has the same X and Y dimensions as the Pixels it is operating on. -Alternately, these fields may be filled by ouput from STDOUT. +Alternately, these fields may be filled by output from STDOUT. The FileSHA1 subelement is automatically calculated for the pixel dump file. diff --git a/specification/src/main/resources/released-schema/2008-02/MLI.xsd b/specification/src/main/resources/released-schema/2008-02/MLI.xsd index d3e4c0f8c..a58a98b80 100644 --- a/specification/src/main/resources/released-schema/2008-02/MLI.xsd +++ b/specification/src/main/resources/released-schema/2008-02/MLI.xsd @@ -84,7 +84,7 @@ Will pass a numeric matrix into the function. -Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. +Translates a module input of Semantic Type Pixels (or any pseudo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. @@ -129,7 +129,7 @@ In the future, can be used to establish references. - Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value" + Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic element name. i.e. "Texture Direction.Direction_Value" @@ -171,7 +171,7 @@ In the future, can be used to establish references. - Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. + Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any pseudo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. @@ -189,7 +189,7 @@ In the future, can be used to stitch together data from different function outpu Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -218,13 +218,13 @@ Note to perl developers: This list should stay syncronized with the Matlab Class - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" The MATLAB scalar will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -294,12 +294,12 @@ The contents of this element should follow CustomAttribute syntax and convention - Maps a location on the Vector to an output data location. Can be used in conjuction with Templates. + Maps a location on the Vector to an output data location. Can be used in conjunction with Templates. - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" @@ -322,7 +322,7 @@ In the future, can be used to stitch together data from different function outpu The MATLAB scalar that is part of a MATLAB vector will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() diff --git a/specification/src/main/resources/released-schema/2008-02/STD.xsd b/specification/src/main/resources/released-schema/2008-02/STD.xsd index b4be024dc..0581f554e 100644 --- a/specification/src/main/resources/released-schema/2008-02/STD.xsd +++ b/specification/src/main/resources/released-schema/2008-02/STD.xsd @@ -70,7 +70,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2008-02/ome.xsd b/specification/src/main/resources/released-schema/2008-02/ome.xsd index b92676b4e..bddf69ef8 100644 --- a/specification/src/main/resources/released-schema/2008-02/ome.xsd +++ b/specification/src/main/resources/released-schema/2008-02/ome.xsd @@ -52,7 +52,7 @@ - The OME element is a container for all information objects acessible by OME. These information objects include descriptions of the imaging experiments + The OME element is a container for all information objects accessible by OME. These information objects include descriptions of the imaging experiments and the people who perform them, descriptions of the microscope, the resulting images and how they were acquired, the analyses performed on those images, and the analysis results themselves. An OME file may contain any or all of this information. @@ -365,7 +365,7 @@ This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. Added Type Photobleaching - ajp diff --git a/specification/src/main/resources/released-schema/2008-04/Editor.xsd b/specification/src/main/resources/released-schema/2008-04/Editor.xsd index a31886656..2a2d30d48 100644 --- a/specification/src/main/resources/released-schema/2008-04/Editor.xsd +++ b/specification/src/main/resources/released-schema/2008-04/Editor.xsd @@ -502,7 +502,7 @@ Currently allowed values are: "templateLocked" - This means that experimental variables can still be edited. "allAttributesLocked" - This means that no editing is allowed. - The presence or absence of this attribute idicates whether a field is locked. + The presence or absence of this attribute indicates whether a field is locked. @@ -511,7 +511,7 @@ - This boolean idicates whether it is mandatory to fill out the field. + This boolean indicates whether it is mandatory to fill out the field. If true, the field should not be left blank. diff --git a/specification/src/main/resources/released-schema/2008-09/BinaryFile.xsd b/specification/src/main/resources/released-schema/2008-09/BinaryFile.xsd index c85c47a81..aaba9edf0 100644 --- a/specification/src/main/resources/released-schema/2008-09/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2008-09/BinaryFile.xsd @@ -40,7 +40,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2008-09/CLI.xsd b/specification/src/main/resources/released-schema/2008-09/CLI.xsd index 88473cdaa..79e72f434 100644 --- a/specification/src/main/resources/released-schema/2008-09/CLI.xsd +++ b/specification/src/main/resources/released-schema/2008-09/CLI.xsd @@ -305,7 +305,7 @@ If used in conjunction with TerminateAt, reading will stop after RepeatCount or TerminateAt specifies a regular expression. When a match to this is found, reading will stop. -If used in conjuction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. @@ -412,7 +412,7 @@ This means a stack statistics record that specifies theC as an index before theT - Use this to construct a Delimited Record. (i.e. tab delimitted, comma delimitted, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. + Use this to construct a Delimited Record. (i.e. tab delimited, comma delimited, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. @@ -425,7 +425,7 @@ This means a stack statistics record that specifies theC as an index before theT - This will be used to separate Records. Defaults to a newline (a newline as interpretted by perl). + This will be used to separate Records. Defaults to a newline (a newline as interpreted by perl). @@ -474,7 +474,7 @@ This means a stack statistics record that specifies theC as an index before theT Allows SemanticTypes Pixels and PixelsPlane to be outputs. The subelements specify locations for the population of data. This data population is useful for a Plane projection algorithm that has the same X and Y dimensions as the Pixels it is operating on. -Alternately, these fields may be filled by ouput from STDOUT. +Alternately, these fields may be filled by output from STDOUT. The FileSHA1 subelement is automatically calculated for the pixel dump file. diff --git a/specification/src/main/resources/released-schema/2008-09/MLI.xsd b/specification/src/main/resources/released-schema/2008-09/MLI.xsd index 9101a047b..d6c1f0652 100644 --- a/specification/src/main/resources/released-schema/2008-09/MLI.xsd +++ b/specification/src/main/resources/released-schema/2008-09/MLI.xsd @@ -84,7 +84,7 @@ Will pass a numeric matrix into the function. -Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. +Translates a module input of Semantic Type Pixels (or any pseudo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. @@ -129,7 +129,7 @@ In the future, can be used to establish references. - Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value" + Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic element name. i.e. "Texture Direction.Direction_Value" @@ -171,7 +171,7 @@ In the future, can be used to establish references. - Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. + Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any pseudo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. @@ -189,7 +189,7 @@ In the future, can be used to stitch together data from different function outpu Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -218,13 +218,13 @@ Note to perl developers: This list should stay syncronized with the Matlab Class - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" The MATLAB scalar will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -294,12 +294,12 @@ The contents of this element should follow CustomAttribute syntax and convention - Maps a location on the Vector to an output data location. Can be used in conjuction with Templates. + Maps a location on the Vector to an output data location. Can be used in conjunction with Templates. - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" @@ -322,7 +322,7 @@ In the future, can be used to stitch together data from different function outpu The MATLAB scalar that is part of a MATLAB vector will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() diff --git a/specification/src/main/resources/released-schema/2008-09/STD.xsd b/specification/src/main/resources/released-schema/2008-09/STD.xsd index 73573628e..681553187 100644 --- a/specification/src/main/resources/released-schema/2008-09/STD.xsd +++ b/specification/src/main/resources/released-schema/2008-09/STD.xsd @@ -70,7 +70,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2008-09/ome.xsd b/specification/src/main/resources/released-schema/2008-09/ome.xsd index 545d27e4c..af9d4913d 100644 --- a/specification/src/main/resources/released-schema/2008-09/ome.xsd +++ b/specification/src/main/resources/released-schema/2008-09/ome.xsd @@ -369,7 +369,7 @@ This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. Added Type Photobleaching - ajp @@ -595,7 +595,7 @@ - There is optionally one of these per Image. They provide support for the Origional OME Perl server. + There is optionally one of these per Image. They provide support for the Original OME Perl server. This specifies mapping of image channel components to RGB or greyscale colorspace with one byte per pixel per RGB channel. RedChannel, GreenChannel, BlueChannel, and GreyChannel specify the scaling of pixel values to 8-bit colorspace values. Display indicates to display the image as Greyscale or RGB. diff --git a/specification/src/main/resources/released-schema/2009-09/BinaryFile.xsd b/specification/src/main/resources/released-schema/2009-09/BinaryFile.xsd index 6d4bc4a65..af1905fb0 100644 --- a/specification/src/main/resources/released-schema/2009-09/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2009-09/BinaryFile.xsd @@ -41,7 +41,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2009-09/CLI.xsd b/specification/src/main/resources/released-schema/2009-09/CLI.xsd index bb2379b7f..078f5905b 100644 --- a/specification/src/main/resources/released-schema/2009-09/CLI.xsd +++ b/specification/src/main/resources/released-schema/2009-09/CLI.xsd @@ -306,7 +306,7 @@ If used in conjunction with TerminateAt, reading will stop after RepeatCount or TerminateAt specifies a regular expression. When a match to this is found, reading will stop. -If used in conjuction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. +If used in conjunction with RepeatCount, reading will stop after RepeatCount or TerminateAt, whichever comes first. @@ -413,7 +413,7 @@ This means a stack statistics record that specifies theC as an index before theT - Use this to construct a Delimited Record. (i.e. tab delimitted, comma delimitted, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. + Use this to construct a Delimited Record. (i.e. tab delimited, comma delimited, etc). At some point this will be expanded to include XYPlanes and RawImageFilePath. @@ -426,7 +426,7 @@ This means a stack statistics record that specifies theC as an index before theT - This will be used to separate Records. Defaults to a newline (a newline as interpretted by perl). + This will be used to separate Records. Defaults to a newline (a newline as interpreted by perl). @@ -475,7 +475,7 @@ This means a stack statistics record that specifies theC as an index before theT Allows SemanticTypes Pixels and PixelsPlane to be outputs. The subelements specify locations for the population of data. This data population is useful for a Plane projection algorithm that has the same X and Y dimensions as the Pixels it is operating on. -Alternately, these fields may be filled by ouput from STDOUT. +Alternately, these fields may be filled by output from STDOUT. The FileSHA1 subelement is automatically calculated for the pixel dump file. diff --git a/specification/src/main/resources/released-schema/2009-09/MLI.xsd b/specification/src/main/resources/released-schema/2009-09/MLI.xsd index ff089dcfe..4afa17494 100644 --- a/specification/src/main/resources/released-schema/2009-09/MLI.xsd +++ b/specification/src/main/resources/released-schema/2009-09/MLI.xsd @@ -85,7 +85,7 @@ Will pass a numeric matrix into the function. -Translates a module input of Semantic Type Pixels (or any psuedo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. +Translates a module input of Semantic Type Pixels (or any pseudo subclass of Pixels) to a numeric matrix. Limits specified by PixelsSlice or its subclasses will be honored. @@ -130,7 +130,7 @@ In the future, can be used to establish references. - Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic elment name. i.e. "Texture Direction.Direction_Value" + Refers to a semantic element of a formal input. Syntax is formal input name, a period, and the semantic element name. i.e. "Texture Direction.Direction_Value" @@ -172,7 +172,7 @@ In the future, can be used to establish references. - Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any psuedo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. + Will translate a numeric array to a Formal Output of Semantic Type Pixels (or any pseudo subclass of Pixels). If PixelsSlice appears in the pseudo inheritance chain, the extents will be set to the extents of the Pixels. @@ -190,7 +190,7 @@ In the future, can be used to stitch together data from different function outpu Useful when a function outputs a Pixels type that is unsupported by OME. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME pixel-type mapping hash $self->{ _matlab_class_to_pixel_type } that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -219,13 +219,13 @@ Note to perl developers: This list should stay syncronized with the Matlab Class - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" The MATLAB scalar will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() @@ -295,12 +295,12 @@ The contents of this element should follow CustomAttribute syntax and convention - Maps a location on the Vector to an output data location. Can be used in conjuction with Templates. + Maps a location on the Vector to an output data location. Can be used in conjunction with Templates. - Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic elment name. i.e. "Angular Second Moment.ASM" + Refers to a semantic element of a formal output. Syntax is formal output name, a period, and the semantic element name. i.e. "Angular Second Moment.ASM" @@ -323,7 +323,7 @@ In the future, can be used to stitch together data from different function outpu The MATLAB scalar that is part of a MATLAB vector will be converted to the (MATLAB) datatype specified. The permitted list is the matlab types supported by OME. -Note to perl developers: This list should stay syncronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() +Note to perl developers: This list should stay synchronized with the Matlab Class to OME SE Type mapping hash $self->{ _matlab_class_to_ome_datatype} that is defined in OME::Analysis::Handlers::MatlabHandler->new() diff --git a/specification/src/main/resources/released-schema/2009-09/ROI.xsd b/specification/src/main/resources/released-schema/2009-09/ROI.xsd index aaffc027f..d8c61a1a8 100644 --- a/specification/src/main/resources/released-schema/2009-09/ROI.xsd +++ b/specification/src/main/resources/released-schema/2009-09/ROI.xsd @@ -299,7 +299,7 @@ The points of the polyline are defined as a list - of comma separated x,y coordinates seperated by + of comma separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2009-09/STD.xsd b/specification/src/main/resources/released-schema/2009-09/STD.xsd index f47745adc..7a5f79c9f 100644 --- a/specification/src/main/resources/released-schema/2009-09/STD.xsd +++ b/specification/src/main/resources/released-schema/2009-09/STD.xsd @@ -72,7 +72,7 @@ Defines a semantic type. Notes: - Granularity of SemanticType is infered from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. + Granularity of SemanticType is inferred from the granularity of the record it derives from. In a record, this granularity is specified by the AppliesTo attribute. diff --git a/specification/src/main/resources/released-schema/2009-09/ome.xsd b/specification/src/main/resources/released-schema/2009-09/ome.xsd index 96fa8cf81..7a994bc86 100644 --- a/specification/src/main/resources/released-schema/2009-09/ome.xsd +++ b/specification/src/main/resources/released-schema/2009-09/ome.xsd @@ -1023,7 +1023,7 @@ ExperimenterRef is required for all Images with well formed LSIDs. This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. diff --git a/specification/src/main/resources/released-schema/2010-04/BinaryFile.xsd b/specification/src/main/resources/released-schema/2010-04/BinaryFile.xsd index 679c93aef..c071daf85 100644 --- a/specification/src/main/resources/released-schema/2010-04/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2010-04/BinaryFile.xsd @@ -41,7 +41,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2010-04/ROI.xsd b/specification/src/main/resources/released-schema/2010-04/ROI.xsd index c526ba1c7..91ddeb82e 100644 --- a/specification/src/main/resources/released-schema/2010-04/ROI.xsd +++ b/specification/src/main/resources/released-schema/2010-04/ROI.xsd @@ -445,7 +445,7 @@ The points of the polyline are defined as a list - of comma separated x,y coordinates seperated by + of comma separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2010-04/ome.xsd b/specification/src/main/resources/released-schema/2010-04/ome.xsd index 39f5f9150..3e13d9f6e 100644 --- a/specification/src/main/resources/released-schema/2010-04/ome.xsd +++ b/specification/src/main/resources/released-schema/2010-04/ome.xsd @@ -1008,7 +1008,7 @@ ExperimenterRef is required for all Images with well formed LSIDs. This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. diff --git a/specification/src/main/resources/released-schema/2010-06/BinaryFile.xsd b/specification/src/main/resources/released-schema/2010-06/BinaryFile.xsd index b22e202af..c0e9d302b 100644 --- a/specification/src/main/resources/released-schema/2010-06/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2010-06/BinaryFile.xsd @@ -43,7 +43,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2010-06/ROI.xsd b/specification/src/main/resources/released-schema/2010-06/ROI.xsd index 48126de46..5f88cbe7f 100644 --- a/specification/src/main/resources/released-schema/2010-06/ROI.xsd +++ b/specification/src/main/resources/released-schema/2010-06/ROI.xsd @@ -460,7 +460,7 @@ The points of the polyline are defined as a list - of comma separated x,y coordinates seperated by + of comma separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2010-06/ome.xsd b/specification/src/main/resources/released-schema/2010-06/ome.xsd index 95134cc6b..4258646d9 100644 --- a/specification/src/main/resources/released-schema/2010-06/ome.xsd +++ b/specification/src/main/resources/released-schema/2010-06/ome.xsd @@ -1008,7 +1008,7 @@ ExperimenterRef is required for all Images with well formed LSIDs. This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. diff --git a/specification/src/main/resources/released-schema/2011-06/BinaryFile.xsd b/specification/src/main/resources/released-schema/2011-06/BinaryFile.xsd index 4eb628bcd..06ebfab86 100644 --- a/specification/src/main/resources/released-schema/2011-06/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2011-06/BinaryFile.xsd @@ -43,7 +43,7 @@ Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2011-06/ROI.xsd b/specification/src/main/resources/released-schema/2011-06/ROI.xsd index 032ad0a77..7738c742f 100644 --- a/specification/src/main/resources/released-schema/2011-06/ROI.xsd +++ b/specification/src/main/resources/released-schema/2011-06/ROI.xsd @@ -471,7 +471,7 @@ The points of the polyline are defined as a list - of comma separated x,y coordinates seperated by + of comma separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2011-06/ome.xsd b/specification/src/main/resources/released-schema/2011-06/ome.xsd index 9dc116f54..a76e4da2e 100644 --- a/specification/src/main/resources/released-schema/2011-06/ome.xsd +++ b/specification/src/main/resources/released-schema/2011-06/ome.xsd @@ -1083,7 +1083,7 @@ ExperimenterRef is required for all Images with well formed LSIDs. This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. diff --git a/specification/src/main/resources/released-schema/2012-06/BinaryFile.xsd b/specification/src/main/resources/released-schema/2012-06/BinaryFile.xsd index 8c119139b..8c968aa1c 100644 --- a/specification/src/main/resources/released-schema/2012-06/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2012-06/BinaryFile.xsd @@ -44,7 +44,7 @@ Externals Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2012-06/ROI.xsd b/specification/src/main/resources/released-schema/2012-06/ROI.xsd index 010a00851..2339229f4 100644 --- a/specification/src/main/resources/released-schema/2012-06/ROI.xsd +++ b/specification/src/main/resources/released-schema/2012-06/ROI.xsd @@ -471,7 +471,7 @@ The points of the polyline are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" @@ -493,7 +493,7 @@ The points of the Polygon are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2012-06/ome.xsd b/specification/src/main/resources/released-schema/2012-06/ome.xsd index cc8401ed2..dd3e476e6 100644 --- a/specification/src/main/resources/released-schema/2012-06/ome.xsd +++ b/specification/src/main/resources/released-schema/2012-06/ome.xsd @@ -1090,7 +1090,7 @@ This element describes the type of experiment. The required Type attribute must contain one or more entries from the following list: FP FRET Time-lapse 4-D+ Screen Immunocytochemistry FISH Electrophysiology Ion-Imaging Colocalization PGI/Documentation FRAP Photoablation Optical-Trapping Photoactivation Fluorescence-Lifetime Spectral-Imaging Other - FP refers to fluorescent proteins, PGI/Docuemntation is not a 'data' image. + FP refers to fluorescent proteins, PGI/Documentation is not a 'data' image. The optional Description element may contain free text to further describe the experiment. diff --git a/specification/src/main/resources/released-schema/2013-06/BinaryFile.xsd b/specification/src/main/resources/released-schema/2013-06/BinaryFile.xsd index e45bd67bc..301e3c4b3 100644 --- a/specification/src/main/resources/released-schema/2013-06/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2013-06/BinaryFile.xsd @@ -43,7 +43,7 @@ Externals Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2013-06/ROI.xsd b/specification/src/main/resources/released-schema/2013-06/ROI.xsd index aec485300..3f0e4f160 100644 --- a/specification/src/main/resources/released-schema/2013-06/ROI.xsd +++ b/specification/src/main/resources/released-schema/2013-06/ROI.xsd @@ -470,7 +470,7 @@ The points of the polyline are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" @@ -492,7 +492,7 @@ The points of the Polygon are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2015-01/BinaryFile.xsd b/specification/src/main/resources/released-schema/2015-01/BinaryFile.xsd index 7f5aa9d5e..3545215b2 100644 --- a/specification/src/main/resources/released-schema/2015-01/BinaryFile.xsd +++ b/specification/src/main/resources/released-schema/2015-01/BinaryFile.xsd @@ -44,7 +44,7 @@ Externals Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. -If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. +If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. diff --git a/specification/src/main/resources/released-schema/2015-01/ROI.xsd b/specification/src/main/resources/released-schema/2015-01/ROI.xsd index 26520b98e..ac5e6c959 100644 --- a/specification/src/main/resources/released-schema/2015-01/ROI.xsd +++ b/specification/src/main/resources/released-schema/2015-01/ROI.xsd @@ -492,7 +492,7 @@ The points of the polyline are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" @@ -514,7 +514,7 @@ The points of the Polygon are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/2016-06/ome.xsd b/specification/src/main/resources/released-schema/2016-06/ome.xsd index 79a534a1f..56c8ddc0e 100644 --- a/specification/src/main/resources/released-schema/2016-06/ome.xsd +++ b/specification/src/main/resources/released-schema/2016-06/ome.xsd @@ -3289,7 +3289,7 @@ Externals Describes a file location. Can optionally specify a portion of a file using Offset and a ReadLength. - If Offset and ReadLength are specified in conjuction with Compression, then they point into the uncompressed file. + If Offset and ReadLength are specified in conjunction with Compression, then they point into the uncompressed file. @@ -4181,7 +4181,7 @@ PlaneInfo (as Plane) The points of the polyline are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" @@ -4207,7 +4207,7 @@ PlaneInfo (as Plane) The points of the Polygon are defined as a list of comma - separated x,y coordinates seperated by spaces like "x1,y1 x2,y2 x3,y3" e.g. + separated x,y coordinates separated by spaces like "x1,y1 x2,y2 x3,y3" e.g. "0,0 1,2 3,5" diff --git a/specification/src/main/resources/released-schema/external/XMLSchema.xsd b/specification/src/main/resources/released-schema/external/XMLSchema.xsd index 1b0af68dc..e392979c8 100644 --- a/specification/src/main/resources/released-schema/external/XMLSchema.xsd +++ b/specification/src/main/resources/released-schema/external/XMLSchema.xsd @@ -451,7 +451,7 @@ Not allowed if simpleContent child is chosen. - May be overriden by setting on complexContent child. + May be overridden by setting on complexContent child. diff --git a/specification/src/main/resources/transforms/2008-09-to-2009-09.xsl b/specification/src/main/resources/transforms/2008-09-to-2009-09.xsl index 8e6a5c525..604a03338 100644 --- a/specification/src/main/resources/transforms/2008-09-to-2009-09.xsl +++ b/specification/src/main/resources/transforms/2008-09-to-2009-09.xsl @@ -664,7 +664,7 @@ @@ -1385,7 +1385,7 @@ - + diff --git a/specification/src/main/resources/transforms/2009-09-to-2010-04.xsl b/specification/src/main/resources/transforms/2009-09-to-2010-04.xsl index f05bc196a..64e1dc88b 100644 --- a/specification/src/main/resources/transforms/2009-09-to-2010-04.xsl +++ b/specification/src/main/resources/transforms/2009-09-to-2010-04.xsl @@ -256,7 +256,7 @@ diff --git a/specification/src/main/resources/transforms/2010-06-to-2003-FC.xsl b/specification/src/main/resources/transforms/2010-06-to-2003-FC.xsl index ec3edfc76..c33597f56 100644 --- a/specification/src/main/resources/transforms/2010-06-to-2003-FC.xsl +++ b/specification/src/main/resources/transforms/2010-06-to-2003-FC.xsl @@ -301,7 +301,7 @@ - MetadataOnly Files cannot be suported in version 2008-02 schema. + MetadataOnly Files cannot be supported in version 2008-02 schema. Begin Dummy BinData End Dummy BinData diff --git a/specification/src/main/resources/transforms/2010-06-to-2008-02.xsl b/specification/src/main/resources/transforms/2010-06-to-2008-02.xsl index 64af30975..2ce8fcdb6 100644 --- a/specification/src/main/resources/transforms/2010-06-to-2008-02.xsl +++ b/specification/src/main/resources/transforms/2010-06-to-2008-02.xsl @@ -436,7 +436,7 @@ - MetadataOnly Files cannot be suported in version 2008-02 schema. + MetadataOnly Files cannot be supported in version 2008-02 schema. Begin Dummy BinData 0 diff --git a/specification/src/main/resources/transforms/internal/OME-CA2OME.xslt b/specification/src/main/resources/transforms/internal/OME-CA2OME.xslt index d0cbd07e0..b10c31b79 100644 --- a/specification/src/main/resources/transforms/internal/OME-CA2OME.xslt +++ b/specification/src/main/resources/transforms/internal/OME-CA2OME.xslt @@ -4,7 +4,7 @@ OME Data Model transforms %% Copyright (C) 2003 - 2016 Open Microscopy Environment: - - Massachusetts Institue of Technology, + - Massachusetts Institute of Technology, - National Institutes of Health, - University of Dundee %% diff --git a/specification/src/main/resources/transforms/internal/OME2OME-CA.xslt b/specification/src/main/resources/transforms/internal/OME2OME-CA.xslt index 85c967090..b5de879c2 100644 --- a/specification/src/main/resources/transforms/internal/OME2OME-CA.xslt +++ b/specification/src/main/resources/transforms/internal/OME2OME-CA.xslt @@ -4,7 +4,7 @@ OME Data Model transforms %% Copyright (C) 2003 - 2016 Open Microscopy Environment: - - Massachusetts Institue of Technology, + - Massachusetts Institute of Technology, - National Institutes of Health, - University of Dundee %% @@ -686,7 +686,7 @@ - + diff --git a/xsd-fu/python/generateDS/README b/xsd-fu/python/generateDS/README index 0b2c61749..138b1f3f3 100644 --- a/xsd-fu/python/generateDS/README +++ b/xsd-fu/python/generateDS/README @@ -399,7 +399,7 @@ Version 1.9a (01/30/2007, again) . Version 1.9a (12/04/2006, again) - * Fixed errors (occuring on import of superclass module) when + * Fixed errors (occurring on import of superclass module) when an element is defined as an extension of an element that is defined as a simpleType restriction on an xs:string. @@ -409,7 +409,7 @@ Version 1.9a (11/27/2006, again) Version 1.9a (10/22/2006, again) * Fix to capture text content of nodes defined with attributes - but with no nested elements into member varialbe valueOf_. + but with no nested elements into member variable valueOf_. Version 1.9a (10/10/2006) * Added minimal support for simpleType. @@ -511,7 +511,7 @@ Version 1.7a (10/28/04) Thanks very much to Lloyd Kvam for help with these fixes and improvements. His ideas, suggestions, and work have been extremely valuable. - * Implementd partial support for . + * Implemented partial support for . Limitation: extension elements cannot override members defined in a base. * Refactored generated methods export and build, so that they @@ -693,7 +693,7 @@ The following enhancements and fixes remain to be done: - Nested (and sometimes anonymous) types -- In some cases, instead of defining a type at top level (with a type name) and then referencing that type inside another type definition, the - definition itself can be nested inside another type defintion. + definition itself can be nested inside another type definition. generateDS.py does not handle this. In effect, generateDS.py requires that you declare all type definitions at top level and that you name them (give them a "name" attribute. A future diff --git a/xsd-fu/python/generateDS/generateDS.html b/xsd-fu/python/generateDS/generateDS.html index 17ea33f76..ee642f09d 100644 --- a/xsd-fu/python/generateDS/generateDS.html +++ b/xsd-fu/python/generateDS/generateDS.html @@ -268,7 +268,7 @@

generateDS -- Generate Data Structures from XML Schema

  • 5   Common problems
  • 6   Supported features of XML Schema