X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=schemas%2Fvamsas.xsd;h=7f01fd2a7b4281d6605ed5b1e7722dde14e97f43;hb=a90114d92734607a7d966e5c4390eb22a2785afb;hp=5a74d58715db89497a3ab1e947c25545b4251346;hpb=787f8da0fbb39ad5b6acfecf5bf9dc9e0750317e;p=vamsas.git diff --git a/schemas/vamsas.xsd b/schemas/vamsas.xsd index 5a74d58..7f01fd2 100644 --- a/schemas/vamsas.xsd +++ b/schemas/vamsas.xsd @@ -1,23 +1,18 @@ - + - - Vorba ID - Vamsas Object Request Broker Address ID (name - needs to be worked on): Suggest it could be of the form - documentRoot/datasetName/SequenceUID for a dataset sequence. - Alignment sequence: - documentRoot/datasetName/AlignmentId/SequenceUID for an - aligned form of a dataset sequence - - + Vorba ID - Vamsas Object Request Broker Address ID (name needs to be + worked on): Suggest it could be of the form documentRoot/datasetName/SequenceUID for a + dataset sequence. Alignment sequence: documentRoot/datasetName/AlignmentId/SequenceUID + for an aligned form of a dataset sequence - - contains unassociated trees and a number of analysis - sets + contains unassociated trees and a number of analysis sets @@ -27,41 +22,26 @@ - - Primary Key for vamsas object referencing - + Primary Key for vamsas object referencing - - - - objects with modifiable=false will not be - modified by a vamsas client update - - + - - Properties. Generally, these are mutable so an application - should check them each time. This may change depending on - the context of the property + Properties. Generally, these are mutable so an application should check + them each time. This may change depending on the context of the property - - Contains a named collection of trees - - - TODO: define - way of referencing leaves of global tree for any - sequence/alignment object. - SUggestion 1: Each named tree leafnode has a unique id (which may be unique in combination with trees own vorba ID). - Dataset sequences can be tagged with a property "vamsas:tree_leaf" - + Contains a named collection of trees + TODO: define way of referencing leaves of global tree for any + sequence/alignment object. SUggestion 1: Each named tree leafnode has a unique + id (which may be unique in combination with trees own vorba ID). Dataset + sequences can be tagged with a property "vamsas:tree_leaf" @@ -72,21 +52,11 @@ - - Primary Key for vamsas - object referencing + Primary Key for vamsas object referencing - - - - objects with - modifiable=false will not be - modified by a vamsas client - update - - + @@ -97,18 +67,10 @@ - - Primary Key for vamsas object referencing - + Primary Key for vamsas object referencing - - - - objects with modifiable=false will not be - modified by a vamsas client update - - + @@ -116,21 +78,15 @@ - - Named and typed property string - + Named and typed property string - - The type specifies how the property will - be parsed. Empty property strings are - allowed, and can be used to prototype - the input to a document. TODO: specify - allowed types - + The type specifies how the property will be parsed. + Empty property strings are allowed, and can be used to prototype the + input to a document. TODO: specify allowed types @@ -140,9 +96,7 @@ - - Primitive labelled URI object - + Primitive labelled URI object @@ -157,22 +111,16 @@ - - Specify an ordered set of positions and/or regions on the principle - dimension of some associated vamsas object - - - Keeping to jaxb-1.0 specification for the moment - this - choice should become a substitution group when we use - jaxb-2.0 capable bindings + Specify an ordered set of positions and/or regions on the principle + dimension of some associated vamsas object + Keeping to jaxb-1.0 specification for the moment - this choice should + become a substitution group when we use jaxb-2.0 capable bindings - - a position within the associated object's - coordinate system + a position within the associated object's coordinate system @@ -181,20 +129,16 @@ - - a region from start to end, with flag for - inclusivity of terminii - + a region from start to end, with flag for inclusivity of + terminii - - when false, a consecutive range like - 'start=1, end=2' means the region lying - after position 1 and before position 2 + when false, a consecutive range like 'start=1, end=2' + means the region lying after position 1 and before position 2 @@ -205,55 +149,50 @@ - - Annotation for a rangeSpec - values can be attached for the whole specification, and to each position within the spec. following the orientation specified by the ordered set of rangeSpec (pos, seg) elements. - + Annotation for a rangeSpec - values can be attached for the whole + specification, and to each position within the spec. following the orientation + specified by the ordered set of rangeSpec (pos, seg) elements. - - Short, meaningful name for the annotation - if this is absent, then the type string should be used in its place. - + Short, meaningful name for the annotation - if this + is absent, then the type string should be used in its place. + - - Human readable description of the annotation - + Human readable description of the annotation + - - TODO: specify this - we have considered taking the GO evidence codes as a model for assessing a measure of quality to an annotation. - + TODO: specify this - we have considered taking the GO + evidence codes as a model for assessing a measure of quality to an + annotation. - - Annotation Element position maps to - ordered positions defined by the - sequence of rangeType pos positions or - concatenated seg start/end segments. - + Annotation Element position maps to ordered positions + defined by the sequence of rangeType pos positions or concatenated + seg start/end segments. - - Ordered set of optionally named float - values for the whole annotation - + Ordered set of optionally named float values for the + whole annotation - + @@ -261,47 +200,32 @@ - - Note:These are mutable so an application - should check them each time. - + Note:These are mutable so an application should check + them each time. - - Primary Key for vamsas object referencing + Primary Key for vamsas object referencing - - - - objects with modifiable=false will not be - modified by a vamsas client update - - + - - Annotation with the same non-empty group - name are grouped together - + Annotation with the same non-empty group name are grouped + together - - A Das Feature has both a type and a Type ID. - We go the route of requiring the type string - to be taken from a controlled vocabulary if - an application expects others to make sense - of it. - The type may qualified - so uniprot:CHAIN is a valid type name, - and considered distinct from someotherDB:CHAIN - + A Das Feature has both a type and a Type ID. We go the + route of requiring the type string to be taken from a controlled + vocabulary if an application expects others to make sense of it. The + type may qualified - so uniprot:CHAIN is a valid type name, and + considered distinct from someotherDB:CHAIN @@ -310,32 +234,22 @@ - - Specifies a named and typed value used to perform - some data transformation. - - - LATER: experiment with xml validation of property - set prototypes for services - + Specifies a named and typed value used to perform some data + transformation. + LATER: experiment with xml validation of property set prototypes + for services - - Named and typed property string - + Named and typed property string - - The type specifies how the property will - be parsed. Empty property strings are - allowed, and can be used to prototype - the input to a document. TODO: specify - allowed types - + The type specifies how the property will be parsed. + Empty property strings are allowed, and can be used to prototype the + input to a document. TODO: specify allowed types @@ -345,21 +259,16 @@ - - Selects all or part of a collection of vamsas - objects as a named input to some transformation - process. Many inputs with the same name imply a - group input (such as a collection of sequences) - + Selects all or part of a collection of vamsas objects as a named + input to some transformation process. Many inputs with the same name imply a + group input (such as a collection of sequences) - - Reference Frame for rangeType - specfication + Reference Frame for rangeType specfication @@ -370,10 +279,8 @@ - - Defines the origin and series of operations applied - directly to the object that references it. - + Defines the origin and series of operations applied directly to + the object that references it. @@ -381,60 +288,44 @@ - - Who - + Who - - With which application - + With which application - - Did what - + Did what - - When - + When - - additional information - + additional information - - parameter for the action - + parameter for the action - - bioinformatic objects input to - action + bioinformatic objects input to action - - Primary Key for vamsas object - referencing + Primary Key for vamsas object referencing @@ -446,173 +337,87 @@ - - A collection of sequences, alignments, trees and - other things. + A collection of sequences, alignments, trees and other things. - - a primary or secondary sequence record - from which all other sequences may be - derived - + a primary or secondary sequence record from which all + other sequences may be derived - - Store a list of database - references for this - sequence record - with - optional mapping from - database sequence to the - given sequence record - + Store a list of database references + for this sequence record - with optional mapping + from database sequence to the given sequence record - + + From: Offset to first + position in dataset sequence record that + this database entry maps to To: Offset + to last position in dataset sequence + record that this database entry maps to + Start: Offset to first last position in + database entry that first (or offset) + position in sequence maps to End: Offset + to last position in database entry that + last (offset) position in sequence maps + to + - - - - Offset - to - first - position - in - dataset - sequence - record - that - this - database - entry - maps - to - - - - - - - Offset - to - last - position - in - dataset - sequence - record - that - this - database - entry - maps - to - - - - - - - Offset - to first - last - position - in - database - entry - that - first - (or - offset) - position - in - sequence - maps to - - - - - - - Offset - to last - position - in - database - entry - that - last - (offset) - position - in - sequence - maps to - - - - + + + + + + - - + + - + - - TODO Database - Naming - Convention: - either start - using LSID (so - change type to - URI) or leave - this as an - uncontrolled/unspecified - string ID - + TODO Database Naming + Convention: either start using LSID (so + change type to URI) or leave this as an + uncontrolled/unspecified string ID + - + - - Version must be - specified - - + Version must be specified - + - + - - TODO: make some - specification of - the database - field from which - this accessionId - is taken from - - should that be a - special property - of the dbRef - object ? - + TODO: make some specification + of the database field from which this + accessionId is taken from - should that be a + special property of the dbRef object ? + - - Primary Key for - vamsas object - referencing - + Primary Key for vamsas object + referencing @@ -620,16 +425,13 @@ - - Primary Key for vamsas - object referencing + Primary Key for vamsas object referencing - - symbol class for sequence + symbol class for sequence @@ -640,10 +442,8 @@ - - Annotate over positions and regions of a - dataset sequence - + Annotate over positions and regions of a dataset + sequence @@ -652,11 +452,8 @@ - - annotation is associated - with a particular dataset - sequence - + annotation is associated with a + particular dataset sequence @@ -666,12 +463,11 @@ - + - - This is annotation over the - coordinate frame defined by all - the columns in the alignment. + This is annotation over the coordinate frame + defined by all the columns in the alignment. @@ -680,18 +476,13 @@ - + - - TODO: decide if - this flag is - redundant - when - true it would - suggest that the - annotationElement - values together - form a graph - + TODO: decide if this flag is + redundant - when true it would suggest that + the annotationElement values together form a + graph @@ -704,60 +495,38 @@ - - - - - Annotate - over - positions - and - regions - of the - ungapped - sequence - in the - context - of the - alignment - - - - - - - - - - - - TODO: - decide - if - this - flag - is - redundant - - - when - true - it - would - suggest - that - the - annotationElement - values - together - form - a - graph - - - - - - - + - - Primary Key for - vamsas object - referencing - + Primary Key for vamsas object + referencing - + - - Dataset Sequence - from which this - alignment - sequence is - taken from - + Dataset Sequence from which + this alignment sequence is taken from + @@ -797,11 +560,8 @@ - - typical properties may be - additional alignment score - objects - + typical properties may be additional + alignment score objects @@ -810,21 +570,13 @@ - - Primary Key for vamsas object - referencing + Primary Key for vamsas object referencing - - - - objects with modifiable=false will - not be modified by a vamsas client - update - - + + @@ -832,9 +584,7 @@ - - Primary Key for vamsas object referencing - + Primary Key for vamsas object referencing @@ -842,53 +592,36 @@ - - per-site symbolic and/or quantitative annotation - - - SecondaryStructure and display character (from - Jalview) have been subsumed into the glyph element - + per-site symbolic and/or quantitative annotation + SecondaryStructure and display character (from Jalview) have been + subsumed into the glyph element - - Free text at this position - + Free text at this position - - Discrete symbol - possibly graphically - represented + Discrete symbol - possibly graphically represented - + - - specifies the symbol - dictionary for this glyph - - eg utf8 (the default), - aasecstr_3 or - kd_hydrophobicity - the - content is not validated so - applications must ensure - they gracefully deal with - invalid entries here - - - TODO: specify a minimum list - of glyph dictionaries to get - us started and provide a way - for the vamsasClient to - validate their content if - regexes are specified - + specifies the symbol dictionary for this + glyph - eg utf8 (the default), aasecstr_3 or + kd_hydrophobicity - the content is not validated so + applications must ensure they gracefully deal with + invalid entries here + TODO: specify a minimum list of glyph + dictionaries to get us started and provide a way for the + vamsasClient to validate their content if regexes are + specified @@ -897,38 +630,29 @@ - - Ordered set of float values - an application - may treat the values together as a vector - with common support for a set of annotation - elements - but this is, again, not validated - so applications should deal gracefully with - varying numbers of dimensions + Ordered set of float values - an application may treat + the values together as a vector with common support for a set of + annotation elements - but this is, again, not validated so applications + should deal gracefully with varying numbers of dimensions - - position with respect to the coordinate frame - defined by a rangeType specification - + position with respect to the coordinate frame defined by a + rangeType specification - - true means the annotation element appears - between the specified position and the next - + true means the annotation element appears between the + specified position and the next - - Primary Key for vamsas object referencing - + Primary Key for vamsas object referencing @@ -940,12 +664,23 @@ - - additional typed properties - + additional typed properties - + + + + + + + object to which the mapping is being mapped + + + + + + + @@ -953,10 +688,8 @@ - - Data specific to a particular type and version of - vamsas application - + Data specific to a particular type and version of vamsas + application @@ -966,13 +699,13 @@ - - Data available to just a - particular user - + Data available to just a particular + user - - + + @@ -989,23 +722,13 @@ - - 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 - + 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 @@ -1015,15 +738,13 @@ - - Version string describing the application specific data storage version used + Version string describing the application specific + data storage version used - - Canonical name of application - + Canonical name of application @@ -1035,41 +756,30 @@ - - General data container to attach a typed - data object to any vamsas object - + General data container to attach a typed data object to + any vamsas object - - true implies data will be decompresses - with Zip before presenting to - application - + true implies data will be decompresses with Zip + before presenting to application - - Type of arbitrary data - TODO: decide - format - use (extended) MIME types ? - + Type of arbitrary data - TODO: decide format - use + (extended) MIME types ? - - Object the arbitrary data is associated - with + Object the arbitrary data is associated with - - Primary Key for vamsas object - referencing + Primary Key for vamsas object referencing @@ -1083,28 +793,43 @@ - - - - - - - - - - - - - - - - - - - - - - - - + + + + Offset to first position in dataset sequence record that start + position on 'onto' maps to + + + + + Offset to last position in dataset sequence record that end + position on 'onto' maps to + + + + + Offset to first position in database entry that first (or offset) + position in sequence maps to + + + + + Offset to last position in database entry that last (offset) + position in sequence maps to + + + + + + + Contains lock information: + locktype:ApplicationHandle + locktype is 'local' or 'full' + A lock is only valid if the ApplicationHandle resolves to a living application in the vamsas session. + A local lock means that the application has locked changes to all local properties on the object. + A full lock means that the application has locked changes to all properties on the object, and any objects that it holds references to. + + + +