X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=schemas%2Fvamsas.xsd;fp=schemas%2Fvamsas.xsd;h=25ccc5500bce94059ff85eba14acb290ff39f371;hb=1b6e5d1b5e248e6c4455f748df970b9fabba4bb4;hp=bf17ca382a4689eff507ac06474de6e32fde223b;hpb=6944ad87af9e39a36c8dc42c077f836bee01599a;p=vamsas.git diff --git a/schemas/vamsas.xsd b/schemas/vamsas.xsd index bf17ca3..25ccc55 100644 --- a/schemas/vamsas.xsd +++ b/schemas/vamsas.xsd @@ -4,7 +4,7 @@ - Specify positions and/or regions on the principle dimension of some associated vamsas objects + Specify positions and/or regions on the principle dimension of some associated vamsas object TODO: this is abstract. should provide context to scope the range of ids for each use Keeping to jaxb-1.0 specification for the moment - this choice should become a substitution group when we use jaxb-2.0 capable bindings @@ -105,9 +105,7 @@ Annotation with the same non-empty group name are grouped together - - annotation may be associated with a particular sequence lying within the same reference frame as the rangeType's objRef - + @@ -202,7 +200,11 @@ Annotate over positions and regions of dataset sequences - + + + annotation may be associated with a particular sequence lying within the same reference frame as the rangeType's objRef + + @@ -212,9 +214,18 @@ Annotate over positions and regions of the alignment - + + + annotation may be associated with a particular sequence lying within the same reference frame as the rangeType's objRef + + + + + TODO: hard to distinguish this from the alignment features element. Do we merge them and leave the applications + + @@ -233,19 +244,17 @@ - - + + Annotate over positions and regions of the ungapped sequences in the alignment TODO: have to remove id rangeSpec or require it to be the same as dataset sequence reference - - - + Primary Key for vamsas object referencing - + Dataset Sequence from which this alignment sequence is taken from @@ -303,9 +312,9 @@ - - - + + + additional typed properties @@ -343,6 +352,7 @@ Data available to just a specific instance of the application + VAMSAS/Pierre: Is this data volatile ? Application instances may not be accessible after the session has closed - the user may have to be presented with the option of picking up the data in that instance